Horton

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

Nathan Bossart <nathandbossart@gmail.com>

View thread View on postgr.es
From: Nathan Bossart <nathandbossart@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrew Dunstan <andrew@dunslane.net>, Mahendra Singh Thalor <mahi6run@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2026-03-16T14:52:21Z
Lists: pgsql-hackers 
On Sun, Mar 15, 2026 at 12:20:41PM -0400, Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.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.

Agreed, I don't think back-patching is worth the (probably low) risk.  The
latest patch for v19 looks good to me.  I recently committed some stuff in
this area, so I can take care of committing this one, too.

-- 
nathan

Commits

  1. pg_dumpall: Fix handling of incompatible options.