-
Notifications
You must be signed in to change notification settings - Fork 360
Open
Description
On my pgbadger installation I see regression between pgbadger 11.2 and 13.1.
In "Most Frequent Errors/Events" section for "ERROR: invalid byte sequence for encoding" in 11.2 I have examples, but in 13.1 pgbadger generates without it.
The command to run pgbadger is:
/usr/bin/pgbadger --tempdir /var/lib/pgbadger/tmp/xxx --pid-dir /var/lib/pgbadger/tmp/xxx --pid-file /var/lib/pgbadger/tmp/xxx/xxx.pid --timezone +3 --jobs 4 -q --disable-query --prefix '#%m [%p]: [%l-1] { user=%u,db=%d,c=%c,e=%e,x=%x,a=%a,r=%r,i=%i,v=%v } ' -o /var/lib/pgbadger/www/htdocs/xxx/xxx.html /var/lib/backup/pg_logs/xxx/xxx/xxx-*.log
PostgreSQL log line:
#2025-06-17 11:48:30.555 [1380788]: [123192-1] { user=xxx,db=xxx,c=685128bd.1511b4,e=22021,x=0,a=xxx(xxx):,r=x.x.x.x(55880),i=idle,v=98/0 } ERROR: invalid byte sequence for encoding "UTF8": 0xc0 0x20
pgbadger 11.2:
pgbadger 13.1:
Metadata
Metadata
Assignees
Labels
No labels