<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>pg_stat_statements on BonesMoses.org</title>
    <link>https://bonesmoses.org/tags/pg_stat_statements/</link>
    <description>Recent content in pg_stat_statements on BonesMoses.org</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 05 Aug 2014 14:35:05 +0000</lastBuildDate><atom:link href="https://bonesmoses.org/tags/pg_stat_statements/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>On PostgreSQL Logging Verbosity</title>
      <link>https://bonesmoses.org/2014/on-postgresql-logging-verbosity/</link>
      <pubDate>Tue, 05 Aug 2014 14:35:05 +0000</pubDate>
      
      <guid>https://bonesmoses.org/2014/on-postgresql-logging-verbosity/</guid>
      <description>Recently I stumbled across a question on Reddit regarding the performance impact of using pgBadger on an active database server. The only real answer to this question is: do not use pgBadger. Before anyone asks&amp;mdash;no, you shouldn&amp;rsquo;t use pgFouine either. This is not an indictment on the quality of either project, but a statement of their obsolescence in the face of recent PostgreSQL features.
One of the recommended postgresql.conf changes for both of these tools is to set log_min_duration_statement to 0.</description>
    </item>
    
  </channel>
</rss>
