From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
---|---|
To: | "S(dot)Bob" <sbob(at)quadratum-braccas(dot)com> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgbadger question |
Date: | 2020-02-26 20:26:12 |
Message-ID: | CAOBaU_Yc609C1MfApjXYP37UHzkW9N1efL2PgiSY6nPAZX+=dQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi,
On Wed, Feb 26, 2020 at 9:17 PM S.Bob <sbob(at)quadratum-braccas(dot)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.".
From | Date | Subject | |
---|---|---|---|
Next Message | Jacque | 2020-02-26 21:17:21 | "NEVER" cautioned to auto_explain's log_analyze parameter on Production |
Previous Message | S.Bob | 2020-02-26 20:17:11 | pgbadger question |