Re: Patch: dumping tables data in multiple chunks in pg_dump - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Patch: dumping tables data in multiple chunks in pg_dump
Date
Msg-id iqhlowrl7c7cmu3e35vzg65qf3rccilvpo7eeymh7pakp3xdqw@gh322zepbst6
Whole thread Raw
In response to Re: Patch: dumping tables data in multiple chunks in pg_dump  (Hannu Krosing <hannuk@google.com>)
Responses Re: Patch: dumping tables data in multiple chunks in pg_dump
List 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?



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: AIX support
Next
From: Andres Freund
Date:
Subject: Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta