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 14:52:21
Message-ID: abgZJZx27gmAtLHr@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Mar 15, 2026 at 12:20:41PM -0400, Tom Lane wrote:
> 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.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Melanie Plageman 2026-03-16 14:53:32 Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access)
Previous Message Fujii Masao 2026-03-16 14:49:01 Re: Add missing stats_reset column to pg_statio_all_sequences view