</sect1>
<sect1 id="continuous-archiving">
- <title>Continuous Archiving and Point-In-Time Recovery (PITR)</title>
+ <title>Continuous Archiving and Point-in-Time Recovery (PITR)</title>
<indexterm zone="backup">
<primary>continuous archiving</primary>
</bibliodiv>
<bibliodiv>
- <title>PostgreSQL-Specific Documentation</title>
+ <title>PostgreSQL-specific Documentation</title>
<para>This section is for related documentation.</para>
<biblioentry id="SIM98">
</sect2>
<sect2 id="auth-ident">
- <title>Ident-Based Authentication</title>
+ <title>Ident-based Authentication</title>
<indexterm>
<primary>ident</primary>
</sect2>
<sect2 id="runtime-config-resource-vacuum-cost">
- <title>Cost-Based Vacuum Delay</title>
+ <title>Cost-based Vacuum Delay</title>
<para>
During the execution of <xref linkend="sql-vacuum">
</sect1>
<sect1 id="runtime-config-statistics">
- <title>Run-Time Statistics</title>
+ <title>Run-time Statistics</title>
<sect2 id="runtime-config-statistics-collector">
<title>Query and Index Statistics Collector</title>
<!-- doc/src/sgml/dfunc.sgml -->
<sect2 id="dfunc">
- <title>Compiling and Linking Dynamically-Loaded Functions</title>
+ <title>Compiling and Linking Dynamically-loaded Functions</title>
<para>
Before you are able to use your
</para>
<sect2>
- <title>Cube-Based Earth Distances</title>
+ <title>Cube-based Earth Distances</title>
<para>
Data is stored in cubes that are points (both corners are the same) using 3
</para>
<table id="earthdistance-cube-functions">
- <title>Cube-Based Earthdistance Functions</title>
+ <title>Cube-based Earthdistance Functions</title>
<tgroup cols="3">
<thead>
<row>
</sect2>
<sect2>
- <title>Point-Based Earth Distances</title>
+ <title>Point-based Earth Distances</title>
<para>
The second part of the module relies on representing Earth locations as
</para>
<table id="earthdistance-point-operators">
- <title>Point-Based Earthdistance Operators</title>
+ <title>Point-based Earthdistance Operators</title>
<tgroup cols="3">
<thead>
<row>
</sect3>
<sect3>
- <title>User-Defined Base Types</title>
+ <title>User-defined Base Types</title>
<para>
New user-defined base types are not directly supported by ECPG.
</sect2>
<sect2 id="ecpg-informix-sqlda">
- <title>Informix-Compatible SQLDA Descriptor Areas</title>
+ <title>Informix-compatible SQLDA Descriptor Areas</title>
<para>
Informix-compatible mode supports a different structure than the one described in
<xref linkend="ecpg-sqlda-descriptors">. See below:
</note>
<table id="posix-character-entry-escapes-table">
- <title>Regular Expression Character-Entry Escapes</title>
+ <title>Regular Expression Character-entry Escapes</title>
<tgroup cols="2">
<thead>
</para>
<table id="posix-class-shorthand-escapes-table">
- <title>Regular Expression Class-Shorthand Escapes</title>
+ <title>Regular Expression Class-shorthand Escapes</title>
<tgroup cols="2">
<thead>
</para>
<table id="posix-embedded-options-table">
- <title>ARE Embedded-Option Letters</title>
+ <title>ARE Embedded-option Letters</title>
<tgroup cols="2">
<thead>
</para>
<formalpara>
- <title>Client-Only installation:</title>
+ <title>Client-only installation:</title>
<para>
If you want to install only the client applications and
interface libraries, then you can use these commands:
</sect1>
<sect1 id="installation-platform-notes">
- <title>Platform-Specific Notes</title>
+ <title>Platform-specific Notes</title>
<para>
This section documents additional platform-specific issues
</sect1>
<sect1 id="lo-funcs">
-<title>Server-Side Functions</title>
+<title>Server-side Functions</title>
<para>
There are server-side functions callable from SQL that correspond to
</para>
<sect2 id="locking-tables">
- <title>Table-Level Locks</title>
+ <title>Table-level Locks</title>
<indexterm zone="locking-tables">
<primary>LOCK</primary>
</sect2>
<sect2 id="locking-rows">
- <title>Row-Level Locks</title>
+ <title>Row-level Locks</title>
<para>
In addition to table-level locks, there are row-level locks, which
</sect2>
<sect2 id="nls-guidelines">
- <title>Message-Writing Guidelines</title>
+ <title>Message-writing Guidelines</title>
<para>
Here are some guidelines for writing messages that are easily
</sect2>
<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">
<primary>SELECT INTO</primary>
</sect2>
<sect2>
- <title>Set-Returning Functions</title>
+ <title>Set-returning Functions</title>
<para>
A <application>PL/Python</application> function can also return sets of
scalar or composite types. There are several ways to achieve this because
</para>
<sect2>
- <title>Start-Up</title>
+ <title>Start-up</title>
<para>
To begin a session, a frontend opens a connection to the server and sends
</refsect2>
<refsect2>
- <title>Zero-Column Tables</title>
+ <title>Zero-column Tables</title>
<para>
<productname>PostgreSQL</productname> allows a table of no columns
</itemizedlist>
</sect3>
<sect3>
- <title>Built-In Functions</title>
+ <title>Built-in Functions</title>
<itemizedlist>
<listitem>
</sect2>
<sect2 id="ssl-certificate-creation">
- <title>Creating a Self-Signed Certificate</title>
+ <title>Creating a Self-signed Certificate</title>
<para>
To create a quick self-signed certificate for the server, use the
</sect3>
<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">
<primary>escape string syntax</primary>
</sect3>
<sect3 id="sql-syntax-dollar-quoting">
- <title>Dollar-Quoted String Constants</title>
+ <title>Dollar-quoted String Constants</title>
<indexterm>
<primary>dollar quoting</primary>
</sect3>
<sect3 id="sql-syntax-bit-strings">
- <title>Bit-String Constants</title>
+ <title>Bit-string Constants</title>
<indexterm zone="sql-syntax-bit-strings">
<primary>bit string</primary>
<!-- doc/src/sgml/xaggr.sgml -->
<sect1 id="xaggr">
- <title>User-Defined Aggregates</title>
+ <title>User-defined Aggregates</title>
<indexterm zone="xaggr">
<primary>aggregate function</primary>
<!-- doc/src/sgml/xfunc.sgml -->
<sect1 id="xfunc">
- <title>User-Defined Functions</title>
+ <title>User-defined Functions</title>
<indexterm zone="xfunc">
<primary>function</primary>
</para>
<table tocentry="1" id="xfunc-c-type-table">
- <title>Equivalent C Types for Built-In SQL Types</title>
+ <title>Equivalent C Types for Built-in SQL Types</title>
<tgroup cols="3">
<thead>
<row>
<sect2>
- <title>Composite-Type Arguments</title>
+ <title>Composite-type Arguments</title>
<para>
Composite types do not have a fixed layout like C structures.
<!-- doc/src/sgml/xoper.sgml -->
<sect1 id="xoper">
- <title>User-Defined Operators</title>
+ <title>User-defined Operators</title>
<indexterm zone="xoper">
<primary>operator</primary>
<!-- doc/src/sgml/xtypes.sgml -->
<sect1 id="xtypes">
- <title>User-Defined Types</title>
+ <title>User-defined Types</title>
<indexterm zone="xtypes">
<primary>data type</primary>