Re: bug: pg_dumpall with --data-only and --clean options is giving an error after some dump

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Mahendra Singh Thalor <mahi6run(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: bug: pg_dumpall with --data-only and --clean options is giving an error after some dump
Date: 2026-03-15 16:20:41
Message-ID: 2018594.1773591641@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Hmm, this looks like behaviour that goes a long way back. Should we
> backpatch this fix?

I wouldn't bother. At the end of the day you get the same failure
report anyway.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2026-03-15 16:31:19 Re: pg_restore --format= option(without any value) should report an error as pg_dump is reporting an error
Previous Message Andrew Dunstan 2026-03-15 16:16:11 Re: pg_restore: remove unnecessary code from restore_all_databases function