fallback if no other solution is possible. If a replica identity other
than <quote>full</quote> is set on the publisher side, a replica identity
comprising the same or fewer columns must also be set on the subscriber
- side. See <xref linkend="sql-createtable-replica-identity"/> for details on
+ side. See <xref linkend="sql-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 <command>UPDATE</command>
or <command>DELETE</command> operations then
by <command>INSERT</command> and the new row version created
by <command>UPDATE</command>. Availability of old row versions for
<command>UPDATE</command> and <command>DELETE</command> depends on
- the configured replica identity (see <xref linkend="sql-createtable-replica-identity"/>).
+ the configured replica identity (see <xref linkend="sql-altertable-replica-identity"/>).
</para>
<para>
</listitem>
</varlistentry>
- <varlistentry id="sql-createtable-replica-identity">
+ <varlistentry id="sql-altertable-replica-identity">
<term><literal>REPLICA IDENTITY</literal></term>
<listitem>
<para>
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
- <link linkend="sql-createtable-replica-identity">replica
+ <link linkend="sql-altertable-replica-identity">replica
identity</link> setting and the
<link linkend="sql-create-access-method">access method</link> name
if the relation has an access method.