mirrors
/
postgres
mirror of https://github.com/postgres/postgres
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Convert SGML IDs to lower case 

IDs in SGML are case insensitive, and we have accumulated a mix of upper
and lower case IDs, including different variants of the same ID.  In
XML, these will be case sensitive, so we need to fix up those
differences.  Going to all lower case seems most straightforward, and
the current build process already makes all anchors and lower case
anyway during the SGML->XML conversion, so this doesn't create any
difference in the output right now.  A future XML-only build process
would, however, maintain any mixed case ID spellings in the output, so
that is another reason to clean this up beforehand.

Author: Alexander Lakhin <exclusion@gmail.com>
This commit is contained in:
Peter Eisentraut 2017-10-19 21:16:39 -04:00
parent 36ea99c84d
commit 1ff01b3902
234 changed files with 925 additions and 925 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/src/sgml/acronyms.sgml
View File

@ -232,7 +232,7 @@
<term><acronym>GIN</acronym></term>
<listitem>
<para>
<link linkend="GIN">Generalized Inverted Index</link>
<link linkend="gin">Generalized Inverted Index</link>
</para>
</listitem>
</varlistentry>
@ -241,7 +241,7 @@
<term><acronym>GiST</acronym></term>
<listitem>
<para>
<link linkend="GiST">Generalized Search Tree</link>
<link linkend="gist">Generalized Search Tree</link>
</para>
</listitem>
</varlistentry>
@ -583,7 +583,7 @@
<term><acronym>SP-GiST</acronym></term>
<listitem>
<para>
<link linkend="SPGiST">Space-Partitioned Generalized Search Tree</link>
<link linkend="spgist">Space-Partitioned Generalized Search Tree</link>
</para>
</listitem>
</varlistentry>

2
doc/src/sgml/arch-dev.sgml
View File

@ -7,7 +7,7 @@
<title>Author</title>
<para>
This chapter originated as part of
<xref linkend="SIM98">, Stefan Simkovics'
<xref linkend="sim98">, Stefan Simkovics'
Master's Thesis prepared at Vienna University of Technology under the direction
of O.Univ.Prof.Dr. Georg Gottlob and Univ.Ass. Mag. Katrin Seyr.
</para>

40
doc/src/sgml/biblio.sgml
View File

@ -18,7 +18,7 @@
<bibliodiv>
<title><acronym>SQL</acronym> Reference Books</title>
<biblioentry id="BOWMAN01">
<biblioentry id="bowman01">
<title>The Practical <acronym>SQL</acronym> Handbook</title>
<subtitle>Using SQL Variants</subtitle>
<edition>Fourth Edition</edition>
@ -43,7 +43,7 @@
<pubdate>2001</pubdate>
</biblioentry>
<biblioentry id="DATE97">
<biblioentry id="date97">
<title>A Guide to the <acronym>SQL</acronym> Standard</title>
<subtitle>A user's guide to the standard database language <acronym>SQL</acronym></subtitle>
<edition>Fourth Edition</edition>
@ -64,7 +64,7 @@
<pubdate>1997</pubdate>
</biblioentry>
<biblioentry id="DATE04">
<biblioentry id="date04">
<title>An Introduction to Database Systems</title>
<edition>Eighth Edition</edition>
<authorgroup>
@ -80,7 +80,7 @@
<pubdate>2003</pubdate>
</biblioentry>
<biblioentry id="ELMA04">
<biblioentry id="elma04">
<title>Fundamentals of Database Systems</title>
<edition>Fourth Edition</edition>
<authorgroup>
@ -100,7 +100,7 @@
<pubdate>2003</pubdate>
</biblioentry>
<biblioentry id="MELT93">
<biblioentry id="melt93">
<title>Understanding the New <acronym>SQL</acronym></title>
<subtitle>A complete guide</subtitle>
<authorgroup>
@ -120,7 +120,7 @@
<pubdate>1993</pubdate>
</biblioentry>
<biblioentry id="ULL88">
<biblioentry id="ull88">
<title>Principles of Database and Knowledge</title>
<subtitle>Base Systems</subtitle>
<authorgroup>
@ -141,7 +141,7 @@
<bibliodiv>
<title>PostgreSQL-specific Documentation</title>
<biblioentry id="SIM98">
<biblioentry id="sim98">
<title>Enhancement of the ANSI SQL Implementation of PostgreSQL</title>
<authorgroup>
<author>
@ -185,7 +185,7 @@ ssimkovi@ag.or.at
<pubdate>November 29, 1998</pubdate>
</biblioentry>
<biblioentry id="YU95">
<biblioentry id="yu95">
<title>The <productname>Postgres95</productname> User Manual</title>
<authorgroup>
<author>
@ -204,7 +204,7 @@ ssimkovi@ag.or.at
<pubdate>Sept. 5, 1995</pubdate>
</biblioentry>
<biblioentry id="FONG">
<biblioentry id="fong">
<title><ulink url="http://db.cs.berkeley.edu/papers/UCB-MS-zfong.pdf">The
design and implementation of the <productname>POSTGRES</productname> query
optimizer</ulink></title>
@ -222,7 +222,7 @@ ssimkovi@ag.or.at
<bibliodiv>
<title>Proceedings and Articles</title>
<biblioentry id="OLSON93">
<biblioentry id="olson93">
<title>Partial indexing in POSTGRES: research project</title>
<authorgroup>
<author>
@ -238,7 +238,7 @@ ssimkovi@ag.or.at
<pubdate>1993</pubdate>
</biblioentry>
<biblioentry id="ONG90">
<biblioentry id="ong90">
<biblioset relation="article">
<title>A Unified Framework for Version Modeling Using Production Rules in a Database System</title>
<authorgroup>
@ -262,7 +262,7 @@ ssimkovi@ag.or.at
</biblioset>
</biblioentry>
<biblioentry id="ROWE87">
<biblioentry id="rowe87">
<biblioset relation="article">
<title><ulink url="http://db.cs.berkeley.edu/papers/ERL-M87-13.pdf">The <productname>POSTGRES</productname>
data model</ulink></title>
@ -284,7 +284,7 @@ ssimkovi@ag.or.at
</confgroup>
</biblioentry>
<biblioentry id="SESHADRI95">
<biblioentry id="seshadri95">
<biblioset relation="article">
<title><ulink url="http://citeseer.ist.psu.edu/seshadri95generalized.html">Generalized
Partial Indexes</ulink></title>
@ -313,7 +313,7 @@ ssimkovi@ag.or.at
<pagenums>420-7</pagenums>
</biblioentry>
<biblioentry id="STON86">
<biblioentry id="ston86">
<biblioset relation="article">
<title><ulink url="http://db.cs.berkeley.edu/papers/ERL-M85-95.pdf">The
design of <productname>POSTGRES</productname></ulink></title>
@ -335,7 +335,7 @@ ssimkovi@ag.or.at
</confgroup>
</biblioentry>
<biblioentry id="STON87a">
<biblioentry id="ston87a">
<biblioset relation="article">
<title>The design of the <productname>POSTGRES</productname> rules system</title>
<authorgroup>
@ -360,7 +360,7 @@ ssimkovi@ag.or.at
</confgroup>
</biblioentry>
<biblioentry id="STON87b">
<biblioentry id="ston87b">
<biblioset relation="article">
<title><ulink url="http://db.cs.berkeley.edu/papers/ERL-M87-06.pdf">The
design of the <productname>POSTGRES</productname> storage
@ -379,7 +379,7 @@ ssimkovi@ag.or.at
</confgroup>
</biblioentry>
<biblioentry id="STON89">
<biblioentry id="ston89">
<biblioset relation="article">
<title><ulink url="http://db.cs.berkeley.edu/papers/ERL-M89-82.pdf">A
commentary on the <productname>POSTGRES</productname> rules
@ -405,7 +405,7 @@ ssimkovi@ag.or.at
</biblioset>
</biblioentry>
<biblioentry id="STON89b">
<biblioentry id="ston89b">
<biblioset relation="article">
<title><ulink url="http://db.cs.berkeley.edu/papers/ERL-M89-17.pdf">The
case for partial indexes</ulink></title>
@ -423,7 +423,7 @@ ssimkovi@ag.or.at
</biblioset>
</biblioentry>
<biblioentry id="STON90a">
<biblioentry id="ston90a">
<biblioset relation="article">
<title><ulink url="http://db.cs.berkeley.edu/papers/ERL-M90-34.pdf">The
implementation of <productname>POSTGRES</productname></ulink></title>
@ -451,7 +451,7 @@ ssimkovi@ag.or.at
</biblioset>
</biblioentry>
<biblioentry id="STON90b">
<biblioentry id="ston90b">
<biblioset relation="article">
<title><ulink url="http://db.cs.berkeley.edu/papers/ERL-M90-36.pdf">On
Rules, Procedures, Caching and Views in Database Systems</ulink></title>

2
doc/src/sgml/brin.sgml
View File

@ -1,6 +1,6 @@
<!-- doc/src/sgml/brin.sgml -->
<chapter id="BRIN">
<chapter id="brin">
<title>BRIN Indexes</title>
<indexterm>

4
doc/src/sgml/btree-gist.sgml
View File

@ -36,7 +36,7 @@
In addition to the typical B-tree search operators, <filename>btree_gist</filename>
also provides index support for <literal>&lt;&gt;</literal> (<quote>not
equals</quote>). This may be useful in combination with an
<link linkend="SQL-CREATETABLE-EXCLUDE">exclusion constraint</link>,
<link linkend="sql-createtable-exclude">exclusion constraint</link>,
as described below.
</para>
@ -70,7 +70,7 @@ SELECT *, a &lt;-&gt; 42 AS dist FROM test ORDER BY a &lt;-&gt; 42 LIMIT 10;
</programlisting>
<para>
Use an <link linkend="SQL-CREATETABLE-EXCLUDE">exclusion
Use an <link linkend="sql-createtable-exclude">exclusion
constraint</link> to enforce the rule that a cage at a zoo
can contain only one kind of animal:
</para>

18
doc/src/sgml/config.sgml
View File

