pg_dumpall bug exit code 0 with fatal

From: Владимир Фролов <frolov(dot)vova(at)gmail(dot)com>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: pg_dumpall bug exit code 0 with fatal
Date: 2026-04-23 15:17:32
Message-ID: CADi=iLRqiz4qD_DoG225D=HtQLPx56HF=D2WcYGGRxx8g0TK0Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I have installed two nodes cluster- PostgreSQL 16.3 (Debian
16.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian
12.2.0-14) 12.2.0, 64-bit with wal logical replication. When i run
pgdump_all - i have error -
pg_dump: error: Dumping the contents of table "*****" failed: PQgetResult()
failed.
pg_dump: detail: Error message from server: ERROR: canceling statement due
to conflict with recovery
DETAIL: User query might have needed to see row versions that must be
removed.
pg_dump: detail: Command was: COPY **** ( **** ) TO stdout;
pg_dumpall: error: pg_dump failed on database "**********", exiting
it is normal, BUT! exit code is 0! In my backup script tell OK to this
task. Monitoring tell ok, but backup is empty (

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2026-04-23 15:40:14 Re: to_date()/to_timestamp() silently accept month=0 and day=0
Previous Message David G. Johnston 2026-04-23 13:04:47 Re: Please subscribe