Re: pgbadger question
От | S.Bob |
---|---|
Тема | Re: pgbadger question |
Дата | |
Msg-id | 320bd9d9-2f7c-0c4d-7f69-8ae5fa8b5fe8@quadratum-braccas.com обсуждение исходный текст |
Ответ на | Re: pgbadger question (manish yadav <manishy174@yahoo.co.in>) |
Список | pgsql-admin |
Already tried that, no luck
On 2/26/20 9:22 PM, manish yadav wrote:
Hi,Please try with passing parameter log_line_prefix using --prefixpgbadger --prefix <value in log_line_prefix> -o postgres-Mon.html ./postgres-Mon.logNote : copy/paste exact value from PostgreSQL.conf file/show all and paste in the command above.Thanks and Regards,Manish Yadav
Mobile : +91 8527607945On 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 = -1When I attempt to parse a report with pgbadger like this:pgbadger -o postgres-Mon.html ./postgres-Mon.logIt parses zero queries, even though the query data is there, just thatit was logged via log_statement = 'all' instead of via settinglog_min_duration_statement = xIs there any way to force pgbadger to pick up / reckognize the loggesqueries?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)
-- `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 по дате отправления: