From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Cc: | kdg(dot)dev(at)gmail(dot)com |
Subject: | Unclear on Publication documentation page |
Date: | 2024-05-18 20:44:47 |
Message-ID: | 171606508791.686.3944833439498473045@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/logical-replication-publication.html
Description:
The page in question:
https://www.postgresql.org/docs/current/logical-replication-publication.html
It says:
"If a table without a replica identity is added to a publication that
replicates UPDATE or DELETE operations then subsequent UPDATE or DELETE
operations will cause an error on the publisher. INSERT operations can
proceed regardless of any replica identity."
The text is ambiguous as to what is meant by "the publisher" in "will cause
an error on the publisher". I've personally never set up logical
replication, which is why I'm reading the documentation now.
The question for me is: Does "the publisher" refer to a logical entity,
created by the "CREATE PUBLICATION " command? And further publication in the
publication<->subscriber model will not work anymore? Or does it refer to
the actual database itself, and will the functionality of the database be
impacted? As in: your live production database can now no longer process
UPDATE and DELETE statements so long as that publication exists/so long as
that publication is configured to publish that particular table?
Regards,
Koen De Groote
From | Date | Subject | |
---|---|---|---|
Next Message | PG Doc comments form | 2024-05-18 21:02:11 | Logical replication - initial data synchronization |
Previous Message | Igor Gnatyuk | 2024-05-17 08:39:35 | Re: Add small detail to RAISE statement descripton |