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

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, 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-16 16:05:39
Message-ID: abgqU-mWqDBRQh4_@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 16, 2026 at 09:52:21AM -0500, Nathan Bossart wrote:
> 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.

Committed.

--
nathan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ayush Tiwari 2026-03-16 16:09:30 Proposal: Prevent Primary/Standby SLRU divergence during MultiXact truncation
Previous Message Alvaro Herrera 2026-03-16 16:03:47 Re: Adding REPACK [concurrently]