@ -170,7 +170,7 @@ shared_buffers = 128MB
<filename>postgresql.auto.conf</filename><indexterm><primary>postgresql.auto.conf</primary></indexterm>,
which has the same format as <filename>postgresql.conf</filename> but should
never be edited manually. This file holds settings provided through
the <xref linkend="SQL-ALTERSYSTEM"> command. This file is automatically
the <xref linkend="sql-altersystem"> command. This file is automatically
read whenever <filename>postgresql.conf</filename> is, and its settings take
effect in the same way. Settings in <filename>postgresql.auto.conf</filename>
override those in <filename>postgresql.conf</filename>.
@ -191,7 +191,7 @@ shared_buffers = 128MB
<para>
<productname>PostgreSQL</productname> provides three SQL
commands to establish configuration defaults.
The already-mentioned <xref linkend="SQL-ALTERSYSTEM"> command
The already-mentioned <xref linkend="sql-altersystem"> command
provides a SQL-accessible means of changing global defaults; it is
functionally equivalent to editing <filename>postgresql.conf</filename>.
In addition, there are two commands that allow setting of defaults
@ -232,7 +232,7 @@ shared_buffers = 128MB
<itemizedlist>
<listitem>
<para>
The <xref linkend="SQL-SHOW"> command allows inspection of the
The <xref linkend="sql-show"> command allows inspection of the
current value of all parameters. The corresponding function is
<function>current_setting(setting_name text)</function>.
</para>
@ -240,7 +240,7 @@ shared_buffers = 128MB
<listitem>
<para>
The <xref linkend="SQL-SET"> command allows modification of the
The <xref linkend="sql-set"> command allows modification of the
current value of those parameters that can be set locally to a
session; it has no effect on other sessions.
The corresponding function is
@ -266,7 +266,7 @@ shared_buffers = 128MB
<listitem>
<para>
Using <xref linkend="SQL-UPDATE"> on this view, specifically
Using <xref linkend="sql-update"> on this view, specifically
updating the <structname>setting</structname> column, is the equivalent
of issuing <command>SET</command> commands. For example, the equivalent of
<programlisting>
@ -6237,7 +6237,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
<para>
For more information on row security policies,
see <xref linkend="SQL-CREATEPOLICY">.
see <xref linkend="sql-createpolicy">.
</para>
</listitem>
</varlistentry>
@ -7040,7 +7040,7 @@ SET XML OPTION { DOCUMENT | CONTENT };
This variable specifies one or more shared libraries that are to be
preloaded at connection start.
It contains a comma-separated list of library names, where each name
is interpreted as for the <xref linkend="SQL-LOAD"> command.
is interpreted as for the <xref linkend="sql-load"> command.
Whitespace between entries is ignored; surround a library name with
double quotes if you need to include whitespace or commas in the name.
The parameter value only takes effect at the start of the connection.
@ -7091,7 +7091,7 @@ SET XML OPTION { DOCUMENT | CONTENT };
This variable specifies one or more shared libraries that are to be
preloaded at connection start.
It contains a comma-separated list of library names, where each name
is interpreted as for the <xref linkend="SQL-LOAD"> command.
is interpreted as for the <xref linkend="sql-load"> command.
Whitespace between entries is ignored; surround a library name with
double quotes if you need to include whitespace or commas in the name.
The parameter value only takes effect at the start of the connection.
@ -7133,7 +7133,7 @@ SET XML OPTION { DOCUMENT | CONTENT };
This variable specifies one or more shared libraries to be preloaded at
server start.
It contains a comma-separated list of library names, where each name
is interpreted as for the <xref linkend="SQL-LOAD"> command.
is interpreted as for the <xref linkend="sql-load"> command.
Whitespace between entries is ignored; surround a library name with
double quotes if you need to include whitespace or commas in the name.
This parameter can only be set at server start. If a specified

38
doc/src/sgml/dblink.sgml
View File

@ -18,7 +18,7 @@
functionality using a more modern and standards-compliant infrastructure.
</para>
<refentry id="CONTRIB-DBLINK-CONNECT">
<refentry id="contrib-dblink-connect">
<indexterm>
<primary>dblink_connect</primary>
</indexterm>
@ -182,7 +182,7 @@ DROP SERVER fdtest;
</refsect1>
</refentry>
<refentry id="CONTRIB-DBLINK-CONNECT-U">
<refentry id="contrib-dblink-connect-u">
<indexterm>
<primary>dblink_connect_u</primary>
</indexterm>
@ -239,7 +239,7 @@ dblink_connect_u(text connname, text connstr) returns text
</refsect1>
</refentry>
<refentry id="CONTRIB-DBLINK-DISCONNECT">
<refentry id="contrib-dblink-disconnect">
<indexterm>
<primary>dblink_disconnect</primary>
</indexterm>
@ -314,7 +314,7 @@ SELECT dblink_disconnect('myconn');
</refsect1>
</refentry>
<refentry id="CONTRIB-DBLINK-FUNCTION">
<refentry id="contrib-dblink-function">
<indexterm>
<primary>dblink</primary>
</indexterm>
@ -532,7 +532,7 @@ SELECT * FROM dblink('myconn', 'select proname, prosrc from pg_proc')
</refsect1>
</refentry>
<refentry id="CONTRIB-DBLINK-EXEC">
<refentry id="contrib-dblink-exec">
<indexterm>
<primary>dblink_exec</primary>
</indexterm>
@ -669,7 +669,7 @@ DETAIL: ERROR: null value in column "relnamespace" violates not-null constrain
</refsect1>
</refentry>
<refentry id="CONTRIB-DBLINK-OPEN">
<refentry id="contrib-dblink-open">
<indexterm>
<primary>dblink_open</primary>
</indexterm>
@ -793,7 +793,7 @@ SELECT dblink_open('foo', 'select proname, prosrc from pg_proc');
</refsect1>
</refentry>
<refentry id="CONTRIB-DBLINK-FETCH">
<refentry id="contrib-dblink-fetch">
<indexterm>
<primary>dblink_fetch</primary>
</indexterm>
@ -946,7 +946,7 @@ SELECT * FROM dblink_fetch('foo', 5) AS (funcname name, source text);
</refsect1>
</refentry>
<refentry id="CONTRIB-DBLINK-CLOSE">
<refentry id="contrib-dblink-close">
<indexterm>
<primary>dblink_close</primary>
</indexterm>
@ -1057,7 +1057,7 @@ SELECT dblink_close('foo');
</refsect1>
</refentry>
<refentry id="CONTRIB-DBLINK-GET-CONNECTIONS">
<refentry id="contrib-dblink-get-connections">
<indexterm>
<primary>dblink_get_connections</primary>
</indexterm>
@ -1102,7 +1102,7 @@ SELECT dblink_get_connections();
</refsect1>
</refentry>
<refentry id="CONTRIB-DBLINK-ERROR-MESSAGE">
<refentry id="contrib-dblink-error-message">
<indexterm>
<primary>dblink_error_message</primary>
</indexterm>
@ -1165,7 +1165,7 @@ SELECT dblink_error_message('dtest1');
</refsect1>
</refentry>
<refentry id="CONTRIB-DBLINK-SEND-QUERY">
<refentry id="contrib-dblink-send-query">
<indexterm>
<primary>dblink_send_query</primary>
</indexterm>
@ -1247,7 +1247,7 @@ SELECT dblink_send_query('dtest1', 'SELECT * FROM foo WHERE f1 &lt; 3');
</refsect1>
</refentry>
<refentry id="CONTRIB-DBLINK-IS-BUSY">
<refentry id="contrib-dblink-is-busy">
<indexterm>
<primary>dblink_is_busy</primary>
</indexterm>
@ -1310,7 +1310,7 @@ SELECT dblink_is_busy('dtest1');
</refsect1>
</refentry>
<refentry id="CONTRIB-DBLINK-GET-NOTIFY">
<refentry id="contrib-dblink-get-notify">
<indexterm>
<primary>dblink_get_notify</primary>
</indexterm>
@ -1392,7 +1392,7 @@ SELECT * FROM dblink_get_notify();
</refsect1>
</refentry>
<refentry id="CONTRIB-DBLINK-GET-RESULT">
<refentry id="contrib-dblink-get-result">
<indexterm>
<primary>dblink_get_result</primary>
</indexterm>
@ -1556,7 +1556,7 @@ contrib_regression=# SELECT * FROM dblink_get_result('dtest1') AS t1(f1 int, f2
</refsect1>
</refentry>
<refentry id="CONTRIB-DBLINK-CANCEL-QUERY">
<refentry id="contrib-dblink-cancel-query">
<indexterm>
<primary>dblink_cancel_query</primary>
</indexterm>
@ -1624,7 +1624,7 @@ SELECT dblink_cancel_query('dtest1');
</refsect1>
</refentry>
<refentry id="CONTRIB-DBLINK-GET-PKEY">
<refentry id="contrib-dblink-get-pkey">
<indexterm>
<primary>dblink_get_pkey</primary>
</indexterm>
@ -1716,7 +1716,7 @@ SELECT * FROM dblink_get_pkey('foobar');
</refsect1>
</refentry>
<refentry id="CONTRIB-DBLINK-BUILD-SQL-INSERT">
<refentry id="contrib-dblink-build-sql-insert">
<indexterm>
<primary>dblink_build_sql_insert</primary>
</indexterm>
@ -1851,7 +1851,7 @@ SELECT dblink_build_sql_insert('foo', '1 2', 2, '{"1", "a"}', '{"1", "b''a"}');
</refsect1>
</refentry>
<refentry id="CONTRIB-DBLINK-BUILD-SQL-DELETE">
<refentry id="contrib-dblink-build-sql-delete">
<indexterm>
<primary>dblink_build_sql_delete</primary>
</indexterm>
@ -1969,7 +1969,7 @@ SELECT dblink_build_sql_delete('"MyFoo"', '1 2', 2, '{"1", "b"}');
</refsect1>
</refentry>
<refentry id="CONTRIB-DBLINK-BUILD-SQL-UPDATE">
<refentry id="contrib-dblink-build-sql-update">
<indexterm>
<primary>dblink_build_sql_update</primary>
</indexterm>

2
doc/src/sgml/ddl.sgml
View File

