Closed bagafoot closed 1 year ago
I had read https://github.com/darold/pgbadger/issues/540 and try -f stderr but it didnt work. I think the main issue is "new line" that not begin with prefix
$38 = '0', $39 = '0', $40 = '0', $41 = NULL, $42 = 'sometext sometext', $43 = '2023-02-14 22:14:26', $44 = '2023-02-09 17:05:22', $45 = '2023-02-09 17:05:22', $46 = '2023-02-09 17:05:22',
I opened log file with notepad++ and it show that new line CRLF
Commit f9658bf might fix this issue, please confirm.
@darold thanks, I think it will work, Are you going to release it in the next patch?
A new release have been published, see https://github.com/darold/pgbadger/releases/tag/v12.1
When binding parameter ( $1, $2 etc) has new line then pgbadger could not parse the line, how to solve this problem, or ignore.
pgBadger version 12.0
command:
/bin/pgbadger --prefix "t[%m] p[%p] h[%h] db[%d] u[%u] x[%x]" -v -d dbexmpl -a 1 -j 20 -s 2 -T "dbexmpl " -q -O /var/lib/pgsql/12/pgbadger/ --exclude-query="^(COPY|VACUUM)" -o dbexmpl.html /LOG/12/dbexmpl_log/dbexmpl12db01-2023.02.16
example:the point where pgbadger cannot parse: