<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Postgresql on Aditya Naik | Personal Website</title>
    <link>https://d6cbd428.hugo-blog-e6x.pages.dev/tags/postgresql/</link>
    <description>Recent content in Postgresql on Aditya Naik | Personal Website</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 02 Jul 2023 06:33:21 +0000</lastBuildDate>
    <atom:link href="https://d6cbd428.hugo-blog-e6x.pages.dev/tags/postgresql/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PGBadger | Postgresql log analysis made easy</title>
      <link>https://d6cbd428.hugo-blog-e6x.pages.dev/blog/2023/07/02/pgbadger-postgresql-log-analysis-made-easy/</link>
      <pubDate>Sun, 02 Jul 2023 06:33:21 +0000</pubDate>
      <guid>https://d6cbd428.hugo-blog-e6x.pages.dev/blog/2023/07/02/pgbadger-postgresql-log-analysis-made-easy/</guid>
      <description>&lt;h2 id=&#34;the-need-for-postgresql-log-analysis&#34;&gt;The need for postgresql log analysis?&lt;/h2&gt;&#xA;&lt;p&gt;While writing sql for any flow, primary focus is on the correctness of the query and not on the performance of the query. Performance issues creep in when updating/iterating a flow iteratively over multiple development cycles.Query performance is important to analyze during scaling. This is where query log analysis comes in.&lt;/p&gt;&#xA;&lt;p&gt;In one of our cases, a complicated workflow was significantly slow when we load tested it. We were trying to figure out the bottleneck both in code structure and with query performance. Our go-to tool for query performance analysis became &lt;code&gt;pgBadger&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
