Re: log_statement vs Statistics Collector (pg_stat_database,, etc)

I am sorry. I am late to this thread. Please do not think there is zero impact.

-------- Original message --------
From: Nik Tek <niktek2005(at)gmail(dot)com>
Date: 12/28/2015 6:05 PM (GMT-06:00)
To: Matheus de Oliveira <matioli(dot)matheus(at)gmail(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] log_statement vs Statistics Collector (pg_stat_database,, etc)

Thank you Matheus!

Based on the study, there's very little performance impact when enabling log_min_duration_statement, right?

Thank you
Nik

On Sun, Dec 27, 2015 at 5:35 AM, Matheus de Oliveira <matioli(dot)matheus(at)gmail(dot)com<mailto:matioli(dot)matheus(at)gmail(dot)com>> wrote:

On Thu, Dec 24, 2015 at 7:32 PM, Nik Tek <niktek2005(at)gmail(dot)com<mailto:niktek2005(at)gmail(dot)com>> wrote:
I wanted to capture all the DML statements executed in the database information (execution time, ).

Question:
Can anyone point me pros and cons on either of the approaches.

In my testing, I haven't found any performance degrade on application operations when enabled the additional logging (below logging).

Besides log_min_duration_statement, you can use tools like pg_stat_statements [1] and POWA [2]. POWA authors even did a comparison of performance impact of having log_min_duration_statement (to latter process with pgBadger), using POWA extension and nothing, see [3].

[1] http://www.postgresql.org/docs/current/static/pgstatstatements.html
[2] http://dalibo.github.io/powa/
[3] https://github.com/dalibo/powa/wiki/POWA-vs-pgBadger

--
Matheus de Oliveira

--
Thank you
NikTeki

Journyx, Inc.
7600 Burnet Road #300
Austin, TX 78757
www.journyx.com

p 512.834.8888
f 512-834-8858

Do you receive our promotional emails? You can subscribe or unsubscribe to those emails at http://go.journyx.com/emailPreference/e/4932/714/