opensourcemirror
/
postgresql
mirror of git://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Releases Wiki Activity

doc: Clean up title case use 

Note: Following existing practice, titles of formalpara and step are
not titlecased.
This commit is contained in:
Peter Eisentraut 2019-09-08 10:26:35 +02:00
parent db43831899
commit 8e929a4667
52 changed files with 123 additions and 122 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -169,7 +169,7 @@ ORDER BY c.relpages DESC LIMIT 10;
</sect2> </sect2>
<sect2> <sect2>
<title>Optional <parameter>heapallindexed</parameter> verification</title> <title>Optional <parameter>heapallindexed</parameter> Verification</title>
<para> <para>
When the <parameter>heapallindexed</parameter> argument to When the <parameter>heapallindexed</parameter> argument to
verification functions is <literal>true</literal>, an additional verification functions is <literal>true</literal>, an additional
@ -210,7 +210,7 @@ ORDER BY c.relpages DESC LIMIT 10;
</sect2> </sect2>
<sect2> <sect2>
<title>Using <filename>amcheck</filename> effectively</title> <title>Using <filename>amcheck</filename> Effectively</title>
<para> <para>
<filename>amcheck</filename> can be effective at detecting various types of <filename>amcheck</filename> can be effective at detecting various types of
@ -319,7 +319,7 @@ ORDER BY c.relpages DESC LIMIT 10;
</sect2> </sect2>
<sect2> <sect2>
<title>Repairing corruption</title> <title>Repairing Corruption</title>
<para> <para>
No error concerning corruption raised by <filename>amcheck</filename> should No error concerning corruption raised by <filename>amcheck</filename> should
ever be a false positive. <filename>amcheck</filename> raises ever be a false positive. <filename>amcheck</filename> raises

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

@ -114,7 +114,7 @@
</sect1> </sect1>
<sect1 id="connect-estab"> <sect1 id="connect-estab">
<title>How Connections are Established</title> <title>How Connections Are Established</title>
<para> <para>
<productname>PostgreSQL</productname> is implemented using a <productname>PostgreSQL</productname> is implemented using a

7
doc/src/sgml/backup.sgml
View File

