From: | manish yadav <manishy174(at)yahoo(dot)co(dot)in> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org, "S(dot)Bob" <sbob(at)quadratum-braccas(dot)com> |
Subject: | Re: pgbadger question |
Date: | 2020-02-27 04:22:06 |
Message-ID: | 1410727976.946305.1582777326664@mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi,
Please try with passing parameter log_line_prefix using --prefix
pgbadger --prefix <value in log_line_prefix> -o postgres-Mon.html ./postgres-Mon.log
Note : copy/paste exact value from PostgreSQL.conf file/show all and paste in the command above.
Thanks and Regards,
Manish Yadav
Mobile : +91 8527607945
On Thursday, 27 February 2020, 1:47:43 AM IST, S.Bob <sbob(at)quadratum-braccas(dot)com> wrote:
All;
Sorry if this is OT:
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?
Thanks in advance
--
`When you say "I wrote a program that crashed Windows", people just stare at you blankly and say "Hey, I got those with the system, *for free*".' (By Linus Torvalds)
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2020-02-27 12:53:26 | Re: PG v12.2 - Setting jit_above_cost is causing the server to crash |
Previous Message | Jeff Janes | 2020-02-26 22:43:53 | Re: "NEVER" cautioned to auto_explain's log_analyze parameter on Production |