Horton

Re: pg_dump crash on identity sequence with not loaded attributes

Artur Zakirov <zaartur@gmail.com>

View thread View on postgr.es
From: Artur Zakirov <zaartur@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter@eisentraut.org>, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2024-12-11T21:41:16Z
Lists: pgsql-bugs 
On Wed, 11 Dec 2024 at 16:48, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> In any case, that's mostly orthogonal to the problem with identity
> sequences.  I now propose leaving out that change and just pushing
> the change in getOwnedSeqs().  The publication-namespace business
> should be discussed on its own thread.

+1, agree it looks like a bit different issue and for now we can fix
only the issue with sequences.

I found another inconsistency with publishing mapping and just mention
it here. According to the code of selectDumpableNamespace() namespaces
"pg_*" and "information_schema" are ignored by pg_dump. But it is
possible to create mapping for publications with "information_schema"
and those mappings will be lost by dump/restore. But I agree that
publication-namespace should have its own thread.

-- 
Kind regards,
Artur

Commits

  1. Fix possible crash in pg_dump with identity sequences.

  2. Do not dump identity sequences with excluded parent table