Re: pgbadger question
От | manish yadav |
---|---|
Тема | Re: pgbadger question |
Дата | |
Msg-id | 1410727976.946305.1582777326664@mail.yahoo.com обсуждение исходный текст |
Ответ на | pgbadger question ("S.Bob" <sbob@quadratum-braccas.com>) |
Ответы |
Re: pgbadger question
|
Список | 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,
Mobile : +91 8527607945
On Thursday, 27 February 2020, 1:47:43 AM IST, S.Bob <sbob@quadratum-braccas.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)
В списке pgsql-admin по дате отправления: