Re: Patch: dumping tables data in multiple chunks in pg_dump

Andres Freund <andres@anarazel.de>

From: Andres Freund <andres@anarazel.de>
To: Hannu Krosing <hannuk@google.com>
Cc: David Rowley <dgrowleyml@gmail.com>, Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Nathan Bossart <nathandbossart@gmail.com>
Date: 2026-01-14T21:40:21Z
Lists: pgsql-hackers
On 2026-01-14 11:52:54 +0100, Hannu Krosing wrote:
> On Tue, Jan 13, 2026 at 3:32 AM David Rowley <dgrowleyml@gmail.com> wrote:
> >
> > On Fri, 14 Nov 2025 at 09:34, Hannu Krosing <hannuk@google.com> wrote:
> > > Added to https://commitfest.postgresql.org/patch/6219/
> >
> > I see you added the "Backport" tag in the CF. This isn't the sort of
> > thing that we'd do that for. Was that a mistake?
> 
> Just wanted to mark it as something that might be backported later as
> one of the important cases for pg_dump is dumping older databases .

I think it's obvious that nothing that's being discussed here has any business
being considered for backporting.

Nor can I follow the argument that dumping of old databases would be an
argument, as the proposed change is in pg_dump, not the server, so a new
pg_dump will suffice to get the benefit, no?