@ -824,8 +824,9 @@ test ! -f /mnt/server/archivedir/00000001000000A900000065 &amp;&amp; cp pg_wal/0
way. The non-exclusive method is recommended and the exclusive one is way. The non-exclusive method is recommended and the exclusive one is
deprecated and will eventually be removed. deprecated and will eventually be removed.
</para> </para>
<sect3 id="backup-lowlevel-base-backup-nonexclusive"> <sect3 id="backup-lowlevel-base-backup-nonexclusive">
<title>Making a non-exclusive low level backup</title> <title>Making a Non-Exclusive Low-Level Backup</title>
<para> <para>
A non-exclusive low level backup is one that allows other A non-exclusive low level backup is one that allows other
concurrent backups to be running (both those started using concurrent backups to be running (both those started using
@ -947,7 +948,7 @@ SELECT * FROM pg_stop_backup(false, true);
</para> </para>
</sect3> </sect3>
<sect3 id="backup-lowlevel-base-backup-exclusive"> <sect3 id="backup-lowlevel-base-backup-exclusive">
<title>Making an exclusive low level backup</title> <title>Making an Exclusive Low-Level Backup</title>
<note> <note>
<para> <para>
@ -1082,7 +1083,7 @@ SELECT pg_stop_backup();
</para> </para>
</sect3> </sect3>
<sect3 id="backup-lowlevel-base-backup-data"> <sect3 id="backup-lowlevel-base-backup-data">
<title>Backing up the data directory</title> <title>Backing Up the Data Directory</title>
<para> <para>
Some file system backup tools emit warnings or errors Some file system backup tools emit warnings or errors
if the files they are trying to copy change while the copy proceeds. if the files they are trying to copy change while the copy proceeds.

8
doc/src/sgml/charset.sgml
View File

@ -580,7 +580,7 @@ SELECT * FROM test1 ORDER BY a || b COLLATE "fr_FR";
</para> </para>
<sect4> <sect4>
<title>libc collations</title> <title>libc Collations</title>
<para> <para>
For example, the operating system might For example, the operating system might
@ -637,7 +637,7 @@ SELECT a COLLATE "C" &lt; b COLLATE "POSIX" FROM test1;
</sect4> </sect4>
<sect4> <sect4>
<title>ICU collations</title> <title>ICU Collations</title>
<para> <para>
With ICU, it is not sensible to enumerate all possible locale names. ICU With ICU, it is not sensible to enumerate all possible locale names. ICU
@ -713,7 +713,7 @@ SELECT a COLLATE "C" &lt; b COLLATE "POSIX" FROM test1;
</para> </para>
<sect4> <sect4>
<title>libc collations</title> <title>libc Collations</title>
<para> <para>
New libc collations can be created like this: New libc collations can be created like this:
@ -737,7 +737,7 @@ CREATE COLLATION german (provider = libc, locale = 'de_DE');
</sect4> </sect4>
<sect4> <sect4>
<title>ICU collations</title> <title>ICU Collations</title>
<para> <para>
ICU allows collations to be customized beyond the basic language+country ICU allows collations to be customized beyond the basic language+country

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

@ -5351,7 +5351,7 @@ SELECT * FROM parent WHERE key = 2400;
</indexterm> </indexterm>
<sect2 id="runtime-config-logging-where"> <sect2 id="runtime-config-logging-where">
<title>Where To Log</title> <title>Where to Log</title>
<indexterm zone="runtime-config-logging-where"> <indexterm zone="runtime-config-logging-where">
<primary>where to log</primary> <primary>where to log</primary>
@ -5795,7 +5795,7 @@ local0.* /var/log/postgresql
</variablelist> </variablelist>
</sect2> </sect2>
<sect2 id="runtime-config-logging-when"> <sect2 id="runtime-config-logging-when">
<title>When To Log</title> <title>When to Log</title>
<variablelist> <variablelist>
@ -6011,7 +6011,7 @@ local0.* /var/log/postgresql
</sect2> </sect2>
<sect2 id="runtime-config-logging-what"> <sect2 id="runtime-config-logging-what">
<title>What To Log</title> <title>What to Log</title>
<variablelist> <variablelist>

2
doc/src/sgml/custom-scan.sgml
View File

@ -1,7 +1,7 @@
<!-- doc/src/sgml/custom-scan.sgml --> <!-- doc/src/sgml/custom-scan.sgml -->
<chapter id="custom-scan"> <chapter id="custom-scan">
<title>Writing A Custom Scan Provider</title> <title>Writing a Custom Scan Provider</title>
<indexterm zone="custom-scan"> <indexterm zone="custom-scan">
<primary>custom scan provider</primary> <primary>custom scan provider</primary>

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

@ -1,7 +1,7 @@
<!-- doc/src/sgml/dfunc.sgml --> <!-- doc/src/sgml/dfunc.sgml -->
<sect2 id="dfunc"> <sect2 id="dfunc">
<title>Compiling and Linking Dynamically-loaded Functions</title> <title>Compiling and Linking Dynamically-Loaded Functions</title>
<para> <para>
Before you are able to use your Before you are able to use your

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

@ -247,7 +247,7 @@ checking for fop... fop
</sect1> </sect1>
<sect1 id="docguide-build"> <sect1 id="docguide-build">
<title>Building The Documentation</title> <title>Building the Documentation</title>
<para> <para>
Once you have everything set up, change to the directory Once you have everything set up, change to the directory

8
doc/src/sgml/earthdistance.sgml
View File

@ -24,7 +24,7 @@
</para> </para>
<sect2> <sect2>
<title>Cube-based Earth Distances</title> <title>Cube-Based Earth Distances</title>
<para> <para>
Data is stored in cubes that are points (both corners are the same) using 3 Data is stored in cubes that are points (both corners are the same) using 3
@ -60,7 +60,7 @@
</para> </para>
<table id="earthdistance-cube-functions"> <table id="earthdistance-cube-functions">
<title>Cube-based Earthdistance Functions</title> <title>Cube-Based Earthdistance Functions</title>
<tgroup cols="3"> <tgroup cols="3">
<thead> <thead>
<row> <row>
@ -137,7 +137,7 @@
</sect2> </sect2>
<sect2> <sect2>
<title>Point-based Earth Distances</title> <title>Point-Based Earth Distances</title>
<para> <para>
The second part of the module relies on representing Earth locations as The second part of the module relies on representing Earth locations as
@ -154,7 +154,7 @@
</para> </para>
<table id="earthdistance-point-operators"> <table id="earthdistance-point-operators">
<title>Point-based Earthdistance Operators</title> <title>Point-Based Earthdistance Operators</title>
<tgroup cols="3"> <tgroup cols="3">
<thead> <thead>
<row> <row>

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

@ -1720,7 +1720,7 @@ while (1)
</sect3> </sect3>
<sect3> <sect3>
<title>User-defined Base Types</title> <title>User-Defined Base Types</title>
<para> <para>
New user-defined base types are not directly supported by ECPG. New user-defined base types are not directly supported by ECPG.

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

@ -953,7 +953,7 @@ SELECT * FROM pg_extension_update_paths('<replaceable>extension_name</replaceabl
</sect2> </sect2>
<sect2> <sect2>
<title>Installing Extensions using Update Scripts</title> <title>Installing Extensions Using Update Scripts</title>
<para> <para>
An extension that has been around for awhile will probably exist in An extension that has been around for awhile will probably exist in

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

@ -1,7 +1,7 @@
<!-- doc/src/sgml/fdwhandler.sgml --> <!-- doc/src/sgml/fdwhandler.sgml -->
<chapter id="fdwhandler"> <chapter id="fdwhandler">
<title>Writing A Foreign Data Wrapper</title> <title>Writing a Foreign Data Wrapper</title>
<indexterm zone="fdwhandler"> <indexterm zone="fdwhandler">
<primary>foreign data wrapper</primary> <primary>foreign data wrapper</primary>
@ -96,7 +96,7 @@
</para> </para>
<sect2 id="fdw-callbacks-scan"> <sect2 id="fdw-callbacks-scan">
<title>FDW Routines For Scanning Foreign Tables</title> <title>FDW Routines for Scanning Foreign Tables</title>
<para> <para>
<programlisting> <programlisting>
@ -286,7 +286,7 @@ EndForeignScan(ForeignScanState *node);
</sect2> </sect2>
<sect2 id="fdw-callbacks-join-scan"> <sect2 id="fdw-callbacks-join-scan">
<title>FDW Routines For Scanning Foreign Joins</title> <title>FDW Routines for Scanning Foreign Joins</title>
<para> <para>
If an FDW supports performing foreign joins remotely (rather than If an FDW supports performing foreign joins remotely (rather than
@ -348,7 +348,7 @@ GetForeignJoinPaths(PlannerInfo *root,
</sect2> </sect2>
<sect2 id="fdw-callbacks-upper-planning"> <sect2 id="fdw-callbacks-upper-planning">
<title>FDW Routines For Planning Post-Scan/Join Processing</title> <title>FDW Routines for Planning Post-Scan/Join Processing</title>
<para> <para>
If an FDW supports performing remote post-scan/join processing, such as If an FDW supports performing remote post-scan/join processing, such as
@ -404,7 +404,7 @@ GetForeignUpperPaths(PlannerInfo *root,
</sect2> </sect2>
<sect2 id="fdw-callbacks-update"> <sect2 id="fdw-callbacks-update">
<title>FDW Routines For Updating Foreign Tables</title> <title>FDW Routines for Updating Foreign Tables</title>
<para> <para>
If an FDW supports writable foreign tables, it should provide If an FDW supports writable foreign tables, it should provide
@ -967,7 +967,7 @@ EndDirectModify(ForeignScanState *node);
</sect2> </sect2>
<sect2 id="fdw-callbacks-row-locking"> <sect2 id="fdw-callbacks-row-locking">
<title>FDW Routines For Row Locking</title> <title>FDW Routines for Row Locking</title>
<para> <para>
If an FDW wishes to support <firstterm>late row locking</firstterm> (as described If an FDW wishes to support <firstterm>late row locking</firstterm> (as described
@ -1231,7 +1231,7 @@ AcquireSampleRowsFunc(Relation relation,
</sect2> </sect2>
<sect2 id="fdw-callbacks-import"> <sect2 id="fdw-callbacks-import">
<title>FDW Routines For <command>IMPORT FOREIGN SCHEMA</command></title> <title>FDW Routines for <command>IMPORT FOREIGN SCHEMA</command></title>
<para> <para>
<programlisting> <programlisting>
@ -1394,7 +1394,7 @@ ShutdownForeignScan(ForeignScanState *node);
</sect2> </sect2>
<sect2 id="fdw-callbacks-reparameterize-paths"> <sect2 id="fdw-callbacks-reparameterize-paths">
<title>FDW Routines For reparameterization of paths</title> <title>FDW Routines for Reparameterization of Paths</title>
<para> <para>
<programlisting> <programlisting>

10
doc/src/sgml/features.sgml
View File

@ -200,7 +200,7 @@
</para> </para>
<sect2 id="functions-xml-limits-xpath1"> <sect2 id="functions-xml-limits-xpath1">
<title>Queries are restricted to XPath 1.0</title> <title>Queries Are Restricted to XPath 1.0</title>
<para> <para>
The <productname>PostgreSQL</productname>-specific functions The <productname>PostgreSQL</productname>-specific functions
@ -383,7 +383,7 @@
</sect3> </sect3>
<sect3 id="functions-xml-limits-casts"> <sect3 id="functions-xml-limits-casts">
<title>Mappings between SQL and XML data types and values</title> <title>Mappings between SQL and XML Data Types and Values</title>
<para> <para>
In SQL:2006 and later, both directions of conversion between standard SQL In SQL:2006 and later, both directions of conversion between standard SQL
@ -424,7 +424,7 @@
</para> </para>
<sect3> <sect3>
<title>Only <literal>BY VALUE</literal> passing mechanism is supported</title> <title>Only <literal>BY VALUE</literal> Passing Mechanism Is Supported</title>
<para> <para>
The SQL standard defines two <firstterm>passing mechanisms</firstterm> The SQL standard defines two <firstterm>passing mechanisms</firstterm>
@ -460,7 +460,7 @@ SELECT XMLQUERY('$a is $b' PASSING BY VALUE <replaceable>x</replaceable> AS a, <
</sect3> </sect3>
<sect3> <sect3>
<title>Cannot pass named parameters to queries</title> <title>Cannot Pass Named Parameters to Queries</title>
<para> <para>
The XPath-based functions support passing one parameter to serve as the The XPath-based functions support passing one parameter to serve as the
@ -470,7 +470,7 @@ SELECT XMLQUERY('$a is $b' PASSING BY VALUE <replaceable>x</replaceable> AS a, <
</sect3> </sect3>
<sect3> <sect3>
<title>No <type>XML(SEQUENCE)</type> type</title> <title>No <type>XML(SEQUENCE)</type> Type</title>
<para> <para>
The <productname>PostgreSQL</productname> <type>xml</type> data type The <productname>PostgreSQL</productname> <type>xml</type> data type

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

@ -5206,7 +5206,7 @@ SELECT foo FROM regexp_split_to_table('the quick brown fox', '\s*') AS foo;
</para> </para>
<table id="posix-character-entry-escapes-table"> <table id="posix-character-entry-escapes-table">
<title>Regular Expression Character-entry Escapes</title> <title>Regular Expression Character-Entry Escapes</title>
<tgroup cols="2"> <tgroup cols="2">
<thead> <thead>
@ -5347,7 +5347,7 @@ SELECT foo FROM regexp_split_to_table('the quick brown fox', '\s*') AS foo;
</para> </para>
<table id="posix-class-shorthand-escapes-table"> <table id="posix-class-shorthand-escapes-table">
<title>Regular Expression Class-shorthand Escapes</title> <title>Regular Expression Class-Shorthand Escapes</title>
<tgroup cols="2"> <tgroup cols="2">
<thead> <thead>
@ -5541,7 +5541,7 @@ SELECT foo FROM regexp_split_to_table('the quick brown fox', '\s*') AS foo;
</para> </para>
<table id="posix-embedded-options-table"> <table id="posix-embedded-options-table">
<title>ARE Embedded-option Letters</title> <title>ARE Embedded-Option Letters</title>
<tgroup cols="2"> <tgroup cols="2">
<thead> <thead>
@ -16425,7 +16425,7 @@ WHERE EXISTS (SELECT 1 FROM tab2 WHERE col2 = tab1.col2);
</sect2> </sect2>
<sect2> <sect2>
<title>Single-row Comparison</title> <title>Single-Row Comparison</title>
<indexterm zone="functions-subquery"> <indexterm zone="functions-subquery">
<primary>comparison</primary> <primary>comparison</primary>
@ -19336,7 +19336,7 @@ SELECT collation for ('foo' COLLATE "de_DE");
</para> </para>
<table id="functions-commit-timestamp"> <table id="functions-commit-timestamp">
<title>Committed transaction information</title> <title>Committed Transaction Information</title>
<tgroup cols="3"> <tgroup cols="3">
<thead> <thead>
<row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row> <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
@ -22351,7 +22351,7 @@ CREATE EVENT TRIGGER test_event_trigger_for_drops
</para> </para>
<table id="functions-event-trigger-table-rewrite"> <table id="functions-event-trigger-table-rewrite">
<title>Table Rewrite information</title> <title>Table Rewrite Information</title>
<tgroup cols="3"> <tgroup cols="3">
<thead> <thead>
<row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row> <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
@ -22419,7 +22419,7 @@ CREATE EVENT TRIGGER test_table_rewrite_oid
</para> </para>
<sect2 id="functions-statistics-mcv"> <sect2 id="functions-statistics-mcv">
<title>Inspecting MCV lists</title> <title>Inspecting MCV Lists</title>
<indexterm> <indexterm>
<primary>pg_mcv_list_items</primary> <primary>pg_mcv_list_items</primary>

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

@ -961,7 +961,7 @@ my_fetch(PG_FUNCTION_ARGS)
<title>Implementation</title> <title>Implementation</title>
<sect2 id="gist-buffering-build"> <sect2 id="gist-buffering-build">
<title>GiST buffering build</title> <title>GiST Buffering Build</title>
<para> <para>
Building large GiST indexes by simply inserting all the tuples tends to be Building large GiST indexes by simply inserting all the tuples tends to be
slow, because if the index tuples are scattered across the index and the slow, because if the index tuples are scattered across the index and the

6
doc/src/sgml/high-availability.sgml
View File

@ -938,7 +938,7 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass'
protection. Replication slots overcome these disadvantages. protection. Replication slots overcome these disadvantages.
</para> </para>
<sect3 id="streaming-replication-slots-manipulation"> <sect3 id="streaming-replication-slots-manipulation">
<title>Querying and manipulating replication slots</title> <title>Querying and Manipulating Replication Slots</title>
<para> <para>
Each replication slot has a name, which can contain lower-case letters, Each replication slot has a name, which can contain lower-case letters,
numbers, and the underscore character. numbers, and the underscore character.
@ -1357,7 +1357,7 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)'
</sect2> </sect2>
<sect2 id="continuous-archiving-in-standby"> <sect2 id="continuous-archiving-in-standby">
<title>Continuous archiving in standby</title> <title>Continuous Archiving in Standby</title>
<indexterm> <indexterm>
<primary>continuous archiving</primary> <primary>continuous archiving</primary>
@ -1626,7 +1626,7 @@ if (!triggered)
</sect2> </sect2>
<sect2 id="warm-standby-record"> <sect2 id="warm-standby-record">
<title>Record-based Log Shipping</title> <title>Record-Based Log Shipping</title>
<para> <para>
It is also possible to implement record-based log shipping using this It is also possible to implement record-based log shipping using this

2
doc/src/sgml/install-windows.sgml
View File

@ -338,7 +338,7 @@ $ENV{MSBFLAGS}="/m";
</sect2> </sect2>
<sect2> <sect2>
<title>Special Considerations for 64-bit Windows</title> <title>Special Considerations for 64-Bit Windows</title>
<para> <para>
PostgreSQL will only build for the x64 architecture on 64-bit Windows, there PostgreSQL will only build for the x64 architecture on 64-bit Windows, there

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

@ -342,7 +342,7 @@ su - postgres
</sect1> </sect1>
<sect1 id="install-getsource"> <sect1 id="install-getsource">
<title>Getting The Source</title> <title>Getting the Source</title>
<para> <para>
The <productname>PostgreSQL</productname> &version; sources can be obtained from the The <productname>PostgreSQL</productname> &version; sources can be obtained from the
@ -2136,7 +2136,7 @@ export MANPATH
</sect1> </sect1>
<sect1 id="installation-platform-notes"> <sect1 id="installation-platform-notes">
<title>Platform-specific Notes</title> <title>Platform-Specific Notes</title>
<para> <para>
This section documents additional platform-specific issues This section documents additional platform-specific issues

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

@ -82,7 +82,7 @@
</para> </para>
<sect1 id="intro-whatis"> <sect1 id="intro-whatis">
<title> What is <productname>PostgreSQL</productname>?</title> <title> What Is <productname>PostgreSQL</productname>?</title>
<para> <para>
<productname>PostgreSQL</productname> is an object-relational <productname>PostgreSQL</productname> is an object-relational

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

@ -18,7 +18,7 @@
</para> </para>
<sect1 id="jit-reason"> <sect1 id="jit-reason">
<title>What is <acronym>JIT</acronym> compilation?</title> <title>What Is <acronym>JIT</acronym> compilation?</title>
<para> <para>
Just-in-Time (<acronym>JIT</acronym>) compilation is the process of turning Just-in-Time (<acronym>JIT</acronym>) compilation is the process of turning

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

@ -131,7 +131,7 @@
</para> </para>
<table id="json-type-mapping-table"> <table id="json-type-mapping-table">
<title>JSON primitive types and corresponding <productname>PostgreSQL</productname> types</title> <title>JSON Primitive Types and Corresponding <productname>PostgreSQL</productname> Types</title>
<tgroup cols="3"> <tgroup cols="3">
<thead> <thead>
<row> <row>
@ -233,7 +233,7 @@ SELECT '{"reading": 1.230e-5}'::json, '{"reading": 1.230e-5}'::jsonb;
</sect2> </sect2>
<sect2 id="json-doc-design"> <sect2 id="json-doc-design">
<title>Designing JSON documents effectively</title> <title>Designing JSON Documents Effectively</title>
<para> <para>
Representing data as JSON can be considerably more flexible than Representing data as JSON can be considerably more flexible than
the traditional relational data model, which is compelling in the traditional relational data model, which is compelling in

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

@ -4664,7 +4664,7 @@ int PQflush(PGconn *conn);
</sect1> </sect1>
<sect1 id="libpq-single-row-mode"> <sect1 id="libpq-single-row-mode">
<title>Retrieving Query Results Row-By-Row</title> <title>Retrieving Query Results Row-by-Row</title>
<indexterm zone="libpq-single-row-mode"> <indexterm zone="libpq-single-row-mode">
<primary>libpq</primary> <primary>libpq</primary>

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

@ -11,7 +11,7 @@
</para> </para>
<table id="limits-table"> <table id="limits-table">
<title><productname>PostgreSQL</productname> limitations</title> <title><productname>PostgreSQL</productname> Limitations</title>
<tgroup cols="3"> <tgroup cols="3">
<thead> <thead>
<row> <row>

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

@ -535,7 +535,7 @@ int lo_unlink(PGconn *conn, Oid lobjId);
</sect1> </sect1>
<sect1 id="lo-funcs"> <sect1 id="lo-funcs">
<title>Server-side Functions</title> <title>Server-Side Functions</title>
<para> <para>
Server-side functions tailored for manipulating large objects from SQL are Server-side functions tailored for manipulating large objects from SQL are
@ -543,7 +543,7 @@ int lo_unlink(PGconn *conn, Oid lobjId);
</para> </para>
<table id="lo-funcs-table"> <table id="lo-funcs-table">
<title>SQL-oriented Large Object Functions</title> <title>SQL-Oriented Large Object Functions</title>
<tgroup cols="5"> <tgroup cols="5">
<thead> <thead>
<row> <row>

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

@ -347,7 +347,7 @@
</sect2> </sect2>
<sect2 id="vacuum-for-visibility-map"> <sect2 id="vacuum-for-visibility-map">
<title>Updating The Visibility Map</title> <title>Updating the Visibility Map</title>
<para> <para>
Vacuum maintains a <link linkend="storage-vm">visibility map</link> for each Vacuum maintains a <link linkend="storage-vm">visibility map</link> for each

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

@ -3620,7 +3620,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</table> </table>
<table id="create-index-phases"> <table id="create-index-phases">
<title>CREATE INDEX phases</title> <title>CREATE INDEX Phases</title>
<tgroup cols="2"> <tgroup cols="2">
<thead> <thead>
<row> <row>
@ -3849,7 +3849,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</table> </table>
<table id="vacuum-phases"> <table id="vacuum-phases">
<title>VACUUM phases</title> <title>VACUUM Phases</title>
<tgroup cols="2"> <tgroup cols="2">
<thead> <thead>
<row> <row>
@ -4043,7 +4043,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</table> </table>
<table id="cluster-phases"> <table id="cluster-phases">
<title>CLUSTER and VACUUM FULL phases</title> <title>CLUSTER and VACUUM FULL Phases</title>
<tgroup cols="2"> <tgroup cols="2">
<thead> <thead>
<row> <row>

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

@ -815,7 +815,7 @@ ERROR: could not serialize access due to read/write dependencies among transact
</para> </para>
<sect2 id="locking-tables"> <sect2 id="locking-tables">
<title>Table-level Locks</title> <title>Table-Level Locks</title>
<indexterm zone="locking-tables"> <indexterm zone="locking-tables">
<primary>LOCK</primary> <primary>LOCK</primary>
@ -847,7 +847,7 @@ ERROR: could not serialize access due to read/write dependencies among transact
</para> </para>
<variablelist> <variablelist>
<title>Table-level Lock Modes</title> <title>Table-Level Lock Modes</title>
<varlistentry> <varlistentry>
<term> <term>
<literal>ACCESS SHARE</literal> <literal>ACCESS SHARE</literal>
@ -1167,7 +1167,7 @@ ERROR: could not serialize access due to read/write dependencies among transact
</sect2> </sect2>
<sect2 id="locking-rows"> <sect2 id="locking-rows">
<title>Row-level Locks</title> <title>Row-Level Locks</title>
<para> <para>
In addition to table-level locks, there are row-level locks, which In addition to table-level locks, there are row-level locks, which
@ -1182,7 +1182,7 @@ ERROR: could not serialize access due to read/write dependencies among transact
</para> </para>
<variablelist> <variablelist>
<title>Row-level Lock Modes</title> <title>Row-Level Lock Modes</title>
<varlistentry> <varlistentry>
<term> <term>
<literal>FOR UPDATE</literal> <literal>FOR UPDATE</literal>
@ -1284,7 +1284,7 @@ ERROR: could not serialize access due to read/write dependencies among transact
</para> </para>
<table tocentry="1" id="row-lock-compatibility"> <table tocentry="1" id="row-lock-compatibility">
<title>Conflicting Row-level Locks</title> <title>Conflicting Row-Level Locks</title>
<tgroup cols="5"> <tgroup cols="5">
<colspec colnum="2" colname="lockst"/> <colspec colnum="2" colname="lockst"/>
<colspec colnum="5" colname="lockend"/> <colspec colnum="5" colname="lockend"/>
@ -1336,7 +1336,7 @@ ERROR: could not serialize access due to read/write dependencies among transact
</sect2> </sect2>
<sect2 id="locking-pages"> <sect2 id="locking-pages">
<title>Page-level Locks</title> <title>Page-Level Locks</title>
<para> <para>
In addition to table and row locks, page-level share/exclusive locks are In addition to table and row locks, page-level share/exclusive locks are
@ -1574,7 +1574,7 @@ SELECT pg_advisory_lock(q.id) FROM
</para> </para>
<sect2 id="serializable-consistency"> <sect2 id="serializable-consistency">
<title>Enforcing Consistency With Serializable Transactions</title> <title>Enforcing Consistency with Serializable Transactions</title>
<para> <para>
If the Serializable transaction isolation level is used for all writes If the Serializable transaction isolation level is used for all writes
@ -1612,7 +1612,7 @@ SELECT pg_advisory_lock(q.id) FROM
</sect2> </sect2>
<sect2 id="non-serializable-consistency"> <sect2 id="non-serializable-consistency">
<title>Enforcing Consistency With Explicit Blocking Locks</title> <title>Enforcing Consistency with Explicit Blocking Locks</title>
<para> <para>
When non-serializable writes are possible, When non-serializable writes are possible,

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

@ -433,7 +433,7 @@ fprintf(stderr, gettext("panic level %d\n"), lvl);
</sect2> </sect2>
<sect2 id="nls-guidelines"> <sect2 id="nls-guidelines">
<title>Message-writing Guidelines</title> <title>Message-Writing Guidelines</title>
<para> <para>
Here are some guidelines for writing messages that are easily Here are some guidelines for writing messages that are easily

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

@ -240,7 +240,7 @@ test=# SELECT * FROM heap_page_item_attrs(get_raw_page('pg_class', 0), 'pg_class
</sect2> </sect2>
<sect2> <sect2>
<title>B-tree Functions</title> <title>B-Tree Functions</title>
<variablelist> <variablelist>
<varlistentry> <varlistentry>

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

@ -1291,7 +1291,7 @@ nd | {"1, 2": 33178, "1, 5": 33178, "2, 5": 27435, "1, 2, 5": 33178}
</sect3> </sect3>
<sect3> <sect3>
<title>Multivariate MCV lists</title> <title>Multivariate MCV Lists</title>
<para> <para>
Another type of statistics stored for each column are most-common value Another type of statistics stored for each column are most-common value
@ -1765,7 +1765,7 @@ SELECT * FROM x, y, a, b, c WHERE something AND somethingelse;
</sect2> </sect2>
<sect2 id="populate-pg-dump"> <sect2 id="populate-pg-dump">
<title>Some Notes About <application>pg_dump</application></title> <title>Some Notes about <application>pg_dump</application></title>
<para> <para>
Dump scripts generated by <application>pg_dump</application> automatically apply Dump scripts generated by <application>pg_dump</application> automatically apply

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

@ -587,7 +587,7 @@ EXPLAIN (ANALYZE, TIMING OFF) SELECT COUNT(*) FROM t GROUP BY a, b;
</sect2> </sect2>
<sect2 id="mcv-lists"> <sect2 id="mcv-lists">
<title>MCV lists</title> <title>MCV Lists</title>
<para> <para>
As explained in <xref linkend="functional-dependencies"/>, functional As explained in <xref linkend="functional-dependencies"/>, functional

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

@ -1,7 +1,7 @@
<!-- doc/src/sgml/plhandler.sgml --> <!-- doc/src/sgml/plhandler.sgml -->
<chapter id="plhandler"> <chapter id="plhandler">
<title>Writing A Procedural Language Handler</title> <title>Writing a Procedural Language Handler</title>
<indexterm zone="plhandler"> <indexterm zone="plhandler">
<primary>procedural language</primary> <primary>procedural language</primary>

26
doc/src/sgml/plpgsql.sgml
View File

@ -913,7 +913,7 @@ my_record.user_id := 20;
</sect2> </sect2>
<sect2 id="plpgsql-statements-sql-noresult"> <sect2 id="plpgsql-statements-sql-noresult">
<title>Executing a Command With No Result</title> <title>Executing a Command with No Result</title>
<para> <para>
For any SQL command that does not return rows, for example For any SQL command that does not return rows, for example
@ -984,7 +984,7 @@ PERFORM create_mv('cs_session_page_requests_mv', my_query);
</sect2> </sect2>
<sect2 id="plpgsql-statements-sql-onerow"> <sect2 id="plpgsql-statements-sql-onerow">
<title>Executing a Query with a Single-row Result</title> <title>Executing a Query with a Single-Row Result</title>
<indexterm zone="plpgsql-statements-sql-onerow"> <indexterm zone="plpgsql-statements-sql-onerow">
<primary>SELECT INTO</primary> <primary>SELECT INTO</primary>
@ -1286,7 +1286,7 @@ EXECUTE format('SELECT count(*) FROM %I '
</note> </note>
<example id="plpgsql-quote-literal-example"> <example id="plpgsql-quote-literal-example">
<title>Quoting Values In Dynamic Queries</title> <title>Quoting Values in Dynamic Queries</title>
<indexterm> <indexterm>
<primary>quote_ident</primary> <primary>quote_ident</primary>
@ -1852,7 +1852,7 @@ SELECT * FROM get_available_flightid(CURRENT_DATE);
</sect2> </sect2>
<sect2 id="plpgsql-statements-returning-procedure"> <sect2 id="plpgsql-statements-returning-procedure">
<title>Returning From a Procedure</title> <title>Returning from a Procedure</title>
<para> <para>
A procedure does not have a return value. A procedure can therefore end A procedure does not have a return value. A procedure can therefore end
@ -2419,7 +2419,7 @@ END LOOP;
</sect2> </sect2>
<sect2 id="plpgsql-records-iterating"> <sect2 id="plpgsql-records-iterating">
<title>Looping Through Query Results</title> <title>Looping through Query Results</title>
<para> <para>
Using a different type of <literal>FOR</literal> loop, you can iterate through Using a different type of <literal>FOR</literal> loop, you can iterate through
@ -2504,7 +2504,7 @@ END LOOP <optional> <replaceable>label</replaceable> </optional>;
</sect2> </sect2>
<sect2 id="plpgsql-foreach-array"> <sect2 id="plpgsql-foreach-array">
<title>Looping Through Arrays</title> <title>Looping through Arrays</title>
<para> <para>
The <literal>FOREACH</literal> loop is much like a <literal>FOR</literal> loop, The <literal>FOREACH</literal> loop is much like a <literal>FOR</literal> loop,
@ -2751,7 +2751,7 @@ SELECT merge_db(1, 'dennis');
</example> </example>
<sect3 id="plpgsql-exception-diagnostics"> <sect3 id="plpgsql-exception-diagnostics">
<title>Obtaining Information About an Error</title> <title>Obtaining Information about an Error</title>
<para> <para>
Exception handlers frequently need to identify the specific error that Exception handlers frequently need to identify the specific error that
@ -3420,7 +3420,7 @@ COMMIT;
</sect2> </sect2>
<sect2 id="plpgsql-cursor-for-loop"> <sect2 id="plpgsql-cursor-for-loop">
<title>Looping Through a Cursor's Result</title> <title>Looping through a Cursor's Result</title>
<para> <para>
There is a variant of the <command>FOR</command> statement that allows There is a variant of the <command>FOR</command> statement that allows
@ -4107,7 +4107,7 @@ CREATE TRIGGER emp_stamp BEFORE INSERT OR UPDATE ON emp
</para> </para>
<example id="plpgsql-trigger-audit-example"> <example id="plpgsql-trigger-audit-example">
<title>A <application>PL/pgSQL</application> Trigger Function For Auditing</title> <title>A <application>PL/pgSQL</application> Trigger Function for Auditing</title>
<para> <para>
This example trigger ensures that any insert, update or delete of a row This example trigger ensures that any insert, update or delete of a row
@ -4164,7 +4164,7 @@ AFTER INSERT OR UPDATE OR DELETE ON emp
</para> </para>
<example id="plpgsql-view-trigger-audit-example"> <example id="plpgsql-view-trigger-audit-example">
<title>A <application>PL/pgSQL</application> View Trigger Function For Auditing</title> <title>A <application>PL/pgSQL</application> View Trigger Function for Auditing</title>
<para> <para>
This example uses a trigger on the view to make it updatable, and This example uses a trigger on the view to make it updatable, and
@ -4246,7 +4246,7 @@ INSTEAD OF INSERT OR UPDATE OR DELETE ON emp_view
<example id="plpgsql-trigger-summary-example"> <example id="plpgsql-trigger-summary-example">
<title>A <application>PL/pgSQL</application> Trigger Function For Maintaining A Summary Table</title> <title>A <application>PL/pgSQL</application> Trigger Function for Maintaining a Summary Table</title>
<para> <para>
The schema detailed here is partly based on the <emphasis>Grocery Store The schema detailed here is partly based on the <emphasis>Grocery Store
@ -4531,7 +4531,7 @@ CREATE EVENT TRIGGER snitch ON ddl_command_start EXECUTE FUNCTION snitch();
</sect1> </sect1>
<sect1 id="plpgsql-implementation"> <sect1 id="plpgsql-implementation">
<title><application>PL/pgSQL</application> Under the Hood</title> <title><application>PL/pgSQL</application> under the Hood</title>
<para> <para>
This section discusses some implementation details that are This section discusses some implementation details that are
@ -5059,7 +5059,7 @@ a_output := a_output || $$ if v_$$ || referrer_keys.kind || $$ like '$$
</sect2> </sect2>
<sect2 id="plpgsql-extra-checks"> <sect2 id="plpgsql-extra-checks">
<title>Additional Compile-time and Run-time Checks</title> <title>Additional Compile-Time and Run-Time Checks</title>
<para> <para>
To aid the user in finding instances of simple but common problems before To aid the user in finding instances of simple but common problems before

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

@ -665,7 +665,7 @@ CALL python_triple(5, 10);
</sect2> </sect2>
<sect2> <sect2>
<title>Set-returning Functions</title> <title>Set-Returning Functions</title>
<para> <para>
A <application>PL/Python</application> function can also return sets of A <application>PL/Python</application> function can also return sets of
scalar or composite types. There are several ways to achieve this because scalar or composite types. There are several ways to achieve this because

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

@ -1610,7 +1610,7 @@ ErrorMessage.
</para> </para>
<sect2 id="sasl-scram-sha-256"> <sect2 id="sasl-scram-sha-256">
<title>SCRAM-SHA-256 authentication</title> <title>SCRAM-SHA-256 Authentication</title>
<para> <para>
The implemented SASL mechanisms at the moment The implemented SASL mechanisms at the moment

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

@ -2078,7 +2078,7 @@ CREATE TABLE cities_partdef
</refsect2> </refsect2>
<refsect2> <refsect2>
<title>Non-deferred Uniqueness Constraints</title> <title>Non-Deferred Uniqueness Constraints</title>
<para> <para>
When a <literal>UNIQUE</literal> or <literal>PRIMARY KEY</literal> constraint is When a <literal>UNIQUE</literal> or <literal>PRIMARY KEY</literal> constraint is
@ -2166,7 +2166,7 @@ CREATE TABLE cities_partdef
</refsect2> </refsect2>
<refsect2> <refsect2>
<title>Zero-column Tables</title> <title>Zero-Column Tables</title>
<para> <para>
<productname>PostgreSQL</productname> allows a table of no columns <productname>PostgreSQL</productname> allows a table of no columns

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

@ -273,7 +273,7 @@ GRANT EXECUTE ON function pg_catalog.pg_read_binary_file(text, bigint, bigint, b
</para> </para>
<refsect2> <refsect2>
<title>How it works</title> <title>How It Works</title>
<para> <para>
The basic idea is to copy all file system-level changes from the source The basic idea is to copy all file system-level changes from the source

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

@ -836,7 +836,7 @@ pgbench <optional> <replaceable>options</replaceable> </optional> <replaceable>d
<title>Notes</title> <title>Notes</title>
<refsect2> <refsect2>
<title>What is the <quote>Transaction</quote> Actually Performed in <application>pgbench</application>?</title> <title>What Is the <quote>Transaction</quote> Actually Performed in <application>pgbench</application>?</title>
<para> <para>
<application>pgbench</application> executes test scripts chosen randomly <application>pgbench</application> executes test scripts chosen randomly
@ -1151,7 +1151,7 @@ SELECT 2 AS two, 3 AS three \gset p_
</refsect2> </refsect2>
<refsect2 id="pgbench-builtin-operators"> <refsect2 id="pgbench-builtin-operators">
<title>Built-In Operators</title> <title>Built-in Operators</title>
<para> <para>
The arithmetic, bitwise, comparison and logical operators listed in The arithmetic, bitwise, comparison and logical operators listed in
@ -1161,7 +1161,7 @@ SELECT 2 AS two, 3 AS three \gset p_
</para> </para>
<table id="pgbench-operators"> <table id="pgbench-operators">
<title>pgbench Operators by increasing precedence</title> <title>pgbench Operators by Increasing Precedence</title>
<tgroup cols="4"> <tgroup cols="4">
<thead> <thead>
<row> <row>

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

@ -86,7 +86,7 @@
<title>Usage</title> <title>Usage</title>
<refsect2> <refsect2>
<title>Interpreting results</title> <title>Interpreting Results</title>
<para> <para>
Good results will show most (>90%) individual timing calls take less than Good results will show most (>90%) individual timing calls take less than
@ -116,7 +116,7 @@ Histogram of timing durations:
</refsect2> </refsect2>
<refsect2> <refsect2>
<title>Measuring executor timing overhead</title> <title>Measuring Executor Timing Overhead</title>
<para> <para>
When the query executor is running a statement using When the query executor is running a statement using
@ -145,7 +145,7 @@ EXPLAIN ANALYZE SELECT COUNT(*) FROM t;
</refsect2> </refsect2>
<refsect2> <refsect2>
<title>Changing time sources</title> <title>Changing Time Sources</title>
<para> <para>
On some newer Linux systems, it's possible to change the clock source used On some newer Linux systems, it's possible to change the clock source used
to collect timing data at any time. A second example shows the slowdown to collect timing data at any time. A second example shows the slowdown
@ -223,7 +223,7 @@ Histogram of timing durations:
</refsect2> </refsect2>
<refsect2> <refsect2>
<title>Clock hardware and timing accuracy</title> <title>Clock Hardware and Timing Accuracy</title>
<para> <para>
Collecting accurate timing information is normally done on computers using Collecting accurate timing information is normally done on computers using

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

@ -450,7 +450,7 @@ pg_upgrade.exe
</step> </step>
<step id="pgupgrade-step-replicas"> <step id="pgupgrade-step-replicas">
<title>Upgrade Streaming Replication and Log-Shipping standby servers</title> <title>Upgrade streaming replication and log-shipping standby servers</title>
<para> <para>
If you used link mode and have Streaming Replication (see <xref If you used link mode and have Streaming Replication (see <xref
@ -617,7 +617,7 @@ rsync --archive --delete --hard-links --size-only --no-inc-recursive /vol1/pg_tb
</step> </step>
<step> <step>
<title>Post-Upgrade processing</title> <title>Post-upgrade processing</title>
<para> <para>
If any post-upgrade processing is required, pg_upgrade will issue If any post-upgrade processing is required, pg_upgrade will issue

2
doc/src/sgml/ref/postgres-ref.sgml
View File

@ -391,7 +391,7 @@ PostgreSQL documentation
</refsect2> </refsect2>
<refsect2> <refsect2>
<title>Semi-internal Options</title> <title>Semi-Internal Options</title>
<para> <para>
The options described here are used The options described here are used

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

@ -2621,7 +2621,7 @@ openssl x509 -req -in server.csr -text -days 365 \
</sect1> </sect1>
<sect1 id="gssapi-enc"> <sect1 id="gssapi-enc">
<title>Secure TCP/IP Connections with GSSAPI encryption</title> <title>Secure TCP/IP Connections with GSSAPI Encryption</title>
<indexterm zone="gssapi-enc"> <indexterm zone="gssapi-enc">
<primary>gssapi</primary> <primary>gssapi</primary>

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

@ -26,7 +26,7 @@
</para> </para>
<sect1 id="git"> <sect1 id="git">
<title>Getting The Source via <productname>Git</productname></title> <title>Getting the Source via <productname>Git</productname></title>
<para> <para>
With <productname>Git</productname> you will make a copy of the entire code repository With <productname>Git</productname> you will make a copy of the entire code repository

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

@ -969,7 +969,7 @@ typedef struct spgLeafConsistentOut
</sect2> </sect2>
<sect2 id="spgist-all-the-same"> <sect2 id="spgist-all-the-same">
<title><quote>All-the-same</quote> Inner Tuples</title> <title><quote>All-the-Same</quote> Inner Tuples</title>
<para> <para>
The <acronym>SP-GiST</acronym> core can override the results of the The <acronym>SP-GiST</acronym> core can override the results of the

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

@ -400,7 +400,7 @@ of the LZ family of compression techniques. See
</para> </para>
<sect2 id="storage-toast-ondisk"> <sect2 id="storage-toast-ondisk">
<title>Out-of-line, on-disk TOAST storage</title> <title>Out-of-Line, On-Disk TOAST Storage</title>
<para> <para>
If any of the columns of a table are <acronym>TOAST</acronym>-able, the table will If any of the columns of a table are <acronym>TOAST</acronym>-able, the table will
@ -516,7 +516,7 @@ comparison table, in which all the HTML pages were cut down to 7 kB to fit.
</sect2> </sect2>
<sect2 id="storage-toast-inmemory"> <sect2 id="storage-toast-inmemory">
<title>Out-of-line, in-memory TOAST storage</title> <title>Out-of-Line, In-Memory TOAST Storage</title>
<para> <para>
<acronym>TOAST</acronym> pointers can point to data that is not on disk, but is <acronym>TOAST</acronym> pointers can point to data that is not on disk, but is

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

@ -333,7 +333,7 @@ SELECT 'foo' 'bar';
</sect3> </sect3>
<sect3 id="sql-syntax-strings-escape"> <sect3 id="sql-syntax-strings-escape">
<title>String Constants with C-style Escapes</title> <title>String Constants with C-Style Escapes</title>
<indexterm zone="sql-syntax-strings-escape"> <indexterm zone="sql-syntax-strings-escape">
<primary>escape string syntax</primary> <primary>escape string syntax</primary>
@ -554,7 +554,7 @@ U&amp;'d!0061t!+000061' UESCAPE '!'
</sect3> </sect3>
<sect3 id="sql-syntax-dollar-quoting"> <sect3 id="sql-syntax-dollar-quoting">
<title>Dollar-quoted String Constants</title> <title>Dollar-Quoted String Constants</title>
<indexterm> <indexterm>
<primary>dollar quoting</primary> <primary>dollar quoting</primary>
@ -634,7 +634,7 @@ $function$
</sect3> </sect3>
<sect3 id="sql-syntax-bit-strings"> <sect3 id="sql-syntax-bit-strings">
<title>Bit-string Constants</title> <title>Bit-String Constants</title>
<indexterm zone="sql-syntax-bit-strings"> <indexterm zone="sql-syntax-bit-strings">
<primary>bit string</primary> <primary>bit string</primary>

2
doc/src/sgml/tablesample-method.sgml
View File

@ -1,7 +1,7 @@
<!-- doc/src/sgml/tablesample-method.sgml --> <!-- doc/src/sgml/tablesample-method.sgml -->
<chapter id="tablesample-method"> <chapter id="tablesample-method">
<title>Writing A Table Sampling Method</title> <title>Writing a Table Sampling Method</title>
<indexterm zone="tablesample-method"> <indexterm zone="tablesample-method">
<primary>table sampling method</primary> <primary>table sampling method</primary>

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

@ -1,7 +1,7 @@
<!-- doc/src/sgml/xaggr.sgml --> <!-- doc/src/sgml/xaggr.sgml -->
<sect1 id="xaggr"> <sect1 id="xaggr">
<title>User-defined Aggregates</title> <title>User-Defined Aggregates</title>
<indexterm zone="xaggr"> <indexterm zone="xaggr">
<primary>aggregate function</primary> <primary>aggregate function</primary>

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

@ -1,7 +1,7 @@
<!-- doc/src/sgml/xfunc.sgml --> <!-- doc/src/sgml/xfunc.sgml -->
<sect1 id="xfunc"> <sect1 id="xfunc">
<title>User-defined Functions</title> <title>User-Defined Functions</title>
<indexterm zone="xfunc"> <indexterm zone="xfunc">
<primary>function</primary> <primary>function</primary>
@ -73,7 +73,7 @@
</sect1> </sect1>
<sect1 id="xproc"> <sect1 id="xproc">
<title>User-defined Procedures</title> <title>User-Defined Procedures</title>
<indexterm zone="xproc"> <indexterm zone="xproc">
<primary>procedure</primary> <primary>procedure</primary>
@ -2572,7 +2572,7 @@ CREATE FUNCTION concat_text(text, text) RETURNS text
&dfunc; &dfunc;
<sect2> <sect2>
<title>Composite-type Arguments</title> <title>Composite-Type Arguments</title>
<para> <para>
Composite types do not have a fixed layout like C structures. Composite types do not have a fixed layout like C structures.

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

@ -1,7 +1,7 @@
<!-- doc/src/sgml/xindex.sgml --> <!-- doc/src/sgml/xindex.sgml -->
<sect1 id="xindex"> <sect1 id="xindex">
<title>Interfacing Extensions To Indexes</title> <title>Interfacing Extensions to Indexes</title>
<indexterm zone="xindex"> <indexterm zone="xindex">
<primary>index</primary> <primary>index</primary>
@ -105,7 +105,7 @@
</para> </para>
<table tocentry="1" id="xindex-btree-strat-table"> <table tocentry="1" id="xindex-btree-strat-table">
<title>B-tree Strategies</title> <title>B-Tree Strategies</title>
<tgroup cols="2"> <tgroup cols="2">
<thead> <thead>
<row> <row>
@ -410,7 +410,7 @@
</para> </para>
<table tocentry="1" id="xindex-btree-support-table"> <table tocentry="1" id="xindex-btree-support-table">
<title>B-tree Support Functions</title> <title>B-Tree Support Functions</title>
<tgroup cols="2"> <tgroup cols="2">
<thead> <thead>
<row> <row>

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

@ -1,7 +1,7 @@
<!-- doc/src/sgml/xoper.sgml --> <!-- doc/src/sgml/xoper.sgml -->
<sect1 id="xoper"> <sect1 id="xoper">
<title>User-defined Operators</title> <title>User-Defined Operators</title>
<indexterm zone="xoper"> <indexterm zone="xoper">
<primary>operator</primary> <primary>operator</primary>

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

@ -1,7 +1,7 @@
<!-- doc/src/sgml/xtypes.sgml --> <!-- doc/src/sgml/xtypes.sgml -->
<sect1 id="xtypes"> <sect1 id="xtypes">
<title>User-defined Types</title> <title>User-Defined Types</title>
<indexterm zone="xtypes"> <indexterm zone="xtypes">
<primary>data type</primary> <primary>data type</primary>