diff options
Diffstat (limited to 'doc/src/sgml/ref/alter_table.sgml')
| -rw-r--r-- | doc/src/sgml/ref/alter_table.sgml | 32 |
1 files changed, 16 insertions, 16 deletions
diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml index f034e75ec09..c25ef5abd6a 100644 --- a/doc/src/sgml/ref/alter_table.sgml +++ b/doc/src/sgml/ref/alter_table.sgml @@ -152,7 +152,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM <listitem> <para> This form adds a new column to the table, using the same syntax as - <xref linkend="sql-createtable"/>. If <literal>IF NOT EXISTS</literal> + <link linkend="sql-createtable"><command>CREATE TABLE</command></link>. If <literal>IF NOT EXISTS</literal> is specified and a column already exists with this name, no error is thrown. </para> @@ -268,7 +268,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM <para> These forms change whether a column is an identity column or change the generation attribute of an existing identity column. - See <xref linkend="sql-createtable"/> for details. + See <link linkend="sql-createtable"><command>CREATE TABLE</command></link> for details. Like <literal>SET DEFAULT</literal>, these forms only affect the behavior of subsequent <command>INSERT</command> and <command>UPDATE</command> commands; they do not cause rows @@ -290,7 +290,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM <para> These forms alter the sequence that underlies an existing identity column. <replaceable>sequence_option</replaceable> is an option - supported by <xref linkend="sql-altersequence"/> such + supported by <link linkend="sql-altersequence"><command>ALTER SEQUENCE</command></link> such as <literal>INCREMENT BY</literal>. </para> </listitem> @@ -302,7 +302,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM <para> This form sets the per-column statistics-gathering target for subsequent - <xref linkend="sql-analyze"/> operations. + <link linkend="sql-analyze"><command>ANALYZE</command></link> operations. The target can be set in the range 0 to 10000; alternatively, set it to -1 to revert to using the system default statistics target (<xref linkend="guc-default-statistics-target"/>). @@ -326,7 +326,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM defined per-attribute options are <literal>n_distinct</literal> and <literal>n_distinct_inherited</literal>, which override the number-of-distinct-values estimates made by subsequent - <xref linkend="sql-analyze"/> + <link linkend="sql-analyze"><command>ANALYZE</command></link> operations. <literal>n_distinct</literal> affects the statistics for the table itself, while <literal>n_distinct_inherited</literal> affects the statistics gathered for the table plus its inheritance children. When set to a @@ -388,7 +388,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM <listitem> <para> This form adds a new constraint to a table using the same constraint - syntax as <xref linkend="sql-createtable"/>, plus the option <literal>NOT + syntax as <link linkend="sql-createtable"><command>CREATE TABLE</command></link>, plus the option <literal>NOT VALID</literal>, which is currently only allowed for foreign key and CHECK constraints. </para> @@ -422,7 +422,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM <para> Additional restrictions apply when unique or primary key constraints - are added to partitioned tables; see <xref linkend="sql-createtable"/>. + are added to partitioned tables; see <link linkend="sql-createtable"><command>CREATE TABLE</command></link>. Also, foreign key constraints on partitioned tables may not be declared <literal>NOT VALID</literal> at present. </para> @@ -598,7 +598,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM even if row level security is disabled. In this case, the policies will <emphasis>not</emphasis> be applied and the policies will be ignored. See also - <xref linkend="sql-createpolicy"/>. + <link linkend="sql-createpolicy"><command>CREATE POLICY</command></link>. </para> </listitem> </varlistentry> @@ -613,7 +613,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM disabled (the default) then row level security will not be applied when the user is the table owner. See also - <xref linkend="sql-createpolicy"/>. + <link linkend="sql-createpolicy"><command>CREATE POLICY</command></link>. </para> </listitem> </varlistentry> @@ -623,7 +623,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM <listitem> <para> This form selects the default index for future - <xref linkend="sql-cluster"/> + <link linkend="sql-cluster"><command>CLUSTER</command></link> operations. It does not actually re-cluster the table. </para> <para> @@ -637,7 +637,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM <listitem> <para> This form removes the most recently used - <xref linkend="sql-cluster"/> + <link linkend="sql-cluster"><command>CLUSTER</command></link> index specification from the table. This affects future cluster operations that don't specify an index. </para> @@ -685,7 +685,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM <literal>information_schema</literal> relations are not considered part of the system catalogs and will be moved. See also - <xref linkend="sql-createtablespace"/>. + <link linkend="sql-createtablespace"><command>CREATE TABLESPACE</command></link>. </para> </listitem> </varlistentry> @@ -707,12 +707,12 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM <para> This form changes one or more storage parameters for the table. See <xref linkend="sql-createtable-storage-parameters"/> in the - <xref linkend="sql-createtable"/> documentation + <link linkend="sql-createtable"><command>CREATE TABLE</command></link> documentation for details on the available parameters. Note that the table contents will not be modified immediately by this command; depending on the parameter you might need to rewrite the table to get the desired effects. - That can be done with <link linkend="sql-vacuum">VACUUM - FULL</link>, <xref linkend="sql-cluster"/> or one of the forms + That can be done with <link linkend="sql-vacuum"><command>VACUUM + FULL</command></link>, <link linkend="sql-cluster"><command>CLUSTER</command></link> or one of the forms of <command>ALTER TABLE</command> that forces a table rewrite. For planner related parameters, changes will take effect from the next time the table is locked so currently executing queries will not be @@ -878,7 +878,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM <para> A partition using <literal>FOR VALUES</literal> uses same syntax for <replaceable class="parameter">partition_bound_spec</replaceable> as - <xref linkend="sql-createtable"/>. The partition bound specification + <link linkend="sql-createtable"><command>CREATE TABLE</command></link>. The partition bound specification must correspond to the partitioning strategy and partition key of the target table. The table to be attached must have all the same columns as the target table and no more; moreover, the column types must also |