fallback if no other solution is possible. If a replica identity other
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 createtable-replica-identity"/> for details on
+ side. See altertable-replica-identity"/> for details on
how to set the replica identity. If a table without a replica identity is
added to a publication that replicates UPDATE
or DELETE operations then
by INSERT and the new row version created
by UPDATE. Availability of old row versions for
UPDATE and DELETE depends on
- the configured replica identity (see createtable-replica-identity"/>).
+ the configured replica identity (see altertable-replica-identity"/>).
- createtable-replica-identity">
+ altertable-replica-identity">
REPLICA IDENTITY
more information is displayed: any comments associated with the
columns of the table are shown, as is the presence of OIDs in the
table, the view definition if the relation is a view, a non-default
- createtable-replica-identity">replica
+ altertable-replica-identity">replica
identity setting and the
access method name
if the relation has an access method.