| From: | Peter Smith <smithpb2250(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | DOC: pg_publication_rel.prrelid says sequences are possible |
| Date: | 2026-04-01 04:59:54 |
| Message-ID: | CAHut+Pv1UKR_bxmN7wcCCpQveHoYprvH-hbdFq8gsaH1Ye7B_w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi.
It is my understanding that only tables can exist in the
'pg_publication_rel' catalog.
e.g. only for these scenarios:
* included tables - when pg_publication.puballtables is false, these
are the specified FOR TABLE ... tables
* excluded tables - when pg_publication.puballtables is true, these
are the specified FOR ALL TABLES EXCEPT (TABLE ...) tables
In particular, AFAIK there is no way for sequences to be in the
'pg_publication_rel' catalog. e.g.
PG19 only supports "CREATE PUBLICATION ... FOR ALL SEQUENCES", which
is indicated by pg_publication.puballsequences.
PG19 has no support for "CREATE PUBLICATION ... FOR SEQUENCE seq1,seq2".
~~
Meanwhile, the DOCS page for 'pg_publication_rel' catalog [1] since
commit 55cefad says that sequences are also possible [2]:
------
prrelid oid (references pg_class.oid)
Reference to table or sequence
------
How are sequences possible? PSA a patch to correct it.
Or, am I mistaken here?
======
[1] https://www.postgresql.org/docs/devel/catalog-pg-publication-rel.html
[2] https://github.com/postgres/postgres/commit/55cefadde874e52b57f7b3c2232744e331f9d6bb#diff-686ae8747787a3c04698ca610350c2b7dc84618c5b28d4b90e94f6f8cd47bd8eR6571
Kind Regards,
Peter Smith.
Fujitsu Australia
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-DOCS-pg_publication_rel.prrelid.patch | application/octet-stream | 843 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nisha Moond | 2026-04-01 05:03:43 | Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? |
| Previous Message | Amit Kapila | 2026-04-01 04:56:53 | Re: [Proposal] Adding Log File Capability to pg_createsubscriber |