Re: pgbadger question - Mailing list pgsql-admin

From Julien Rouhaud
Subject Re: pgbadger question
Date
Msg-id CAOBaU_Yc609C1MfApjXYP37UHzkW9N1efL2PgiSY6nPAZX+=dQ@mail.gmail.com
Whole thread Raw
In response to pgbadger question  ("S.Bob" <sbob@quadratum-braccas.com>)
List pgsql-admin
Hi,

On Wed, Feb 26, 2020 at 9:17 PM S.Bob <sbob@quadratum-braccas.com> wrote:
>
> We have a client that logs all statements with :
>
> log_statement = 'all'
>
> However they also have left log_min_duration_statement disabled:
>
> log_min_duration_statement = -1
>
>
> When I attempt to parse a report with pgbadger like this:
>
> pgbadger -o postgres-Mon.html ./postgres-Mon.log
>
>
> It parses zero queries, even though the query data is there, just that
> it was logged via log_statement = 'all' instead of via setting
> log_min_duration_statement = x
>
>
> Is there any way  to force pgbadger to pick up / reckognize the logges
> queries?

According to https://github.com/darold/pgbadger/, it's not possible:

"Do not enable log_statement as its log format will not be parsed by pgBadger.".



pgsql-admin by date:

Previous
From: "S.Bob"
Date:
Subject: pgbadger question
Next
From: Jacque
Date:
Subject: "NEVER" cautioned to auto_explain's log_analyze parameter onProduction