@ -908,7 +908,7 @@ CREATE TABLE circles (
</para>
<para>
See also <link linkend="SQL-CREATETABLE-EXCLUDE"><command>CREATE
See also <link linkend="sql-createtable-exclude"><command>CREATE
TABLE ... CONSTRAINT ... EXCLUDE</command></link> for details.
</para>

70
doc/src/sgml/ecpg.sgml
View File

@ -2270,7 +2270,7 @@ int PGTYPESnumeric_from_decimal(decimal *src, numeric *dst);
<para>
The following functions can be used to work with the date type:
<variablelist>
<varlistentry id="PGTYPESdatefromtimestamp">
<varlistentry id="pgtypesdatefromtimestamp">
<term><function>PGTYPESdate_from_timestamp</function></term>
<listitem>
<para>
@ -2284,7 +2284,7 @@ date PGTYPESdate_from_timestamp(timestamp dt);
</listitem>
</varlistentry>
<varlistentry id="PGTYPESdatefromasc">
<varlistentry id="pgtypesdatefromasc">
<term><function>PGTYPESdate_from_asc</function></term>
<listitem>
<para>
@ -2389,7 +2389,7 @@ date PGTYPESdate_from_asc(char *str, char **endptr);
</listitem>
</varlistentry>
<varlistentry id="PGTYPESdatetoasc">
<varlistentry id="pgtypesdatetoasc">
<term><function>PGTYPESdate_to_asc</function></term>
<listitem>
<para>
@ -2404,7 +2404,7 @@ char *PGTYPESdate_to_asc(date dDate);
</listitem>
</varlistentry>
<varlistentry id="PGTYPESdatejulmdy">
<varlistentry id="pgtypesdatejulmdy">
<term><function>PGTYPESdate_julmdy</function></term>
<listitem>
<para>
@ -2423,7 +2423,7 @@ void PGTYPESdate_julmdy(date d, int *mdy);
</listitem>
</varlistentry>
<varlistentry id="PGTYPESdatemdyjul">
<varlistentry id="pgtypesdatemdyjul">
<term><function>PGTYPESdate_mdyjul</function></term>
<listitem>
<para>
@ -2439,7 +2439,7 @@ void PGTYPESdate_mdyjul(int *mdy, date *jdate);
</listitem>
</varlistentry>
<varlistentry id="PGTYPESdatedayofweek">
<varlistentry id="pgtypesdatedayofweek">
<term><function>PGTYPESdate_dayofweek</function></term>
<listitem>
<para>
@ -2491,7 +2491,7 @@ int PGTYPESdate_dayofweek(date d);
</listitem>
</varlistentry>
<varlistentry id="PGTYPESdatetoday">
<varlistentry id="pgtypesdatetoday">
<term><function>PGTYPESdate_today</function></term>
<listitem>
<para>
@ -2505,7 +2505,7 @@ void PGTYPESdate_today(date *d);
</listitem>
</varlistentry>
<varlistentry id="PGTYPESdatefmtasc">
<varlistentry id="pgtypesdatefmtasc">
<term><function>PGTYPESdate_fmt_asc</function></term>
<listitem>
<para>
@ -2626,7 +2626,7 @@ int PGTYPESdate_fmt_asc(date dDate, char *fmtstring, char *outbuf);
</listitem>
</varlistentry>
<varlistentry id="PGTYPESdatedefmtasc">
<varlistentry id="pgtypesdatedefmtasc">
<term><function>PGTYPESdate_defmt_asc</function></term>
<listitem>
<para>
@ -2747,7 +2747,7 @@ int PGTYPESdate_defmt_asc(date *d, char *fmt, char *str);
<para>
The following functions can be used to work with the timestamp type:
<variablelist>
<varlistentry id="PGTYPEStimestampfromasc">
<varlistentry id="pgtypestimestampfromasc">
<term><function>PGTYPEStimestamp_from_asc</function></term>
<listitem>
<para>
@ -2766,7 +2766,7 @@ timestamp PGTYPEStimestamp_from_asc(char *str, char **endptr);
<para>
The function returns the parsed timestamp on success. On error,
<literal>PGTYPESInvalidTimestamp</literal> is returned and <varname>errno</varname> is
set to <literal>PGTYPES_TS_BAD_TIMESTAMP</literal>. See <xref linkend="PGTYPESInvalidTimestamp"> for important notes on this value.
set to <literal>PGTYPES_TS_BAD_TIMESTAMP</literal>. See <xref linkend="pgtypesinvalidtimestamp"> for important notes on this value.
</para>
<para>
In general, the input string can contain any combination of an allowed
@ -2811,7 +2811,7 @@ timestamp PGTYPEStimestamp_from_asc(char *str, char **endptr);
</listitem>
</varlistentry>
<varlistentry id="PGTYPEStimestamptoasc">
<varlistentry id="pgtypestimestamptoasc">
<term><function>PGTYPEStimestamp_to_asc</function></term>
<listitem>
<para>
@ -2826,7 +2826,7 @@ char *PGTYPEStimestamp_to_asc(timestamp tstamp);
</listitem>
</varlistentry>
<varlistentry id="PGTYPEStimestampcurrent">
<varlistentry id="pgtypestimestampcurrent">
<term><function>PGTYPEStimestamp_current</function></term>
<listitem>
<para>
@ -2840,7 +2840,7 @@ void PGTYPEStimestamp_current(timestamp *ts);
</listitem>
</varlistentry>
<varlistentry id="PGTYPEStimestampfmtasc">
<varlistentry id="pgtypestimestampfmtasc">
<term><function>PGTYPEStimestamp_fmt_asc</function></term>
<listitem>
<para>
@ -3175,7 +3175,7 @@ int PGTYPEStimestamp_fmt_asc(timestamp *ts, char *output, int str_len, char *fmt
</listitem>
</varlistentry>
<varlistentry id="PGTYPEStimestampsub">
<varlistentry id="pgtypestimestampsub">
<term><function>PGTYPEStimestamp_sub</function></term>
<listitem>
<para>
@ -3196,7 +3196,7 @@ int PGTYPEStimestamp_sub(timestamp *ts1, timestamp *ts2, interval *iv);
</listitem>
</varlistentry>
<varlistentry id="PGTYPEStimestampdefmtasc">
<varlistentry id="pgtypestimestampdefmtasc">
<term><function>PGTYPEStimestamp_defmt_asc</function></term>
<listitem>
<para>
@ -3217,13 +3217,13 @@ int PGTYPEStimestamp_defmt_asc(char *str, char *fmt, timestamp *d);
</para>
<para>
This is the reverse function to <xref
linkend="PGTYPEStimestampfmtasc">. See the documentation there in
linkend="pgtypestimestampfmtasc">. See the documentation there in
order to find out about the possible formatting mask entries.
</para>
</listitem>
</varlistentry>
<varlistentry id="PGTYPEStimestampaddinterval">
<varlistentry id="pgtypestimestampaddinterval">
<term><function>PGTYPEStimestamp_add_interval</function></term>
<listitem>
<para>
@ -3243,7 +3243,7 @@ int PGTYPEStimestamp_add_interval(timestamp *tin, interval *span, timestamp *tou
</listitem>
</varlistentry>
<varlistentry id="PGTYPEStimestampsubinterval">
<varlistentry id="pgtypestimestampsubinterval">
<term><function>PGTYPEStimestamp_sub_interval</function></term>
<listitem>
<para>
@ -3277,7 +3277,7 @@ int PGTYPEStimestamp_sub_interval(timestamp *tin, interval *span, timestamp *tou
The following functions can be used to work with the interval type:
<variablelist>
<varlistentry id="PGTYPESintervalnew">
<varlistentry id="pgtypesintervalnew">
<term><function>PGTYPESinterval_new</function></term>
<listitem>
<para>
@ -3289,7 +3289,7 @@ interval *PGTYPESinterval_new(void);
</listitem>
</varlistentry>
<varlistentry id="PGTYPESintervalfree">
<varlistentry id="pgtypesintervalfree">
<term><function>PGTYPESinterval_free</function></term>
<listitem>
<para>
@ -3301,7 +3301,7 @@ void PGTYPESinterval_new(interval *intvl);
</listitem>
</varlistentry>
<varlistentry id="PGTYPESintervalfromasc">
<varlistentry id="pgtypesintervalfromasc">
<term><function>PGTYPESinterval_from_asc</function></term>
<listitem>
<para>
@ -3319,7 +3319,7 @@ interval *PGTYPESinterval_from_asc(char *str, char **endptr);
</listitem>
</varlistentry>
<varlistentry id="PGTYPESintervaltoasc">
<varlistentry id="pgtypesintervaltoasc">
<term><function>PGTYPESinterval_to_asc</function></term>
<listitem>
<para>
@ -3334,7 +3334,7 @@ char *PGTYPESinterval_to_asc(interval *span);
</listitem>
</varlistentry>
<varlistentry id="PGTYPESintervalcopy">
<varlistentry id="pgtypesintervalcopy">
<term><function>PGTYPESinterval_copy</function></term>
<listitem>
<para>
@ -3543,7 +3543,7 @@ void PGTYPESdecimal_free(decimal *var);
<title>Special Constants of pgtypeslib</title>
<para>
<variablelist>
<varlistentry id="PGTYPESInvalidTimestamp">
<varlistentry id="pgtypesinvalidtimestamp">
<term><literal>PGTYPESInvalidTimestamp</literal></term>
<listitem>
<para>
@ -5868,7 +5868,7 @@ ECPG = ecpg
<para>
For more details about the <function>ECPGget_PGconn()</function>, see
<xref linkend="ecpg-library">. For information about the large
object function interface, see <xref linkend="largeObjects">.
object function interface, see <xref linkend="largeobjects">.
</para>
<para>
@ -8653,7 +8653,7 @@ void rtoday(date *d);
that it sets to the current date.
</para>
<para>
Internally this function uses the <xref linkend="PGTYPESdatetoday">
Internally this function uses the <xref linkend="pgtypesdatetoday">
function.
</para>
</listitem>
@ -8678,7 +8678,7 @@ int rjulmdy(date d, short mdy[3]);
The function always returns 0 at the moment.
</para>
<para>
Internally the function uses the <xref linkend="PGTYPESdatejulmdy">
Internally the function uses the <xref linkend="pgtypesdatejulmdy">
function.
</para>
</listitem>
@ -8748,7 +8748,7 @@ int rdefmtdate(date *d, char *fmt, char *str);
</para>
<para>
Internally this function is implemented to use the <xref
linkend="PGTYPESdatedefmtasc"> function. See the reference there for a
linkend="pgtypesdatedefmtasc"> function. See the reference there for a
table of example input.
</para>
</listitem>
@ -8771,7 +8771,7 @@ int rfmtdate(date d, char *fmt, char *str);
On success, 0 is returned and a negative value if an error occurred.
</para>
<para>
Internally this function uses the <xref linkend="PGTYPESdatefmtasc">
Internally this function uses the <xref linkend="pgtypesdatefmtasc">
function, see the reference there for examples.
</para>
</listitem>
@ -8795,7 +8795,7 @@ int rmdyjul(short mdy[3], date *d);
</para>
<para>
Internally the function is implemented to use the function <xref
linkend="PGTYPESdatemdyjul">.
linkend="pgtypesdatemdyjul">.
</para>
</listitem>
</varlistentry>
@ -8851,7 +8851,7 @@ int rdayofweek(date d);
</para>
<para>
Internally the function is implemented to use the function <xref
linkend="PGTYPESdatedayofweek">.
linkend="pgtypesdatedayofweek">.
</para>
</listitem>
</varlistentry>
@ -8889,7 +8889,7 @@ int dtcvasc(char *str, timestamp *ts);
</para>
<para>
Internally this function uses the <xref
linkend="PGTYPEStimestampfromasc"> function. See the reference there
linkend="pgtypestimestampfromasc"> function. See the reference there
for a table with example inputs.
</para>
</listitem>
@ -8911,7 +8911,7 @@ dtcvfmtasc(char *inbuf, char *fmtstr, timestamp *dtvalue)
</para>
<para>
This function is implemented by means of the <xref
linkend="PGTYPEStimestampdefmtasc"> function. See the documentation
linkend="pgtypestimestampdefmtasc"> function. See the documentation
there for a list of format specifiers that can be used.
</para>
<para>
@ -8983,7 +8983,7 @@ int dttofmtasc(timestamp *ts, char *output, int str_len, char *fmtstr);
</para>
<para>
Internally, this function uses the <xref
linkend="PGTYPEStimestampfmtasc"> function. See the reference there for
linkend="pgtypestimestampfmtasc"> function. See the reference there for
information on what format mask specifiers can be used.
</para>
</listitem>

4
doc/src/sgml/func.sgml
View File

@ -17866,7 +17866,7 @@ SELECT collation for ('foo' COLLATE "de_DE");
logging and checkpoint processing. This information is cluster-wide,
and not specific to any one database. They provide most of the same
information, from the same source, as
<xref linkend="APP-PGCONTROLDATA">, although in a form better suited
<xref linkend="app-pgcontroldata">, although in a form better suited
to <acronym>SQL</acronym> functions.
</para>
@ -20376,7 +20376,7 @@ FOR EACH ROW EXECUTE PROCEDURE suppress_redundant_updates_trigger();
</para>
<para>
For more information about creating triggers, see
<xref linkend="SQL-CREATETRIGGER">.
<xref linkend="sql-createtrigger">.
</para>
</sect1>

4
doc/src/sgml/geqo.sgml
View File

@ -320,13 +320,13 @@
<listitem>
<para>
<xref linkend="ELMA04">
<xref linkend="elma04">
</para>
</listitem>
<listitem>
<para>
<xref linkend="FONG">
<xref linkend="fong">
</para>
</listitem>
</itemizedlist>

2
doc/src/sgml/gin.sgml
View File

@ -1,6 +1,6 @@
<!-- doc/src/sgml/gin.sgml -->
<chapter id="GIN">
<chapter id="gin">
<title>GIN Indexes</title>
<indexterm>

2
doc/src/sgml/gist.sgml
View File

@ -1,6 +1,6 @@
<!-- doc/src/sgml/gist.sgml -->
<chapter id="GiST">
<chapter id="gist">
<title>GiST Indexes</title>
<indexterm>

14
doc/src/sgml/history.sgml
View File

@ -31,12 +31,12 @@
Office (<acronym>ARO</acronym>), the National Science Foundation
(<acronym>NSF</acronym>), and ESL, Inc. The implementation of
<productname>POSTGRES</productname> began in 1986. The initial
concepts for the system were presented in <xref linkend="STON86">,
concepts for the system were presented in <xref linkend="ston86">,
and the definition of the initial data model appeared in <xref
linkend="ROWE87">. The design of the rule system at that time was
described in <xref linkend="STON87a">. The rationale and
linkend="rowe87">. The design of the rule system at that time was
described in <xref linkend="ston87a">. The rationale and
architecture of the storage manager were detailed in <xref
linkend="STON87b">.
linkend="ston87b">.
</para>
<para>
@ -44,10 +44,10 @@
releases since then. The first <quote>demoware</quote> system
became operational in 1987 and was shown at the 1988
<acronym>ACM-SIGMOD</acronym> Conference. Version 1, described in
<xref linkend="STON90a">, was released to a few external users in
<xref linkend="ston90a">, was released to a few external users in
June 1989. In response to a critique of the first rule system
(<xref linkend="STON89">), the rule system was redesigned (<xref
linkend="STON90b">), and Version 2 was released in June 1990 with
(<xref linkend="ston89">), the rule system was redesigned (<xref
linkend="ston90b">), and Version 2 was released in June 1990 with
the new rule system. Version 3 appeared in 1991 and added support
for multiple storage managers, an improved query executor, and a
rewritten rule system. For the most part, subsequent releases

16
doc/src/sgml/indices.sgml
View File

@ -98,8 +98,8 @@ CREATE INDEX test1_id_index ON test1 (id);
In production environments this is often unacceptable.
It is possible to allow writes to occur in parallel with index
creation, but there are several caveats to be aware of &mdash;
for more information see <xref linkend="SQL-CREATEINDEX-CONCURRENTLY"
endterm="SQL-CREATEINDEX-CONCURRENTLY-title">.
for more information see <xref linkend="sql-createindex-concurrently"
endterm="sql-createindex-concurrently-title">.
</para>
<para>
@ -232,7 +232,7 @@ CREATE INDEX <replaceable>name</replaceable> ON <replaceable>table</replaceable>
documented in <xref linkend="gist-builtin-opclasses-table">.
Many other GiST operator
classes are available in the <literal>contrib</literal> collection or as separate
projects. For more information see <xref linkend="GiST">.
projects. For more information see <xref linkend="gist">.
</para>
<para>
@ -278,7 +278,7 @@ SELECT * FROM places ORDER BY location <-> point '(101,456)' LIMIT 10;
these operators.)
The SP-GiST operator classes included in the standard distribution are
documented in <xref linkend="spgist-builtin-opclasses-table">.
For more information see <xref linkend="SPGiST">.
For more information see <xref linkend="spgist">.
</para>
<para>
@ -319,7 +319,7 @@ SELECT * FROM places ORDER BY location <-> point '(101,456)' LIMIT 10;
documented in <xref linkend="gin-builtin-opclasses-table">.
Many other GIN operator
classes are available in the <literal>contrib</literal> collection or as separate
projects. For more information see <xref linkend="GIN">.
projects. For more information see <xref linkend="gin">.
</para>
<para>
@ -352,7 +352,7 @@ SELECT * FROM places ORDER BY location <-> point '(101,456)' LIMIT 10;
The BRIN operator classes included in the standard distribution are
documented in <xref linkend="brin-builtin-opclasses-table">.
For more information see <xref linkend="BRIN">.
For more information see <xref linkend="brin">.
</para>
</sect1>
@ -962,8 +962,8 @@ CREATE UNIQUE INDEX tests_success_constraint ON tests (subject, target)
<para>
More information about partial indexes can be found in <xref
linkend="STON89b">, <xref linkend="OLSON93">, and <xref
linkend="SESHADRI95">.
linkend="ston89b">, <xref linkend="olson93">, and <xref
linkend="seshadri95">.
</para>
</sect1>

2
doc/src/sgml/libpq.sgml
View File

@ -2447,7 +2447,7 @@ PGresult *PQprepare(PGconn *conn,
<function>PQprepare</function> creates a prepared statement for later
execution with <function>PQexecPrepared</function>. This feature allows
commands to be executed repeatedly without being parsed and
planned each time; see <xref linkend="SQL-PREPARE"> for details.
planned each time; see <xref linkend="sql-prepare"> for details.
<function>PQprepare</function> is supported only in protocol 3.0 and later
connections; it will fail when using protocol 2.0.
</para>

2
doc/src/sgml/lobj.sgml
View File

@ -1,6 +1,6 @@
<!-- doc/src/sgml/lobj.sgml -->
<chapter id="largeObjects">
<chapter id="largeobjects">
<title>Large Objects</title>
<indexterm zone="largeobjects"><primary>large object</primary></indexterm>

2
doc/src/sgml/logical-replication.sgml
View File

@ -126,7 +126,7 @@
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-createtable-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

6
doc/src/sgml/logicaldecoding.sgml
View File

@ -24,7 +24,7 @@
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-createtable-replica-identity">).
</para>
<para>
@ -576,8 +576,8 @@ typedef void (*LogicalDecodeChangeCB) (struct LogicalDecodingContext *ctx,
<note>
<para>
Only changes in user defined tables that are not unlogged
(see <xref linkend="SQL-CREATETABLE-UNLOGGED">) and not temporary
(see <xref linkend="SQL-CREATETABLE-TEMPORARY">) can be extracted using
(see <xref linkend="sql-createtable-unlogged">) and not temporary
(see <xref linkend="sql-createtable-temporary">) can be extracted using
logical decoding.
</para>
</note>

4
doc/src/sgml/mvcc.sgml
View File

@ -929,7 +929,7 @@ ERROR: could not serialize access due to read/write dependencies among transact
<command>CREATE STATISTICS</command> and
<command>ALTER TABLE VALIDATE</command> and other
<command>ALTER TABLE</command> variants (for full details see
<xref linkend="SQL-ALTERTABLE">).
<xref linkend="sql-altertable">).
</para>
</listitem>
</varlistentry>
@ -972,7 +972,7 @@ ERROR: could not serialize access due to read/write dependencies among transact
<para>
Acquired by <command>CREATE COLLATION</command>,
<command>CREATE TRIGGER</command>, and many forms of
<command>ALTER TABLE</command> (see <xref linkend="SQL-ALTERTABLE">).
<command>ALTER TABLE</command> (see <xref linkend="sql-altertable">).
</para>
</listitem>
</varlistentry>

4
doc/src/sgml/passwordcheck.sgml
View File

@ -10,8 +10,8 @@
<para>
The <filename>passwordcheck</filename> module checks users' passwords
whenever they are set with
<xref linkend="SQL-CREATEROLE"> or
<xref linkend="SQL-ALTERROLE">.
<xref linkend="sql-createrole"> or
<xref linkend="sql-alterrole">.
If a password is considered too weak, it will be rejected and
the command will terminate with an error.
</para>

2
doc/src/sgml/perform.sgml
View File

@ -1848,7 +1848,7 @@ SELECT * FROM x, y, a, b, c WHERE something AND somethingelse;
<listitem>
<para>
Create <link linkend="SQL-CREATETABLE-UNLOGGED">unlogged
Create <link linkend="sql-createtable-unlogged">unlogged
tables</link> to avoid <acronym>WAL</acronym> writes, though it
makes the tables non-crash-safe.
</para>

2
doc/src/sgml/queries.sgml
View File

@ -795,7 +795,7 @@ SELECT *
AS t1(proname name, prosrc text)
WHERE proname LIKE 'bytea%';
</programlisting>
The <xref linkend="CONTRIB-DBLINK-FUNCTION"> function
The <xref linkend="contrib-dblink-function"> function
(part of the <xref linkend="dblink"> module) executes
a remote query. It is declared to return
<type>record</type> since it might be used for any kind of query.

2
doc/src/sgml/query.sgml
View File

@ -12,7 +12,7 @@
tutorial is only intended to give you an introduction and is in no
way a complete tutorial on <acronym>SQL</acronym>. Numerous books
have been written on <acronym>SQL</acronym>, including <xref
linkend="MELT93"> and <xref linkend="DATE97">.
linkend="melt93"> and <xref linkend="date97">.
You should be aware that some <productname>PostgreSQL</productname>
language features are extensions to the standard.
</para>

6
doc/src/sgml/rangetypes.sgml
View File

@ -65,7 +65,7 @@
</listitem>
</itemizedlist>
In addition, you can define your own range types;
see <xref linkend="SQL-CREATETYPE"> for more information.
see <xref linkend="sql-createtype"> for more information.
</para>
</sect2>
@ -406,7 +406,7 @@ SELECT '[11:10, 23:00]'::timerange;
</programlisting>
<para>
See <xref linkend="SQL-CREATETYPE"> for more information about creating
See <xref linkend="sql-createtype"> for more information about creating
range types.
</para>
</sect2>
@ -462,7 +462,7 @@ CREATE INDEX reservation_idx ON reservation USING GIST (during);
While <literal>UNIQUE</literal> is a natural constraint for scalar
values, it is usually unsuitable for range types. Instead, an
exclusion constraint is often more appropriate
(see <link linkend="SQL-CREATETABLE-EXCLUDE">CREATE TABLE
(see <link linkend="sql-createtable-exclude">CREATE TABLE
... CONSTRAINT ... EXCLUDE</link>). Exclusion constraints allow the
specification of constraints such as <quote>non-overlapping</quote> on a
range type. For example:

6
doc/src/sgml/ref/abort.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/abort.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ABORT">
<refentry id="sql-abort">
<indexterm zone="sql-abort">
<primary>ABORT</primary>
</indexterm>
@ -33,7 +33,7 @@ ABORT [ WORK | TRANSACTION ]
all the updates made by the transaction to be discarded.
This command is identical
in behavior to the standard <acronym>SQL</acronym> command
<xref linkend="SQL-ROLLBACK">,
<xref linkend="sql-rollback">,
and is present only for historical reasons.
</para>
</refsect1>
@ -58,7 +58,7 @@ ABORT [ WORK | TRANSACTION ]
<title>Notes</title>
<para>
Use <xref linkend="SQL-COMMIT"> to
Use <xref linkend="sql-commit"> to
successfully terminate a transaction.
</para>

2
doc/src/sgml/ref/alter_aggregate.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_aggregate.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERAGGREGATE">
<refentry id="sql-alteraggregate">
<indexterm zone="sql-alteraggregate">
<primary>ALTER AGGREGATE</primary>
</indexterm>

2
doc/src/sgml/ref/alter_collation.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_collation.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERCOLLATION">
<refentry id="sql-altercollation">
<indexterm zone="sql-altercollation">
<primary>ALTER COLLATION</primary>
</indexterm>

2
doc/src/sgml/ref/alter_conversion.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_conversion.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERCONVERSION">
<refentry id="sql-alterconversion">
<indexterm zone="sql-alterconversion">
<primary>ALTER CONVERSION</primary>
</indexterm>

2
doc/src/sgml/ref/alter_database.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_database.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERDATABASE">
<refentry id="sql-alterdatabase">
<indexterm zone="sql-alterdatabase">
<primary>ALTER DATABASE</primary>
</indexterm>

2
doc/src/sgml/ref/alter_default_privileges.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_default_privileges.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERDEFAULTPRIVILEGES">
<refentry id="sql-alterdefaultprivileges">
<indexterm zone="sql-alterdefaultprivileges">
<primary>ALTER DEFAULT PRIVILEGES</primary>
</indexterm>

8
doc/src/sgml/ref/alter_domain.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_domain.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERDOMAIN">
<refentry id="sql-alterdomain">
<indexterm zone="sql-alterdomain">
<primary>ALTER DOMAIN</primary>
</indexterm>
@ -80,7 +80,7 @@ ALTER DOMAIN <replaceable class="parameter">name</replaceable>
<listitem>
<para>
This form adds a new constraint to a domain using the same syntax as
<xref linkend="SQL-CREATEDOMAIN">.
<xref linkend="sql-createdomain">.
When a new constraint is added to a domain, all columns using that
domain will be checked against the newly added constraint. These
checks can be suppressed by adding the new constraint using the
@ -325,7 +325,7 @@ ALTER DOMAIN zipcode SET SCHEMA customers;
</programlisting></para>
</refsect1>
<refsect1 id="SQL-ALTERDOMAIN-compatibility">
<refsect1 id="sql-alterdomain-compatibility">
<title>Compatibility</title>
<para>
@ -338,7 +338,7 @@ ALTER DOMAIN zipcode SET SCHEMA customers;
</para>
</refsect1>
<refsect1 id="SQL-ALTERDOMAIN-see-also">
<refsect1 id="sql-alterdomain-see-also">
<title>See Also</title>
<simplelist type="inline">

2
doc/src/sgml/ref/alter_event_trigger.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_event_trigger.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTEREVENTTRIGGER">
<refentry id="sql-altereventtrigger">
<indexterm zone="sql-altereventtrigger">
<primary>ALTER EVENT TRIGGER</primary>
</indexterm>

4
doc/src/sgml/ref/alter_extension.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_extension.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTEREXTENSION">
<refentry id="sql-alterextension">
<indexterm zone="sql-alterextension">
<primary>ALTER EXTENSION</primary>
</indexterm>
@ -319,7 +319,7 @@ ALTER EXTENSION hstore ADD FUNCTION populate_record(anyelement, hstore);
</para>
</refsect1>
<refsect1 id="SQL-ALTEREXTENSION-see-also">
<refsect1 id="sql-alterextension-see-also">
<title>See Also</title>
<simplelist type="inline">

2
doc/src/sgml/ref/alter_foreign_data_wrapper.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_foreign_data_wrapper.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERFOREIGNDATAWRAPPER">
<refentry id="sql-alterforeigndatawrapper">
<indexterm zone="sql-alterforeigndatawrapper">
<primary>ALTER FOREIGN DATA WRAPPER</primary>
</indexterm>

8
doc/src/sgml/ref/alter_foreign_table.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/rel/alter_foreign_table.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERFOREIGNTABLE">
<refentry id="sql-alterforeigntable">
<indexterm zone="sql-alterforeigntable">
<primary>ALTER FOREIGN TABLE</primary>
</indexterm>
@ -72,7 +72,7 @@ ALTER FOREIGN TABLE [ IF EXISTS ] <replaceable class="parameter">name</replaceab
<listitem>
<para>
This form adds a new column to the foreign table, using the same syntax as
<xref linkend="SQL-CREATEFOREIGNTABLE">.
<xref linkend="sql-createforeigntable">.
Unlike the case when adding a column to a regular table, nothing happens
to the underlying storage: this action simply declares that
some new column is now accessible through the foreign table.
@ -173,7 +173,7 @@ ALTER FOREIGN TABLE [ IF EXISTS ] <replaceable class="parameter">name</replaceab
<listitem>
<para>
This form adds a new constraint to a foreign table, using the same
syntax as <xref linkend="SQL-CREATEFOREIGNTABLE">.
syntax as <xref linkend="sql-createforeigntable">.
Currently only <literal>CHECK</literal> constraints are supported.
</para>
@ -182,7 +182,7 @@ ALTER FOREIGN TABLE [ IF EXISTS ] <replaceable class="parameter">name</replaceab
done to verify the constraint is correct; rather, this action simply
declares that some new condition should be assumed to hold for all rows
in the foreign table. (See the discussion
in <xref linkend="SQL-CREATEFOREIGNTABLE">.)
in <xref linkend="sql-createforeigntable">.)
If the constraint is marked <literal>NOT VALID</literal>, then it isn't
assumed to hold, but is only recorded for possible future use.
</para>

2
doc/src/sgml/ref/alter_function.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_function.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERFUNCTION">
<refentry id="sql-alterfunction">
<indexterm zone="sql-alterfunction">
<primary>ALTER FUNCTION</primary>
</indexterm>

6
doc/src/sgml/ref/alter_group.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_group.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERGROUP">
<refentry id="sql-altergroup">
<indexterm zone="sql-altergroup">
<primary>ALTER GROUP</primary>
</indexterm>
@ -50,8 +50,8 @@ ALTER GROUP <replaceable class="parameter">group_name</replaceable> RENAME TO <r
<quote>group</quote> for this purpose.) These variants are effectively
equivalent to granting or revoking membership in the role named as the
<quote>group</quote>; so the preferred way to do this is to use
<xref linkend="SQL-GRANT"> or
<xref linkend="SQL-REVOKE">.
<xref linkend="sql-grant"> or
<xref linkend="sql-revoke">.
</para>
<para>

10
doc/src/sgml/ref/alter_index.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_index.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERINDEX">
<refentry id="sql-alterindex">
<indexterm zone="sql-alterindex">
<primary>ALTER INDEX</primary>
</indexterm>
@ -70,7 +70,7 @@ ALTER INDEX ALL IN TABLESPACE <replaceable class="parameter">name</replaceable>
this command, use <command>ALTER DATABASE</command> or explicit
<command>ALTER INDEX</command> invocations instead if desired.
See also
<xref linkend="SQL-CREATETABLESPACE">.
<xref linkend="sql-createtablespace">.
</para>
</listitem>
</varlistentry>
@ -91,11 +91,11 @@ ALTER INDEX ALL IN TABLESPACE <replaceable class="parameter">name</replaceable>
<para>
This form changes one or more index-method-specific storage parameters
for the index. See
<xref linkend="SQL-CREATEINDEX">
<xref linkend="sql-createindex">
for details on the available parameters. Note that the index contents
will not be modified immediately by this command; depending on the
parameter you might need to rebuild the index with
<xref linkend="SQL-REINDEX">
<xref linkend="sql-reindex">
to get the desired effects.
</para>
</listitem>
@ -225,7 +225,7 @@ ALTER INDEX ALL IN TABLESPACE <replaceable class="parameter">name</replaceable>
<para>
These operations are also possible using
<xref linkend="SQL-ALTERTABLE">.
<xref linkend="sql-altertable">.
<command>ALTER INDEX</command> is in fact just an alias for the forms
of <command>ALTER TABLE</command> that apply to indexes.
</para>

2
doc/src/sgml/ref/alter_language.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_language.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERLANGUAGE">
<refentry id="sql-alterlanguage">
<indexterm zone="sql-alterlanguage">
<primary>ALTER LANGUAGE</primary>
</indexterm>

2
doc/src/sgml/ref/alter_large_object.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_large_object.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERLARGEOBJECT">
<refentry id="sql-alterlargeobject">
<indexterm zone="sql-alterlargeobject">
<primary>ALTER LARGE OBJECT</primary>
</indexterm>

2
doc/src/sgml/ref/alter_materialized_view.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_materialized_view.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERMATERIALIZEDVIEW">
<refentry id="sql-altermaterializedview">
<indexterm zone="sql-altermaterializedview">
<primary>ALTER MATERIALIZED VIEW</primary>
</indexterm>

2
doc/src/sgml/ref/alter_opclass.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_opclass.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTEROPCLASS">
<refentry id="sql-alteropclass">
<indexterm zone="sql-alteropclass">
<primary>ALTER OPERATOR CLASS</primary>
</indexterm>

2
doc/src/sgml/ref/alter_operator.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_operator.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTEROPERATOR">
<refentry id="sql-alteroperator">
<indexterm zone="sql-alteroperator">
<primary>ALTER OPERATOR</primary>
</indexterm>

2
doc/src/sgml/ref/alter_opfamily.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_opfamily.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTEROPFAMILY">
<refentry id="sql-alteropfamily">
<indexterm zone="sql-alteropfamily">
<primary>ALTER OPERATOR FAMILY</primary>
</indexterm>

2
doc/src/sgml/ref/alter_policy.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_policy.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERPOLICY">
<refentry id="sql-alterpolicy">
<indexterm zone="sql-alterpolicy">
<primary>ALTER POLICY</primary>
</indexterm>

4
doc/src/sgml/ref/alter_publication.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_publication.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERPUBLICATION">
<refentry id="sql-alterpublication">
<indexterm zone="sql-alterpublication">
<primary>ALTER PUBLICATION</primary>
</indexterm>
@ -101,7 +101,7 @@ ALTER PUBLICATION <replaceable class="parameter">name</replaceable> RENAME TO <r
<listitem>
<para>
This clause alters publication parameters originally set by
<xref linkend="SQL-CREATEPUBLICATION">. See there for more information.
<xref linkend="sql-createpublication">. See there for more information.
</para>
</listitem>
</varlistentry>

16
doc/src/sgml/ref/alter_role.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_role.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERROLE">
<refentry id="sql-alterrole">
<indexterm zone="sql-alterrole">
<primary>ALTER ROLE</primary>
</indexterm>
@ -65,8 +65,8 @@ ALTER ROLE { <replaceable class="parameter">role_specification</replaceable> | A
<xref linkend="sql-createrole">.
(All the possible attributes are covered,
except that there are no options for adding or removing memberships; use
<xref linkend="SQL-GRANT"> and
<xref linkend="SQL-REVOKE"> for that.)
<xref linkend="sql-grant"> and
<xref linkend="sql-revoke"> for that.)
Attributes not mentioned in the command retain their previous settings.
Database superusers can change any of these settings for any role.
Roles having <literal>CREATEROLE</literal> privilege can change any of these
@ -173,7 +173,7 @@ ALTER ROLE { <replaceable class="parameter">role_specification</replaceable> | A
<listitem>
<para>
These clauses alter attributes originally set by
<xref linkend="SQL-CREATEROLE">. For more information, see the
<xref linkend="sql-createrole">. For more information, see the
<command>CREATE ROLE</command> reference page.
</para>
</listitem>
@ -236,14 +236,14 @@ ALTER ROLE { <replaceable class="parameter">role_specification</replaceable> | A
<title>Notes</title>
<para>
Use <xref linkend="SQL-CREATEROLE">
to add new roles, and <xref linkend="SQL-DROPROLE"> to remove a role.
Use <xref linkend="sql-createrole">
to add new roles, and <xref linkend="sql-droprole"> to remove a role.
</para>
<para>
<command>ALTER ROLE</command> cannot change a role's memberships.
Use <xref linkend="SQL-GRANT"> and
<xref linkend="SQL-REVOKE">
Use <xref linkend="sql-grant"> and
<xref linkend="sql-revoke">
to do that.
</para>

2
doc/src/sgml/ref/alter_rule.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_rule.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERRULE">
<refentry id="sql-alterrule">
<indexterm zone="sql-alterrule">
<primary>ALTER RULE</primary>
</indexterm>

2
doc/src/sgml/ref/alter_schema.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_schema.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERSCHEMA">
<refentry id="sql-alterschema">
<indexterm zone="sql-alterschema">
<primary>ALTER SCHEMA</primary>
</indexterm>

2
doc/src/sgml/ref/alter_sequence.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_sequence.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERSEQUENCE">
<refentry id="sql-altersequence">
<indexterm zone="sql-altersequence">
<primary>ALTER SEQUENCE</primary>
</indexterm>

2
doc/src/sgml/ref/alter_server.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_server.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERSERVER">
<refentry id="sql-alterserver">
<indexterm zone="sql-alterserver">
<primary>ALTER SERVER</primary>
</indexterm>

2
doc/src/sgml/ref/alter_statistics.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_statistics.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERSTATISTICS">
<refentry id="sql-alterstatistics">
<indexterm zone="sql-alterstatistics">
<primary>ALTER STATISTICS</primary>
</indexterm>

8
doc/src/sgml/ref/alter_subscription.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_subscription.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERSUBSCRIPTION">
<refentry id="sql-altersubscription">
<indexterm zone="sql-altersubscription">
<primary>ALTER SUBSCRIPTION</primary>
</indexterm>
@ -68,7 +68,7 @@ ALTER SUBSCRIPTION <replaceable class="parameter">name</replaceable> RENAME TO <
<listitem>
<para>
This clause alters the connection property originally set by
<xref linkend="SQL-CREATESUBSCRIPTION">. See there for more
<xref linkend="sql-createsubscription">. See there for more
information.
</para>
</listitem>
@ -79,7 +79,7 @@ ALTER SUBSCRIPTION <replaceable class="parameter">name</replaceable> RENAME TO <
<listitem>
<para>
Changes list of subscribed publications. See
<xref linkend="SQL-CREATESUBSCRIPTION"> for more information.
<xref linkend="sql-createsubscription"> for more information.
By default this command will also act like <literal>REFRESH
PUBLICATION</literal>.
</para>
@ -162,7 +162,7 @@ ALTER SUBSCRIPTION <replaceable class="parameter">name</replaceable> RENAME TO <
<listitem>
<para>
This clause alters parameters originally set by
<xref linkend="SQL-CREATESUBSCRIPTION">. See there for more
<xref linkend="sql-createsubscription">. See there for more
information. The allowed options are <literal>slot_name</literal> and
<literal>synchronous_commit</literal>
</para>

6
doc/src/sgml/ref/alter_system.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_system.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERSYSTEM">
<refentry id="sql-altersystem">
<indexterm zone="sql-altersystem">
<primary>ALTER SYSTEM</primary>
</indexterm>
@ -135,8 +135,8 @@ ALTER SYSTEM RESET wal_level;
<title>See Also</title>
<simplelist type="inline">
<member><xref linkend="SQL-SET"></member>
<member><xref linkend="SQL-SHOW"></member>
<member><xref linkend="sql-set"></member>
<member><xref linkend="sql-show"></member>
</simplelist>
</refsect1>

30
doc/src/sgml/ref/alter_table.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_table.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERTABLE">
<refentry id="sql-altertable">
<indexterm zone="sql-altertable">
<primary>ALTER TABLE</primary>
</indexterm>
@ -109,7 +109,7 @@ ALTER TABLE [ IF EXISTS ] <replaceable class="parameter">name</replaceable>
<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>
<xref linkend="sql-createtable">. If <literal>IF NOT EXISTS</literal>
is specified and a column already exists with this name,
no error is thrown.
</para>
@ -314,7 +314,7 @@ ALTER TABLE [ IF EXISTS ] <replaceable class="parameter">name</replaceable>
<listitem>
<para>
This form adds a new constraint to a table using the same syntax as
<xref linkend="SQL-CREATETABLE">, plus the option <literal>NOT
<xref linkend="sql-createtable">, plus the option <literal>NOT
VALID</literal>, which is currently only allowed for foreign key
and CHECK constraints.
If the constraint is marked <literal>NOT VALID</literal>, the
@ -483,7 +483,7 @@ ALTER TABLE [ IF EXISTS ] <replaceable class="parameter">name</replaceable>
even if row level security is disabled - in this case, the policies will
NOT be applied and the policies will be ignored.
See also
<xref linkend="SQL-CREATEPOLICY">.
<xref linkend="sql-createpolicy">.
</para>
</listitem>
</varlistentry>
@ -498,7 +498,7 @@ ALTER TABLE [ IF EXISTS ] <replaceable class="parameter">name</replaceable>
disabled (the default) then row level security will not be applied when
the user is the table owner.
See also
<xref linkend="SQL-CREATEPOLICY">.
<xref linkend="sql-createpolicy">.
</para>
</listitem>
</varlistentry>
@ -508,7 +508,7 @@ ALTER TABLE [ IF EXISTS ] <replaceable class="parameter">name</replaceable>
<listitem>
<para>
This form selects the default index for future
<xref linkend="SQL-CLUSTER">
<xref linkend="sql-cluster">
operations. It does not actually re-cluster the table.
</para>
<para>
@ -522,7 +522,7 @@ ALTER TABLE [ IF EXISTS ] <replaceable class="parameter">name</replaceable>
<listitem>
<para>
This form removes the most recently used
<xref linkend="SQL-CLUSTER">
<xref linkend="sql-cluster">
index specification from the table. This affects
future cluster operations that don't specify an index.
</para>
@ -582,7 +582,7 @@ ALTER TABLE [ IF EXISTS ] <replaceable class="parameter">name</replaceable>
<literal>information_schema</literal> relations are not considered part
of the system catalogs and will be moved.
See also
<xref linkend="SQL-CREATETABLESPACE">.
<xref linkend="sql-createtablespace">.
</para>
</listitem>
</varlistentry>
@ -592,7 +592,7 @@ ALTER TABLE [ IF EXISTS ] <replaceable class="parameter">name</replaceable>
<listitem>
<para>
This form changes the table from unlogged to logged or vice-versa
(see <xref linkend="SQL-CREATETABLE-UNLOGGED">). It cannot be applied
(see <xref linkend="sql-createtable-unlogged">). It cannot be applied
to a temporary table.
</para>
</listitem>
@ -603,13 +603,13 @@ ALTER TABLE [ IF EXISTS ] <replaceable class="parameter">name</replaceable>
<listitem>
<para>
This form changes one or more storage parameters for the table. See
<xref linkend="SQL-CREATETABLE-storage-parameters"
endterm="SQL-CREATETABLE-storage-parameters-title">
<xref linkend="sql-createtable-storage-parameters"
endterm="sql-createtable-storage-parameters-title">
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">VACUUM
FULL</link>, <xref linkend="sql-cluster"> 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
@ -722,7 +722,7 @@ ALTER TABLE [ IF EXISTS ] <replaceable class="parameter">name</replaceable>
</listitem>
</varlistentry>
<varlistentry id="SQL-CREATETABLE-REPLICA-IDENTITY">
<varlistentry id="sql-createtable-replica-identity">
<term><literal>REPLICA IDENTITY</literal></term>
<listitem>
<para>
@ -810,7 +810,7 @@ ALTER TABLE [ IF EXISTS ] <replaceable class="parameter">name</replaceable>
<para>
If the new partition is a foreign table, nothing is done to verify
that all the rows in the foreign table obey the partition constraint.
(See the discussion in <xref linkend="SQL-CREATEFOREIGNTABLE"> about
(See the discussion in <xref linkend="sql-createforeigntable"> about
constraints on the foreign table.)
</para>

2
doc/src/sgml/ref/alter_tablespace.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_tablespace.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERTABLESPACE">
<refentry id="sql-altertablespace">
<indexterm zone="sql-altertablespace">
<primary>ALTER TABLESPACE</primary>
</indexterm>

4
doc/src/sgml/ref/alter_trigger.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_trigger.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERTRIGGER">
<refentry id="sql-altertrigger">
<indexterm zone="sql-altertrigger">
<primary>ALTER TRIGGER</primary>
</indexterm>
@ -90,7 +90,7 @@ ALTER TRIGGER <replaceable class="parameter">name</replaceable> ON <replaceable
<para>
The ability to temporarily enable or disable a trigger is provided by
<xref linkend="SQL-ALTERTABLE">, not by
<xref linkend="sql-altertable">, not by
<command>ALTER TRIGGER</command>, because <command>ALTER TRIGGER</command> has no
convenient way to express the option of enabling or disabling all of
a table's triggers at once.

2
doc/src/sgml/ref/alter_tsconfig.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_tsconfig.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERTSCONFIG">
<refentry id="sql-altertsconfig">
<indexterm zone="sql-altertsconfig">
<primary>ALTER TEXT SEARCH CONFIGURATION</primary>
</indexterm>

2
doc/src/sgml/ref/alter_tsdictionary.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_tsdictionary.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERTSDICTIONARY">
<refentry id="sql-altertsdictionary">
<indexterm zone="sql-altertsdictionary">
<primary>ALTER TEXT SEARCH DICTIONARY</primary>
</indexterm>

2
doc/src/sgml/ref/alter_tsparser.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_tsparser.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERTSPARSER">
<refentry id="sql-altertsparser">
<indexterm zone="sql-altertsparser">
<primary>ALTER TEXT SEARCH PARSER</primary>
</indexterm>

2
doc/src/sgml/ref/alter_tstemplate.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_tstemplate.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERTSTEMPLATE">
<refentry id="sql-altertstemplate">
<indexterm zone="sql-altertstemplate">
<primary>ALTER TEXT SEARCH TEMPLATE</primary>
</indexterm>

6
doc/src/sgml/ref/alter_type.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_type.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERTYPE">
<refentry id="sql-altertype">
<indexterm zone="sql-altertype">
<primary>ALTER TYPE</primary>
</indexterm>
@ -52,7 +52,7 @@ ALTER TYPE <replaceable class="parameter">name</replaceable> RENAME VALUE <repla
<listitem>
<para>
This form adds a new attribute to a composite type, using the same syntax as
<xref linkend="SQL-CREATETYPE">.
<xref linkend="sql-createtype">.
</para>
</listitem>
</varlistentry>
@ -364,7 +364,7 @@ ALTER TYPE colors RENAME VALUE 'purple' TO 'mauve';
</para>
</refsect1>
<refsect1 id="SQL-ALTERTYPE-see-also">
<refsect1 id="sql-altertype-see-also">
<title>See Also</title>
<simplelist type="inline">

2
doc/src/sgml/ref/alter_user.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_user.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERUSER">
<refentry id="sql-alteruser">
<indexterm zone="sql-alteruser">
<primary>ALTER USER</primary>
</indexterm>

2
doc/src/sgml/ref/alter_user_mapping.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_user_mapping.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERUSERMAPPING">
<refentry id="sql-alterusermapping">
<indexterm zone="sql-alterusermapping">
<primary>ALTER USER MAPPING</primary>
</indexterm>

2
doc/src/sgml/ref/alter_view.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/alter_view.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ALTERVIEW">
<refentry id="sql-alterview">
<indexterm zone="sql-alterview">
<primary>ALTER VIEW</primary>
</indexterm>

2
doc/src/sgml/ref/analyze.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/analyze.sgml
PostgreSQL documentation
-->
<refentry id="SQL-ANALYZE">
<refentry id="sql-analyze">
<indexterm zone="sql-analyze">
<primary>ANALYZE</primary>
</indexterm>

6
doc/src/sgml/ref/begin.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/begin.sgml
PostgreSQL documentation
-->
<refentry id="SQL-BEGIN">
<refentry id="sql-begin">
<indexterm zone="sql-begin">
<primary>BEGIN</primary>
</indexterm>
@ -95,8 +95,8 @@ BEGIN [ WORK | TRANSACTION ] [ <replaceable class="parameter">transaction_mode</
</para>
<para>
Use <xref linkend="SQL-COMMIT"> or
<xref linkend="SQL-ROLLBACK">
Use <xref linkend="sql-commit"> or
<xref linkend="sql-rollback">
to terminate a transaction block.
</para>

2
doc/src/sgml/ref/close.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/close.sgml
PostgreSQL documentation
-->
<refentry id="SQL-CLOSE">
<refentry id="sql-close">
<indexterm zone="sql-close">
<primary>CLOSE</primary>
</indexterm>

4
doc/src/sgml/ref/cluster.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/cluster.sgml
PostgreSQL documentation
-->
<refentry id="SQL-CLUSTER">
<refentry id="sql-cluster">
<indexterm zone="sql-cluster">
<primary>CLUSTER</primary>
</indexterm>
@ -57,7 +57,7 @@ CLUSTER [VERBOSE]
<command>CLUSTER <replaceable class="parameter">table_name</replaceable></command>
reclusters the table using the same index as before. You can also
use the <literal>CLUSTER</literal> or <literal>SET WITHOUT CLUSTER</literal>
forms of <xref linkend="SQL-ALTERTABLE"> to set the index to be used for
forms of <xref linkend="sql-altertable"> to set the index to be used for
future cluster operations, or to clear any previous setting.
</para>

8
doc/src/sgml/ref/clusterdb.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/clusterdb.sgml
PostgreSQL documentation
-->
<refentry id="APP-CLUSTERDB">
<refentry id="app-clusterdb">
<indexterm zone="app-clusterdb">
<primary>clusterdb</primary>
</indexterm>
@ -60,7 +60,7 @@ PostgreSQL documentation
<para>
<application>clusterdb</application> is a wrapper around the SQL
command <xref linkend="SQL-CLUSTER">.
command <xref linkend="sql-cluster">.
There is no effective difference between clustering databases via
this utility and via other methods for accessing the server.
</para>
@ -289,8 +289,8 @@ PostgreSQL documentation
<title>Diagnostics</title>
<para>
In case of difficulty, see <xref linkend="SQL-CLUSTER">
and <xref linkend="APP-PSQL"> for
In case of difficulty, see <xref linkend="sql-cluster">
and <xref linkend="app-psql"> for
discussions of potential problems and error messages.
The database server must be running at the
targeted host. Also, any default connection settings and environment

2
doc/src/sgml/ref/comment.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/comment.sgml
PostgreSQL documentation
-->
<refentry id="SQL-COMMENT">
<refentry id="sql-comment">
<indexterm zone="sql-comment">
<primary>COMMENT</primary>
</indexterm>

4
doc/src/sgml/ref/commit.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/commit.sgml
PostgreSQL documentation
-->
<refentry id="SQL-COMMIT">
<refentry id="sql-commit">
<indexterm zone="sql-commit">
<primary>COMMIT</primary>
</indexterm>
@ -55,7 +55,7 @@ COMMIT [ WORK | TRANSACTION ]
<title>Notes</title>
<para>
Use <xref linkend="SQL-ROLLBACK"> to
Use <xref linkend="sql-rollback"> to
abort a transaction.
</para>

2
doc/src/sgml/ref/commit_prepared.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/commit_prepared.sgml
PostgreSQL documentation
-->
<refentry id="SQL-COMMIT-PREPARED">
<refentry id="sql-commit-prepared">
<indexterm zone="sql-commit-prepared">
<primary>COMMIT PREPARED</primary>
</indexterm>

4
doc/src/sgml/ref/copy.sgml
View File

@ -4,7 +4,7 @@ PostgreSQL documentation
-->
<refentry id="SQL-COPY">
<refentry id="sql-copy">
<indexterm zone="sql-copy">
<primary>COPY</primary>
</indexterm>
@ -451,7 +451,7 @@ COPY <replaceable class="parameter">count</replaceable>
<para>
Do not confuse <command>COPY</command> with the
<application>psql</application> instruction
<command><link linkend="APP-PSQL-meta-commands-copy">\copy</link></command>. <command>\copy</command> invokes
<command><link linkend="app-psql-meta-commands-copy">\copy</link></command>. <command>\copy</command> invokes
<command>COPY FROM STDIN</command> or <command>COPY TO
STDOUT</command>, and then fetches/stores the data in a file
accessible to the <application>psql</application> client. Thus,

2
doc/src/sgml/ref/create_aggregate.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/create_aggregate.sgml
PostgreSQL documentation
-->
<refentry id="SQL-CREATEAGGREGATE">
<refentry id="sql-createaggregate">
<indexterm zone="sql-createaggregate">
<primary>CREATE AGGREGATE</primary>
</indexterm>

2
doc/src/sgml/ref/create_cast.sgml
View File

@ -1,6 +1,6 @@
<!-- doc/src/sgml/ref/create_cast.sgml -->
<refentry id="SQL-CREATECAST">
<refentry id="sql-createcast">
<indexterm zone="sql-createcast">
<primary>CREATE CAST</primary>
</indexterm>

2
doc/src/sgml/ref/create_collation.sgml
View File

@ -1,6 +1,6 @@
<!-- doc/src/sgml/ref/create_collation.sgml -->
<refentry id="SQL-CREATECOLLATION">
<refentry id="sql-createcollation">
<indexterm zone="sql-createcollation">
<primary>CREATE COLLATION</primary>
</indexterm>

2
doc/src/sgml/ref/create_conversion.sgml
View File

@ -1,6 +1,6 @@
<!-- doc/src/sgml/ref/create_conversion.sgml -->
<refentry id="SQL-CREATECONVERSION">
<refentry id="sql-createconversion">
<indexterm zone="sql-createconversion">
<primary>CREATE CONVERSION</primary>
</indexterm>

8
doc/src/sgml/ref/create_database.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/create_database.sgml
PostgreSQL documentation
-->
<refentry id="SQL-CREATEDATABASE">
<refentry id="sql-createdatabase">
<indexterm zone="sql-createdatabase">
<primary>CREATE DATABASE</primary>
</indexterm>
@ -45,7 +45,7 @@ CREATE DATABASE <replaceable class="parameter">name</replaceable>
<para>
To create a database, you must be a superuser or have the special
<literal>CREATEDB</literal> privilege.
See <xref linkend="SQL-CREATEUSER">.
See <xref linkend="sql-createuser">.
</para>
<para>
@ -203,11 +203,11 @@ CREATE DATABASE <replaceable class="parameter">name</replaceable>
</para>
<para>
Use <xref linkend="SQL-DROPDATABASE"> to remove a database.
Use <xref linkend="sql-dropdatabase"> to remove a database.
</para>
<para>
The program <xref linkend="APP-CREATEDB"> is a
The program <xref linkend="app-createdb"> is a
wrapper program around this command, provided for convenience.
</para>

6
doc/src/sgml/ref/create_domain.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/create_domain.sgml
PostgreSQL documentation
-->
<refentry id="SQL-CREATEDOMAIN">
<refentry id="sql-createdomain">
<indexterm zone="sql-createdomain">
<primary>CREATE DOMAIN</primary>
</indexterm>
@ -242,7 +242,7 @@ CREATE TABLE us_snail_addy (
</programlisting></para>
</refsect1>
<refsect1 id="SQL-CREATEDOMAIN-compatibility">
<refsect1 id="sql-createdomain-compatibility">
<title>Compatibility</title>
<para>
@ -251,7 +251,7 @@ CREATE TABLE us_snail_addy (
</para>
</refsect1>
<refsect1 id="SQL-CREATEDOMAIN-see-also">
<refsect1 id="sql-createdomain-see-also">
<title>See Also</title>
<simplelist type="inline">

2
doc/src/sgml/ref/create_event_trigger.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/create_event_trigger.sgml
PostgreSQL documentation
-->
<refentry id="SQL-CREATEEVENTTRIGGER">
<refentry id="sql-createeventtrigger">
<indexterm zone="sql-createeventtrigger">
<primary>CREATE EVENT TRIGGER</primary>
</indexterm>

2
doc/src/sgml/ref/create_extension.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/create_extension.sgml
PostgreSQL documentation
-->
<refentry id="SQL-CREATEEXTENSION">
<refentry id="sql-createextension">
<indexterm zone="sql-createextension">
<primary>CREATE EXTENSION</primary>
</indexterm>

2
doc/src/sgml/ref/create_foreign_data_wrapper.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/create_foreign_data_wrapper.sgml
PostgreSQL documentation
-->
<refentry id="SQL-CREATEFOREIGNDATAWRAPPER">
<refentry id="sql-createforeigndatawrapper">
<indexterm zone="sql-createforeigndatawrapper">
<primary>CREATE FOREIGN DATA WRAPPER</primary>
</indexterm>

12
doc/src/sgml/ref/create_foreign_table.sgml
View File

@ -1,6 +1,6 @@
<!-- doc/src/sgml/ref/create_foreign_table.sgml -->
<refentry id="SQL-CREATEFOREIGNTABLE">
<refentry id="sql-createforeigntable">
<indexterm zone="sql-createforeigntable">
<primary>CREATE FOREIGN TABLE</primary>
</indexterm>
@ -51,7 +51,7 @@ CHECK ( <replaceable class="parameter">expression</replaceable> ) [ NO INHERIT ]
</synopsis>
</refsynopsisdiv>
<refsect1 id="SQL-CREATEFOREIGNTABLE-description">
<refsect1 id="sql-createforeigntable-description">
<title>Description</title>
<para>
@ -252,7 +252,7 @@ CHECK ( <replaceable class="parameter">expression</replaceable> ) [ NO INHERIT ]
<para>
The name of an existing foreign server to use for the foreign table.
For details on defining a server, see <xref
linkend="SQL-CREATESERVER">.
linkend="sql-createserver">.
</para>
</listitem>
</varlistentry>
@ -310,7 +310,7 @@ CHECK ( <replaceable class="parameter">expression</replaceable> ) [ NO INHERIT ]
</para>
</refsect1>
<refsect1 id="SQL-CREATEFOREIGNTABLE-examples">
<refsect1 id="sql-createforeigntable-examples">
<title>Examples</title>
<para>
@ -342,8 +342,8 @@ CREATE FOREIGN TABLE measurement_y2016m07
</refsect1>
<refsect1 id="SQL-CREATEFOREIGNTABLE-compatibility">
<title id="SQL-CREATEFOREIGNTABLE-compatibility-title">Compatibility</title>
<refsect1 id="sql-createforeigntable-compatibility">
<title id="sql-createforeigntable-compatibility-title">Compatibility</title>
<para>
The <command>CREATE FOREIGN TABLE</command> command largely conforms to the

4
doc/src/sgml/ref/create_function.sgml
View File

@ -2,7 +2,7 @@
doc/src/sgml/ref/create_function.sgml
-->
<refentry id="SQL-CREATEFUNCTION">
<refentry id="sql-createfunction">
<indexterm zone="sql-createfunction">
<primary>CREATE FUNCTION</primary>
</indexterm>
@ -543,7 +543,7 @@ CREATE [ OR REPLACE ] FUNCTION
the SQL function. The string <replaceable
class="parameter">obj_file</replaceable> is the name of the shared
library file containing the compiled C function, and is interpreted
as for the <xref linkend="SQL-LOAD"> command. The string
as for the <xref linkend="sql-load"> command. The string
<replaceable class="parameter">link_symbol</replaceable> is the
function's link symbol, that is, the name of the function in the C
language source code. If the link symbol is omitted, it is assumed

2
doc/src/sgml/ref/create_group.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/create_group.sgml
PostgreSQL documentation
-->
<refentry id="SQL-CREATEGROUP">
<refentry id="sql-creategroup">
<indexterm zone="sql-creategroup">
<primary>CREATE GROUP</primary>
</indexterm>

16
doc/src/sgml/ref/create_index.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/create_index.sgml
PostgreSQL documentation
-->
<refentry id="SQL-CREATEINDEX">
<refentry id="sql-createindex">
<indexterm zone="sql-createindex">
<primary>CREATE INDEX</primary>
</indexterm>
@ -120,8 +120,8 @@ CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] [ [ IF NOT EXISTS ] <replaceable class=
updates, or deletes on the table; whereas a standard index build
locks out writes (but not reads) on the table until it's done.
There are several caveats to be aware of when using this option
&mdash; see <xref linkend="SQL-CREATEINDEX-CONCURRENTLY"
endterm="SQL-CREATEINDEX-CONCURRENTLY-title">.
&mdash; see <xref linkend="sql-createindex-concurrently"
endterm="sql-createindex-concurrently-title">.
</para>
</listitem>
</varlistentry>
@ -288,8 +288,8 @@ CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] [ [ IF NOT EXISTS ] <replaceable class=
</variablelist>
<refsect2 id="SQL-CREATEINDEX-storage-parameters">
<title id="SQL-CREATEINDEX-storage-parameters-title">Index Storage Parameters</title>
<refsect2 id="sql-createindex-storage-parameters">
<title id="sql-createindex-storage-parameters-title">Index Storage Parameters</title>
<para>
The optional <literal>WITH</literal> clause specifies <firstterm>storage
@ -409,10 +409,10 @@ CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] [ [ IF NOT EXISTS ] <replaceable class=
</variablelist>
</refsect2>
<refsect2 id="SQL-CREATEINDEX-CONCURRENTLY">
<title id="SQL-CREATEINDEX-CONCURRENTLY-title">Building Indexes Concurrently</title>
<refsect2 id="sql-createindex-concurrently">
<title id="sql-createindex-concurrently-title">Building Indexes Concurrently</title>
<indexterm zone="SQL-CREATEINDEX-CONCURRENTLY">
<indexterm zone="sql-createindex-concurrently">
<primary>index</primary>
<secondary>building concurrently</secondary>
</indexterm>

2
doc/src/sgml/ref/create_language.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/create_language.sgml
PostgreSQL documentation
-->
<refentry id="SQL-CREATELANGUAGE">
<refentry id="sql-createlanguage">
<indexterm zone="sql-createlanguage">
<primary>CREATE LANGUAGE</primary>
</indexterm>

2
doc/src/sgml/ref/create_materialized_view.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/create_materialized_view.sgml
PostgreSQL documentation
-->
<refentry id="SQL-CREATEMATERIALIZEDVIEW">
<refentry id="sql-creatematerializedview">
<indexterm zone="sql-creatematerializedview">
<primary>CREATE MATERIALIZED VIEW</primary>
</indexterm>

2
doc/src/sgml/ref/create_opclass.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/create_opclass.sgml
PostgreSQL documentation
-->
<refentry id="SQL-CREATEOPCLASS">
<refentry id="sql-createopclass">
<indexterm zone="sql-createopclass">
<primary>CREATE OPERATOR CLASS</primary>
</indexterm>

2
doc/src/sgml/ref/create_operator.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/create_operator.sgml
PostgreSQL documentation
-->
<refentry id="SQL-CREATEOPERATOR">
<refentry id="sql-createoperator">
<indexterm zone="sql-createoperator">
<primary>CREATE OPERATOR</primary>
</indexterm>

2
doc/src/sgml/ref/create_opfamily.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/create_opfamily.sgml
PostgreSQL documentation
-->
<refentry id="SQL-CREATEOPFAMILY">
<refentry id="sql-createopfamily">
<indexterm zone="sql-createopfamily">
<primary>CREATE OPERATOR FAMILY</primary>
</indexterm>

12
doc/src/sgml/ref/create_policy.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/create_policy.sgml
PostgreSQL documentation
-->
<refentry id="SQL-CREATEPOLICY">
<refentry id="sql-createpolicy">
<indexterm zone="sql-createpolicy">
<primary>CREATE POLICY</primary>
</indexterm>
@ -222,7 +222,7 @@ CREATE POLICY <replaceable class="parameter">name</replaceable> ON <replaceable
<variablelist>
<varlistentry id="SQL-CREATEPOLICY-ALL">
<varlistentry id="sql-createpolicy-all">
<term><literal>ALL</literal></term>
<listitem>
<para>
@ -253,7 +253,7 @@ CREATE POLICY <replaceable class="parameter">name</replaceable> ON <replaceable
</listitem>
</varlistentry>
<varlistentry id="SQL-CREATEPOLICY-SELECT">
<varlistentry id="sql-createpolicy-select">
<term><literal>SELECT</literal></term>
<listitem>
<para>
@ -273,7 +273,7 @@ CREATE POLICY <replaceable class="parameter">name</replaceable> ON <replaceable
</listitem>
</varlistentry>
<varlistentry id="SQL-CREATEPOLICY-INSERT">
<varlistentry id="sql-createpolicy-insert">
<term><literal>INSERT</literal></term>
<listitem>
<para>
@ -294,7 +294,7 @@ CREATE POLICY <replaceable class="parameter">name</replaceable> ON <replaceable
</listitem>
</varlistentry>
<varlistentry id="SQL-CREATEPOLICY-UPDATE">
<varlistentry id="sql-createpolicy-update">
<term><literal>UPDATE</literal></term>
<listitem>
<para>
@ -353,7 +353,7 @@ CREATE POLICY <replaceable class="parameter">name</replaceable> ON <replaceable
</listitem>
</varlistentry>
<varlistentry id="SQL-CREATEPOLICY-DELETE">
<varlistentry id="sql-createpolicy-delete">
<term><literal>DELETE</literal></term>
<listitem>
<para>

2
doc/src/sgml/ref/create_publication.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/create_publication.sgml
PostgreSQL documentation
-->
<refentry id="SQL-CREATEPUBLICATION">
<refentry id="sql-createpublication">
<indexterm zone="sql-createpublication">
<primary>CREATE PUBLICATION</primary>
</indexterm>

16
doc/src/sgml/ref/create_role.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/create_role.sgml
PostgreSQL documentation
-->
<refentry id="SQL-CREATEROLE">
<refentry id="sql-createrole">
<indexterm zone="sql-createrole">
<primary>CREATE ROLE</primary>
</indexterm>
@ -329,8 +329,8 @@ CREATE ROLE <replaceable class="parameter">name</replaceable> [ [ WITH ] <replac
<title>Notes</title>
<para>
Use <xref linkend="SQL-ALTERROLE"> to
change the attributes of a role, and <xref linkend="SQL-DROPROLE">
Use <xref linkend="sql-alterrole"> to
change the attributes of a role, and <xref linkend="sql-droprole">
to remove a role. All the attributes
specified by <command>CREATE ROLE</command> can be modified by later
<command>ALTER ROLE</command> commands.
@ -339,8 +339,8 @@ CREATE ROLE <replaceable class="parameter">name</replaceable> [ [ WITH ] <replac
<para>
The preferred way to add and remove members of roles that are being
used as groups is to use
<xref linkend="SQL-GRANT"> and
<xref linkend="SQL-REVOKE">.
<xref linkend="sql-grant"> and
<xref linkend="sql-revoke">.
</para>
<para>
@ -358,7 +358,7 @@ CREATE ROLE <replaceable class="parameter">name</replaceable> [ [ WITH ] <replac
a member of a role with <literal>CREATEDB</literal> privilege does not immediately
grant the ability to create databases, even if <literal>INHERIT</literal> is set;
it would be necessary to become that role via
<xref linkend="SQL-SET-ROLE"> before
<xref linkend="sql-set-role"> before
creating a database.
</para>
@ -385,7 +385,7 @@ CREATE ROLE <replaceable class="parameter">name</replaceable> [ [ WITH ] <replac
<para>
<productname>PostgreSQL</productname> includes a program <xref
linkend="APP-CREATEUSER"> that has
linkend="app-createuser"> that has
the same functionality as <command>CREATE ROLE</command> (in fact,
it calls this command) but can be run from the command shell.
</para>
@ -402,7 +402,7 @@ CREATE ROLE <replaceable class="parameter">name</replaceable> [ [ WITH ] <replac
with this command. The password will be transmitted to the server
in cleartext, and it might also be logged in the client's command
history or the server log. The command <xref
linkend="APP-CREATEUSER">, however, transmits
linkend="app-createuser">, however, transmits
the password encrypted. Also, <xref linkend="app-psql">
contains a command
<command>\password</command> that can be used to safely change the

2
doc/src/sgml/ref/create_rule.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/create_rule.sgml
PostgreSQL documentation
-->
<refentry id="SQL-CREATERULE">
<refentry id="sql-createrule">
<indexterm zone="sql-createrule">
<primary>CREATE RULE</primary>
</indexterm>

2
doc/src/sgml/ref/create_schema.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/create_schema.sgml
PostgreSQL documentation
-->
<refentry id="SQL-CREATESCHEMA">
<refentry id="sql-createschema">
<indexterm zone="sql-createschema">
<primary>CREATE SCHEMA</primary>
</indexterm>

2
doc/src/sgml/ref/create_sequence.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/create_sequence.sgml
PostgreSQL documentation
-->
<refentry id="SQL-CREATESEQUENCE">
<refentry id="sql-createsequence">
<indexterm zone="sql-createsequence">
<primary>CREATE SEQUENCE</primary>
</indexterm>

2
doc/src/sgml/ref/create_server.sgml
View File

@ -3,7 +3,7 @@ doc/src/sgml/ref/create_server.sgml
PostgreSQL documentation
-->
<refentry id="SQL-CREATESERVER">
<refentry id="sql-createserver">
<indexterm zone="sql-createserver">
<primary>CREATE SERVER</primary>
</indexterm>

Some files were not shown because too many files have changed in this diff Show More