| From: | Artur Zakirov <zaartur(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_dump crash on identity sequence with not loaded attributes |
| Date: | 2024-12-11 21:41:16 |
| Message-ID: | CAKNkYnzRS0YG-e0iKdLQns=EBm67qDHS=Dcf-2o_QsJnHW52LQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, 11 Dec 2024 at 16:48, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Niklas Hambüchen | 2024-12-11 21:59:41 | "memory exhausted" in query parser/simplifier for many nested parentheses |
| Previous Message | Daniel Gustafsson | 2024-12-11 21:18:05 | Re: BUG #18745: /src/bin/pg_waldump/compat.c |