aboutsummaryrefslogtreecommitdiff
path: root/doc/src/sgml/ref/create_index.sgml
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2017-10-19 21:16:39 -0400
committerPeter Eisentraut <peter_e@gmx.net>2017-10-20 19:26:10 -0400
commit1ff01b3902cbf5b22d1a439014202499c21b2994 (patch)
tree0eb543455c6b64c46371638230cb7b5ca93fe667 /doc/src/sgml/ref/create_index.sgml
parent36ea99c84d856177ec307307788a279cc600566e (diff)
downloadpostgresql-1ff01b3902cbf5b22d1a439014202499c21b2994.tar.gz
postgresql-1ff01b3902cbf5b22d1a439014202499c21b2994.zip
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>
Diffstat (limited to 'doc/src/sgml/ref/create_index.sgml')
-rw-r--r--doc/src/sgml/ref/create_index.sgml16
1 files changed, 8 insertions, 8 deletions
diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index bb2601dc8c8..92c0090dfd4 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -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>