Re: log_statement vs Statistics Collector (pg_stat_database,, etc) - Mailing list pgsql-admin

From Nik Tek
Subject Re: log_statement vs Statistics Collector (pg_stat_database,, etc)
Date
Msg-id CAHySzWWVrcZXNc5z6umEy5YBxo5ew4r9wOoAAyq+=NpwqeE2vw@mail.gmail.com
Whole thread Raw
In response to Re: log_statement vs Statistics Collector (pg_stat_database,, etc)  (Matheus de Oliveira <matioli.matheus@gmail.com>)
Responses Re: log_statement vs Statistics Collector (pg_stat_database,, etc)
Re: log_statement vs Statistics Collector (pg_stat_database,, etc)
List pgsql-admin
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.matheus@gmail.com> wrote:

On Thu, Dec 24, 2015 at 7:32 PM, Nik Tek <niktek2005@gmail.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

pgsql-admin by date:

Previous
From: Iñigo Salvat
Date:
Subject: backward issue
Next
From: Scott Whitney
Date:
Subject: Re: log_statement vs Statistics Collector (pg_stat_database,, etc)