From c765ba9d094d1e815dee61036731565539be43da Mon Sep 17 00:00:00 2001 From: Peter Smith Date: Tue, 7 Mar 2023 18:15:27 +1100 Subject: [PATCH v1] PGDOCS - replica identity quotes --- doc/src/sgml/logical-replication.sgml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml index 1bd5660..caaf46c 100644 --- a/doc/src/sgml/logical-replication.sgml +++ b/doc/src/sgml/logical-replication.sgml @@ -124,17 +124,17 @@ - A published table must have a replica identity configured in + A published table must have a replica identity configured in order to be able to replicate UPDATE and DELETE operations, so that appropriate rows to update or delete can be identified on the subscriber side. By default, this is the primary key, if there is one. Another unique index (with certain additional requirements) can also be set to be the replica identity. If the table does not have any suitable key, then it can be set - to replica identity full, which means the entire row becomes + to replica identity FULL, which means the entire row becomes the key. This, however, is very inefficient and should only be used as a fallback if no other solution is possible. If a replica identity other - than full is set on the publisher side, a replica identity + than FULL is set on the publisher side, a replica identity comprising the same or fewer columns must also be set on the subscriber side. See for details on how to set the replica identity. If a table without a replica identity is -- 1.8.3.1