Re: pg_dump crash on identity sequence with not loaded attributes - Mailing list pgsql-bugs

From Artur Zakirov
Subject Re: pg_dump crash on identity sequence with not loaded attributes
Date
Msg-id CAKNkYnzRS0YG-e0iKdLQns=EBm67qDHS=Dcf-2o_QsJnHW52LQ@mail.gmail.com
Whole thread Raw
In response to Re: pg_dump crash on identity sequence with not loaded attributes  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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



pgsql-bugs by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: BUG #18745: /src/bin/pg_waldump/compat.c
Next
From: Niklas Hambüchen
Date:
Subject: "memory exhausted" in query parser/simplifier for many nested parentheses