rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Properly capitalize documentation headings; some only had initial-word 

capitalization.
This commit is contained in:
Bruce Momjian 2011-01-29 13:00:18 -05:00
parent 6f489dca65
commit 5d5678d7c3
65 changed files with 447 additions and 447 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -15,7 +15,7 @@
</para>
<sect2>
<title>Functions implemented</title>
<title>Functions Implemented</title>
<para>
The functions implemented by <filename>adminpack</> can only be run by a

2
doc/src/sgml/auth-delay.sgml
View File

@ -22,7 +22,7 @@
</para>
<sect2>
<title>Configuration parameters</title>
<title>Configuration Parameters</title>
<variablelist>
<varlistentry>

2
doc/src/sgml/auto-explain.sgml
View File

@ -32,7 +32,7 @@ LOAD 'auto_explain';
</para>
<sect2>
<title>Configuration parameters</title>
<title>Configuration Parameters</title>
<para>
There are several configuration parameters that control the behavior of

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

@ -103,7 +103,7 @@ pg_dump <replaceable class="parameter">dbname</replaceable> &gt; <replaceable cl
</important>
<sect2 id="backup-dump-restore">
<title>Restoring the dump</title>
<title>Restoring the Dump</title>
<para>
The text files created by <application>pg_dump</> are intended to
@ -225,7 +225,7 @@ psql -f <replaceable class="parameter">infile</replaceable> postgres
</sect2>
<sect2 id="backup-dump-large">
<title>Handling large databases</title>
<title>Handling Large Databases</title>
<para>
Some operating systems have maximum file size limits that cause
@ -527,7 +527,7 @@ tar -cf backup.tar /usr/local/pgsql/data
</para>
<sect2 id="backup-archiving-wal">
<title>Setting up WAL archiving</title>
<title>Setting Up WAL Archiving</title>
<para>
In an abstract sense, a running <productname>PostgreSQL</> system
@ -934,7 +934,7 @@ SELECT pg_stop_backup();
</sect2>
<sect2 id="backup-pitr-recovery">
<title>Recovering using a Continuous Archive Backup</title>
<title>Recovering Using a Continuous Archive Backup</title>
<para>
Okay, the worst has happened and you need to recover from your backup.
@ -1193,7 +1193,7 @@ restore_command = 'cp /mnt/server/archivedir/%f %p'
</para>
<sect3 id="backup-standalone">
<title>Standalone hot backups</title>
<title>Standalone Hot Backups</title>
<para>
It is possible to use <productname>PostgreSQL</>'s backup facilities to
@ -1256,7 +1256,7 @@ restore_command = 'gunzip &lt; /mnt/server/archivedir/%f | pg_decompresslog - %p
</sect3>
<sect3 id="backup-scripts">
<title><varname>archive_command</varname> scripts</title>
<title><varname>archive_command</varname> Scripts</title>
<para>
Many people choose to use scripts to define their
@ -1482,7 +1482,7 @@ archive_command = 'local_backup_script.sh'
</variablelist>
<sect2 id="migration-methods-pgdump">
<title>Migrating data via <application>pg_dump</></title>
<title>Migrating Data via <application>pg_dump</></title>
<para>
To dump data from one major version of <productname>PostgreSQL</> and
@ -1562,7 +1562,7 @@ psql -f backup postgres
</sect2>
<sect2 id="migration-methods-other">
<title>Other data migration methods</title>
<title>Other Data Migration Methods</title>
<para>
The <filename>contrib</> program

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

@ -31,7 +31,7 @@
</para>
<sect2>
<title>Example usage</title>
<title>Example Usage</title>
<programlisting>
CREATE TABLE test (a int4);

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

@ -36,7 +36,7 @@
</para>
<sect2>
<title>Example usage</title>
<title>Example Usage</title>
<para>
Simple example using btree_gist instead of btree:

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

@ -1,7 +1,7 @@
<!-- doc/src/sgml/charset.sgml -->
<chapter id="charset">
<title>Localization</>
<title>Localization</title>
<para>
This chapter describes the available localization features from the
@ -44,7 +44,7 @@
</para>
<sect2>
<title>Overview</>
<title>Overview</title>
<para>
Locale support is automatically initialized when a database
@ -198,7 +198,7 @@ initdb --locale=sv_SE
</sect2>
<sect2>
<title>Behavior</>
<title>Behavior</title>
<para>
The locale settings influence the following SQL features:
@ -256,7 +256,7 @@ initdb --locale=sv_SE
</sect2>
<sect2>
<title>Problems</>
<title>Problems</title>
<para>
If locale support doesn't work according to the explanation above,

36
doc/src/sgml/client-auth.sgml
View File

@ -54,7 +54,7 @@
</para>
<sect1 id="auth-pg-hba-conf">
<title>The <filename>pg_hba.conf</filename> file</title>
<title>The <filename>pg_hba.conf</filename> File</title>
<indexterm zone="auth-pg-hba-conf">
<primary>pg_hba.conf</primary>
@ -577,7 +577,7 @@ hostnossl <replaceable>database</replaceable> <replaceable>user</replaceable>
</para>
<example id="example-pg-hba.conf">
<title>Example <filename>pg_hba.conf</filename> entries</title>
<title>Example <filename>pg_hba.conf</filename> Entries</title>
<programlisting>
# Allow any user on the local system to connect to any database with
# any database user name using Unix-domain sockets (the default for local
@ -666,7 +666,7 @@ local db1,db2,@demodbs all md5
</sect1>
<sect1 id="auth-username-maps">
<title>User name maps</title>
<title>User Name Maps</title>
<indexterm zone="auth-username-maps">
<primary>User name maps</primary>
@ -771,7 +771,7 @@ mymap /^(.*)@otherdomain\.com$ guest
</para>
<example id="example-pg-ident.conf">
<title>An example <filename>pg_ident.conf</> file</title>
<title>An Example <filename>pg_ident.conf</> File</title>
<programlisting>
# MAPNAME SYSTEM-USERNAME PG-USERNAME
@ -786,13 +786,13 @@ omicron bryanh guest1
</sect1>
<sect1 id="auth-methods">
<title>Authentication methods</title>
<title>Authentication Methods</title>
<para>
The following subsections describe the authentication methods in more detail.
</para>
<sect2 id="auth-trust">
<title>Trust authentication</title>
<title>Trust Authentication</title>
<para>
When <literal>trust</> authentication is specified,
@ -840,7 +840,7 @@ omicron bryanh guest1
</sect2>
<sect2 id="auth-password">
<title>Password authentication</title>
<title>Password Authentication</title>
<indexterm>
<primary>MD5</>
@ -883,7 +883,7 @@ omicron bryanh guest1
</sect2>
<sect2 id="gssapi-auth">
<title>GSSAPI authentication</title>
<title>GSSAPI Authentication</title>
<indexterm zone="gssapi-auth">
<primary>GSSAPI</primary>
@ -960,7 +960,7 @@ omicron bryanh guest1
</sect2>
<sect2 id="sspi-auth">
<title>SSPI authentication</title>
<title>SSPI Authentication</title>
<indexterm zone="sspi-auth">
<primary>SSPI</primary>
@ -1026,7 +1026,7 @@ omicron bryanh guest1
</sect2>
<sect2 id="kerberos-auth">
<title>Kerberos authentication</title>
<title>Kerberos Authentication</title>
<indexterm zone="kerberos-auth">
<primary>Kerberos</primary>
@ -1198,7 +1198,7 @@ omicron bryanh guest1
</sect2>
<sect2 id="auth-ident">
<title>Ident-based authentication</title>
<title>Ident-Based Authentication</title>
<indexterm>
<primary>ident</primary>
@ -1229,7 +1229,7 @@ omicron bryanh guest1
</para>
<sect3>
<title>Ident Authentication over TCP/IP</title>
<title>Ident Authentication Over TCP/IP</title>
<para>
The <quote>Identification Protocol</quote> is described in
@ -1276,7 +1276,7 @@ omicron bryanh guest1
</sect3>
<sect3>
<title>Ident Authentication over Local Sockets</title>
<title>Ident Authentication Over Local Sockets</title>
<para>
On systems supporting <symbol>SO_PEERCRED</symbol> requests for
@ -1306,7 +1306,7 @@ omicron bryanh guest1
</sect2>
<sect2 id="auth-ldap">
<title>LDAP authentication</title>
<title>LDAP Authentication</title>
<indexterm zone="auth-ldap">
<primary>LDAP</primary>
@ -1450,7 +1450,7 @@ ldapserver=ldap.example.net ldapprefix="cn=" ldapsuffix=", dc=example, dc=net"
</sect2>
<sect2 id="auth-radius">
<title>RADIUS authentication</title>
<title>RADIUS Authentication</title>
<indexterm zone="auth-radius">
<primary>RADIUS</primary>
@ -1539,7 +1539,7 @@ ldapserver=ldap.example.net ldapprefix="cn=" ldapsuffix=", dc=example, dc=net"
</sect2>
<sect2 id="auth-cert">
<title>Certificate authentication</title>
<title>Certificate Authentication</title>
<indexterm zone="auth-cert">
<primary>Certificate</primary>
@ -1575,7 +1575,7 @@ ldapserver=ldap.example.net ldapprefix="cn=" ldapsuffix=", dc=example, dc=net"
</sect2>
<sect2 id="auth-pam">
<title>PAM authentication</title>
<title>PAM Authentication</title>
<indexterm zone="auth-pam">
<primary>PAM</primary>
@ -1621,7 +1621,7 @@ ldapserver=ldap.example.net ldapprefix="cn=" ldapsuffix=", dc=example, dc=net"
</sect1>
<sect1 id="client-authentication-problems">
<title>Authentication problems</title>
<title>Authentication Problems</title>
<para>
Authentication failures and related problems generally

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

@ -3204,7 +3204,7 @@ local0.* /var/log/postgresql
</para>
<table id="runtime-config-severity-levels">
<title>Message severity levels</title>
<title>Message Severity Levels</title>
<tgroup cols="4">
<thead>
<row>
@ -6084,11 +6084,11 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1)
</para>
<table id="runtime-config-short-table">
<title>Short option key</title>
<title>Short Option Key</title>
<tgroup cols="2">
<thead>
<row>
<entry>Short option</entry>
<entry>Short Option</entry>
<entry>Equivalent</entry>
</row>
</thead>

10
doc/src/sgml/contrib-spi.sgml
View File

@ -18,7 +18,7 @@
</para>
<sect2>
<title>refint.c &mdash; functions for implementing referential integrity</title>
<title>refint.c &mdash; Functions for Implementing Referential Integrity</title>
<para>
<function>check_primary_key()</> and
@ -59,7 +59,7 @@
</sect2>
<sect2>
<title>timetravel.c &mdash; functions for implementing time travel</title>
<title>timetravel.c &mdash; Functions for Implementing Time Travel</title>
<para>
Long ago, <productname>PostgreSQL</> had a built-in time travel feature
@ -152,7 +152,7 @@ CREATE TABLE mytab (
</sect2>
<sect2>
<title>autoinc.c &mdash; functions for autoincrementing fields</title>
<title>autoinc.c &mdash; Functions for Autoincrementing Fields</title>
<para>
<function>autoinc()</> is a trigger that stores the next value of
@ -179,7 +179,7 @@ CREATE TABLE mytab (
</sect2>
<sect2>
<title>insert_username.c &mdash; functions for tracking who changed a table</title>
<title>insert_username.c &mdash; Functions for Tracking Who Changed a Table</title>
<para>
<function>insert_username()</> is a trigger that stores the current
@ -200,7 +200,7 @@ CREATE TABLE mytab (
</sect2>
<sect2>
<title>moddatetime.c &mdash; functions for tracking last modification time</title>
<title>moddatetime.c &mdash; Functions for Tracking Last Modification Time</title>
<para>
<function>moddatetime()</> is a trigger that stores the current

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

@ -23,7 +23,7 @@
</para>
<table id="cube-repr-table">
<title>Cube external representations</title>
<title>Cube External Representations</title>
<tgroup cols="2">
<tbody>
<row>
@ -102,7 +102,7 @@
</para>
<table id="cube-gist-operators">
<title>Cube GiST operators</title>
<title>Cube GiST Operators</title>
<tgroup cols="2">
<thead>
<row>
@ -181,7 +181,7 @@
</para>
<table id="cube-functions-table">
<title>Cube functions</title>
<title>Cube Functions</title>
<tgroup cols="2">
<tbody>
<row>

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

@ -1065,7 +1065,7 @@ SELECT '52093.89'::money::numeric::float8;
</para>
<example>
<title>Using the character types</title>
<title>Using the Character Types</title>
<programlisting>
CREATE TABLE test1 (a character(4));
@ -1218,7 +1218,7 @@ SELECT b, char_length(b) FROM test2;
</para>
<sect2>
<title><type>bytea</> hex format</title>
<title><type>bytea</> Hex Format</title>
<para>
The <quote>hex</> format encodes binary data as 2 hexadecimal digits
@ -1245,7 +1245,7 @@ SELECT E'\\xDEADBEEF';
</sect2>
<sect2>
<title><type>bytea</> escape format</title>
<title><type>bytea</> Escape Format</title>
<para>
The <quote>escape</quote> format is the traditional
@ -2492,7 +2492,7 @@ P <replaceable>quantity</> <replaceable>unit</> <optional> <replaceable>quantity
</para>
<table id="datatype-interval-iso8601-units">
<title>ISO 8601 interval unit abbreviations</title>
<title>ISO 8601 Interval Unit Abbreviations</title>
<tgroup cols="2">
<thead>
<row>
@ -2827,7 +2827,7 @@ P <optional> <replaceable>years</>-<replaceable>months</>-<replaceable>days</> <
</para>
<example id="datatype-boolean-example">
<title>Using the <type>boolean</type> type</title>
<title>Using the <type>boolean</type> Type</title>
<programlisting>
CREATE TABLE test1 (a boolean, b text);
@ -3526,7 +3526,7 @@ SELECT person.name, holidays.num_weeks FROM person, holidays
</sect2>
<sect2 id="datatype-macaddr">
<title><type>macaddr</></>
<title><type>macaddr</type></title>
<indexterm>
<primary>macaddr (data type)</primary>
@ -3624,7 +3624,7 @@ SELECT person.name, holidays.num_weeks FROM person, holidays
</para>
<example>
<title>Using the bit string types</title>
<title>Using the Bit String Types</title>
<programlisting>
CREATE TABLE test (a BIT(3), b BIT VARYING(5));

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

@ -9,7 +9,7 @@
</para>
<sect1 id="disk-usage">
<title>Determining Disk Usage</Title>
<title>Determining Disk Usage</title>
<indexterm zone="disk-usage">
<primary>disk usage</primary>

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

@ -1044,7 +1044,7 @@ save_size.pdfjadetex = 15000
</sect2>
<sect2>
<title>Other Emacs modes</title>
<title>Other Emacs Modes</title>
<para>
<productname>GNU Emacs</productname> ships with a different

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

@ -24,7 +24,7 @@
</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
@ -59,7 +59,7 @@
</para>
<table id="earthdistance-cube-functions">
<title>Cube-based earthdistance functions</title>
<title>Cube-Based Earthdistance Functions</title>
<tgroup cols="3">
<thead>
<row>
@ -136,7 +136,7 @@
</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
@ -152,7 +152,7 @@
</para>
<table id="earthdistance-point-operators">
<title>Point-based earthdistance operators</title>
<title>Point-Based Earthdistance Operators</title>
<tgroup cols="3">
<thead>
<row>

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

@ -82,7 +82,7 @@ EXEC SQL ...;
</para>
<sect2 id="ecpg-connecting">
<title>Connecting to the database server</title>
<title>Connecting to the Database Server</title>
<para>
One connects to a database using the following statement:
@ -214,7 +214,7 @@ EXEC SQL CONNECT TO :target USER :user;
</sect2>
<sect2 id="ecpg-set-connection">
<title>Choosing a connection</title>
<title>Choosing a Connection</title>
<para>
SQL statements in embedded SQL programs are by default executed on
@ -295,7 +295,7 @@ current=testdb1 (should be testdb1)
</sect2>
<sect2 id="ecpg-disconnect">
<title>Closing a connection</title>
<title>Closing a Connection</title>
<para>
To close a connection, use the following statement:
@ -352,7 +352,7 @@ EXEC SQL DISCONNECT <optional><replaceable>connection</replaceable></optional>;
</para>
<sect2 id="ecpg-executing">
<title>Executing SQL statements</title>
<title>Executing SQL Statements</title>
<para>
Creating a table:
@ -424,7 +424,7 @@ EXEC SQL SHOW search_path INTO :var;
</sect2>
<sect2 id="ecpg-cursors">
<title>Using cursors</title>
<title>Using Cursors</title>
<para>
To retrieve a result set holding multiple rows, an application has
@ -466,7 +466,7 @@ EXEC SQL COMMIT;
</sect2>
<sect2 id="ecpg-transactions">
<title>Managing transactions</title>
<title>Managing Transactions</title>
<para>
In the default mode, statements are committed only when
@ -525,7 +525,7 @@ EXEC SQL COMMIT;
</sect2>
<sect2 id="ecpg-prepared">
<title>Prepared statements</title>
<title>Prepared Statements</title>
<para>
When the values to be passed to an SQL statement are not known at
@ -696,7 +696,7 @@ EXEC SQL int i = 4;
</sect2>
<sect2 id="ecpg-retrieving">
<title>Retrieving query results</title>
<title>Retrieving Query Results</title>
<para>
Now you should be able to pass data generated by your program into
@ -768,7 +768,7 @@ do
</sect2>
<sect2 id="ecpg-variables-type-mapping">
<title>Type mapping</title>
<title>Type Mapping</title>
<para>
When ECPG applications exchange values between the PostgreSQL
@ -799,7 +799,7 @@ do
</para>
<table id="ecpg-datatype-hostvars-table">
<title>Mapping between PostgreSQL data types and C variable types</title>
<title>Mapping Between PostgreSQL Data Types and C Variable Types</title>
<tgroup cols="2">
<thead>
<row>
@ -893,7 +893,7 @@ do
</table>
<sect3 id="ecpg-char">
<title>Handling character strings</title>
<title>Handling Character Strings</title>
<para>
To handle SQL character string data types, such
@ -967,7 +967,7 @@ VARCHAR v2[128];
</sect3>
<sect3 id="ecpg-special-types">
<title>Accessing special data types</title>
<title>Accessing Special Data Types</title>
<para>
ECPG contains some special types that help you to interact easily
@ -1158,7 +1158,7 @@ EXEC SQL END DECLARE SECTION;
</sect3>
<sect3 id="ecpg-variables-nonprimitive-c">
<title>Host variables with nonprimitive types</title>
<title>Host Variables with Nonprimitive Types</title>
<para>
As a host variable you can also use arrays, typedefs, structs, and
@ -1374,7 +1374,7 @@ EXEC SQL END DECLARE SECTION;
</sect2>
<sect2 id="ecpg-variables-nonprimitive-sql">
<title>Handling nonprimitive SQL data types</title>
<title>Handling Nonprimitive SQL Data Types</title>
<para>
This section contains information on how to handle nonscalar and
@ -1504,7 +1504,7 @@ while (1)
</sect3>
<sect3>
<title>Composite types</title>
<title>Composite Types</title>
<para>
Composite types are not directly supported in ECPG, but an easy workaround is possible.
@ -1624,7 +1624,7 @@ while (1)
</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.
@ -1772,7 +1772,7 @@ EXEC SQL SELECT b INTO :val :val_ind FROM test1;
</para>
<sect2 id="ecpg-dynamic-without-result">
<title>Executing statements without a result set</title>
<title>Executing Statements without a Result Set</title>
<para>
The simplest way to execute an arbitrary SQL statement is to use
@ -1794,7 +1794,7 @@ EXEC SQL EXECUTE IMMEDIATE :stmt;
</sect2>
<sect2 id="ecpg-dynamic-input">
<title>Executing a statement with input parameters</title>
<title>Executing a Statement with Input Parameters</title>
<para>
A more powerful way to execute arbitrary SQL statements is to
@ -1825,7 +1825,7 @@ EXEC SQL DEALLOCATE PREPARE <replaceable>name</replaceable>;
</sect2>
<sect2 id="ecpg-dynamic-with-result">
<title>Executing a statement with a result set</title>
<title>Executing a Statement with a Result Set</title>
<para>
To execute an SQL statement with a single result row,
@ -1887,7 +1887,7 @@ EXEC SQL DISCONNECT ALL;
</sect1>
<sect1 id="ecpg-pgtypes">
<title>pgtypes library</title>
<title>pgtypes Library</title>
<para>
The pgtypes library maps <productname>PostgreSQL</productname> database
@ -1914,7 +1914,7 @@ free(out);
</para>
<sect2 id="ecpg-pgtypes-numeric">
<title>The numeric type</title>
<title>The numeric Type</title>
<para>
The numeric type offers to do calculations with arbitrary precision. See
<xref linkend="datatype-numeric"> for the equivalent type in the
@ -2237,7 +2237,7 @@ int PGTYPESnumeric_from_decimal(decimal *src, numeric *dst);
</sect2>
<sect2 id="ecpg-pgtypes-date">
<title>The date type</title>
<title>The date Type</title>
<para>
The date type in C enables your programs to deal with data of the SQL type
date. See <xref linkend="datatype-datetime"> for the equivalent type in the
@ -2282,7 +2282,7 @@ date PGTYPESdate_from_asc(char *str, char **endptr);
<xref linkend="ecpg-pgtypesdate-from-asc-table"> shows the allowed input formats.
</para>
<table id="ecpg-pgtypesdate-from-asc-table">
<title>Valid input formats for <function>PGTYPESdate_from_asc</function></title>
<title>Valid Input Formats for <function>PGTYPESdate_from_asc</function></title>
<tgroup cols="2">
<thead>
<row>
@ -2539,7 +2539,7 @@ int PGTYPESdate_fmt_asc(date dDate, char *fmtstring, char *outbuf);
the same date: November 23, 1959.
</para>
<table id="ecpg-pgtypesdate-fmt-asc-example-table">
<title>Valid input formats for <function>PGTYPESdate_fmt_asc</function></title>
<title>Valid Input Formats for <function>PGTYPESdate_fmt_asc</function></title>
<tgroup cols="2">
<thead>
<row>
@ -2629,7 +2629,7 @@ int PGTYPESdate_defmt_asc(date *d, char *fmt, char *str);
you an idea of how to use this function.
</para>
<table id="ecpg-rdefmtdate-example-table">
<title>Valid input formats for <function>rdefmtdate</function></title>
<title>Valid Input Formats for <function>rdefmtdate</function></title>
<tgroup cols="3">
<thead>
<row>
@ -2714,7 +2714,7 @@ int PGTYPESdate_defmt_asc(date *d, char *fmt, char *str);
</sect2>
<sect2 id="ecpg-pgtypes-timestamp">
<title>The timestamp type</title>
<title>The timestamp Type</title>
<para>
The timestamp type in C enables your programs to deal with data of the SQL
type timestamp. See <xref linkend="datatype-datetime"> for the equivalent
@ -2756,7 +2756,7 @@ timestamp PGTYPEStimestamp_from_asc(char *str, char **endptr);
<xref linkend="ecpg-pgtypestimestamp-from-asc-example-table"> contains a few examples for input strings.
</para>
<table id="ecpg-pgtypestimestamp-from-asc-example-table">
<title>Valid input formats for <function>PGTYPEStimestamp_from_asc</function></title>
<title>Valid Input Formats for <function>PGTYPEStimestamp_from_asc</function></title>
<tgroup cols="2">
<thead>
<row>
@ -3243,7 +3243,7 @@ int PGTYPEStimestamp_sub_interval(timestamp *tin, interval *span, timestamp *tou
</sect2>
<sect2 id="ecpg-pgtypes-interval">
<title>The interval type</title>
<title>The interval Type</title>
<para>
The interval type in C enables your programs to deal with data of the SQL
type interval. See <xref linkend="datatype-datetime"> for the equivalent
@ -3330,7 +3330,7 @@ int PGTYPESinterval_copy(interval *intvlsrc, interval *intvldest);
</sect2>
<sect2 id="ecpg-pgtypes-decimal">
<title>The decimal type</title>
<title>The decimal Type</title>
<para>
The decimal type is similar to the numeric type. However it is limited to
a maximum precision of 30 significant digits. In contrast to the numeric
@ -3374,7 +3374,7 @@ void PGTYPESdecimal_free(decimal *var);
</sect2>
<sect2 id="ecpg-pgtypes-errno">
<title>errno values of pgtypeslib</title>
<title>errno Values of pgtypeslib</title>
<para>
<variablelist>
<varlistentry>
@ -3516,7 +3516,7 @@ void PGTYPESdecimal_free(decimal *var);
</sect2>
<sect2 id="ecpg-pgtypes-constants">
<title>Special constants of pgtypeslib</title>
<title>Special Constants of pgtypeslib</title>
<para>
<variablelist>
<varlistentry id="PGTYPESInvalidTimestamp">
@ -3557,7 +3557,7 @@ void PGTYPESdecimal_free(decimal *var);
</para>
<sect2 id="ecpg-named-descriptors">
<title>Named SQL descriptor areas</title>
<title>Named SQL Descriptor Areas</title>
<para>
A named SQL descriptor area consists of a header, which contains
@ -3815,7 +3815,7 @@ EXEC SQL GET DESCRIPTOR mydesc VALUE 1 :id = DATA;
</sect2>
<sect2 id="ecpg-sqlda-descriptors">
<title>SQLDA descriptor areas</title>
<title>SQLDA Descriptor Areas</title>
<para>
An SQLDA Descriptor Area is a C language structure which can be also used
@ -3852,7 +3852,7 @@ EXEC SQL DESCRIBE prepared_statement INTO mysqlda;
</procedure>
<sect3>
<title>SQLDA data structure</title>
<title>SQLDA Datac Structure</title>
<para>
SQLDA uses three data structure
@ -3869,7 +3869,7 @@ EXEC SQL DESCRIBE prepared_statement INTO mysqlda;
</tip>
<sect4 id="ecpg-sqlda-sqlda">
<title>sqlda_t structure</title>
<title>sqlda_t Structure</title>
<para>
The structure type <type>sqlda_t</type> is the type of the
@ -3966,7 +3966,7 @@ typedef struct sqlda_struct sqlda_t;
</sect4>
<sect4 id="ecpg-sqlda-sqlvar">
<title>sqlvar_t structure</title>
<title>sqlvar_t Structure</title>
<para>
The structure type <type>sqlvar_t</type> holds a column value
@ -4041,7 +4041,7 @@ typedef struct sqlvar_struct sqlvar_t;
</sect4>
<sect4 id="ecpg-sqlda-sqlname">
<title>struct sqlname structure</title>
<title>struct sqlname Structure</title>
<para>
A <type>struct sqlname</type> structure holds a column name. It
@ -4080,7 +4080,7 @@ struct sqlname
</sect3>
<sect3 id="ecpg-sqlda-output">
<title>Retreiving a result set using an SQLDA</title>
<title>Retreiving a Result Set Using an SQLDA</title>
<procedure>
<para>
@ -4169,7 +4169,7 @@ switch (v.sqltype)
</sect3>
<sect3 id="ecpg-sqlda-input">
<title>Passing query parameters using an SQLDA</title>
<title>Passing Query Parameters Using an SQLDA</title>
<procedure>
<para>
@ -4255,7 +4255,7 @@ free(sqlda2);
</sect3>
<sect3 id="ecpg-sqlda-example">
<title>A sample application using SQLDA</title>
<title>A Sample Application Using SQLDA</title>
<para>
Here is an example program, which describes how to fetch access
@ -4426,7 +4426,7 @@ main(void)
</para>
<example id="ecpg-sqlda-example-example">
<title>Example SQLDA program</title>
<title>Example SQLDA Program</title>
<programlisting>
#include &lt;stdlib.h>
#include &lt;string.h>
@ -4633,7 +4633,7 @@ tup_deleted = 0 (type: 9)
</para>
<sect2 id="ecpg-whenever">
<title>Setting callbacks</title>
<title>Setting Callbacks</title>
<para>
One simple method to catch errors and warnings is to set a
@ -4954,7 +4954,7 @@ sqlstate: 42P01
</sect2>
<sect2 id="ecpg-sqlstate-sqlcode">
<title><literal>SQLSTATE</literal> vs <literal>SQLCODE</literal></title>
<title><literal>SQLSTATE</literal> vs. <literal>SQLCODE</literal></title>
<para>
The fields <literal>sqlca.sqlstate</literal> and
@ -5469,7 +5469,7 @@ while (1)
</sect1>
<sect1 id="ecpg-preproc">
<title>Preprocessor directives</title>
<title>Preprocessor Directives</title>
<para>
Several preprocessor directives are available that modify how
@ -5478,7 +5478,7 @@ while (1)
</para>
<sect2 id="ecpg-include">
<title>Including files</title>
<title>Including Files</title>
<para>
To include an external file into your embedded SQL program, use:
@ -5537,7 +5537,7 @@ EXEC SQL INCLUDE "<replaceable>filename</replaceable>";
</sect2>
<sect2 id="ecpg-define">
<title>The define and undef directives</title>
<title>The define and undef Directives</title>
<para>
Similar to the directive <literal>#define</literal> that is known from C,
embedded SQL has a similar concept:
@ -5580,7 +5580,7 @@ EXEC SQL UPDATE Tbl SET col = MYNUMBER;
</sect2>
<sect2 id="ecpg-ifdef">
<title>ifdef, ifndef, else, elif, and endif directives</title>
<title>ifdef, ifndef, else, elif, and endif Directives</title>
<para>
You can use the following directives to compile code sections conditionally:
@ -5842,7 +5842,7 @@ ECPG = ecpg
</para>
<example id="ecpg-lo-example">
<title>ECPG program accessing large objects</title>
<title>ECPG Program Accessing Large Objects</title>
<programlisting><![CDATA[
#include <stdio.h>
#include <stdlib.h>
@ -5960,7 +5960,7 @@ main(void)
</para>
<sect2 id="ecpg-cpp-scope">
<title>Scope for host variables</title>
<title>Scope for Host Variables</title>
<para>
The <command>ecpg</command> preprocessor understands the scope of
@ -6038,7 +6038,7 @@ void TestCpp::test()
</sect2>
<sect2 id="ecpg-cpp-and-c">
<title>C++ application development with external C module</title>
<title>C++ Application Development with External C Module</title>
<para>
If you understand these technical limitations of
@ -7873,7 +7873,7 @@ $COMMIT;
</para>
<sect2 id="ecpg-informix-types">
<title>Additional types</title>
<title>Additional Types</title>
<para>
The Informix-special "string" pseudo-type for storing right-trimmed character string data is now
supported in Informix-mode without using <literal>typedef</literal>. In fact, in Informix-mode,
@ -7889,7 +7889,7 @@ EXEC SQL FETCH MYCUR INTO :userid;
</sect2>
<sect2 id="ecpg-informix-statements">
<title>Additional/missing embedded SQL statements</title>
<title>Additional/Missing Embedded SQL Statements</title>
<para>
<variablelist>
<varlistentry>
@ -7931,7 +7931,7 @@ EXEC SQL CLOSE DATABASE;
</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:
@ -8208,7 +8208,7 @@ EXEC SQL INCLUDE sqlda.h;
</sect2>
<sect2 id="ecpg-informix-functions">
<title>Additional functions</title>
<title>Additional Functions</title>
<para>
<variablelist>
<varlistentry>
@ -9266,7 +9266,7 @@ risnull(CINTTYPE, (char *) &i);
</sect2>
<sect2 id="ecpg-informix-constants">
<title>Additional constants</title>
<title>Additional Constants</title>
<para>
Note that all constants here describe errors and all of them are defined
to represent negative values. In the descriptions of the different

2
doc/src/sgml/external-projects.sgml
View File

@ -61,7 +61,7 @@
</para>
<table id="language-interface-table">
<title>Externally Maintained Client Interfaces</>
<title>Externally Maintained Client Interfaces</title>
<tgroup cols="4">
<thead>

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

@ -9535,7 +9535,7 @@ table2-mapping
</para>
<figure id="xslt-xml-html">
<title>XSLT stylesheet for converting SQL/XML output to HTML</title>
<title>XSLT Stylesheet for Converting SQL/XML Output to HTML</title>
<programlisting><![CDATA[
<?xml version="1.0"?>
<xsl:stylesheet version="1.0"
@ -13618,7 +13618,7 @@ SELECT typlen FROM pg_type WHERE oid = pg_typeof(33);
</para>
<table id="functions-txid-snapshot">
<title>Transaction IDs and snapshots</title>
<title>Transaction IDs and Snapshots</title>
<tgroup cols="3">
<thead>
<row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
@ -13671,7 +13671,7 @@ SELECT typlen FROM pg_type WHERE oid = pg_typeof(33);
</para>
<table id="functions-txid-snapshot-parts">
<title>Snapshot components</title>
<title>Snapshot Components</title>
<tgroup cols="2">
<thead>
<row>

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

@ -319,7 +319,7 @@
</para>
<sect2 id="gin-fast-update">
<title>GIN fast update technique</title>
<title>GIN Fast Update Technique</title>
<para>
Updating a <acronym>GIN</acronym> index tends to be slow because of the
@ -357,7 +357,7 @@
</sect2>
<sect2 id="gin-partial-match">
<title>Partial match algorithm</title>
<title>Partial Match Algorithm</title>
<para>
GIN can support <quote>partial match</> queries, in which the query
@ -378,11 +378,11 @@
</sect1>
<sect1 id="gin-tips">
<title>GIN tips and tricks</title>
<title>GIN Tips and Tricks</title>
<variablelist>
<varlistentry>
<term>Create vs insert</term>
<term>Create vs. insert</term>
<listitem>
<para>
Insertion into a <acronym>GIN</acronym> index can be slow

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

@ -82,7 +82,7 @@
</para>
<sect1 id="different-replication-solutions">
<title>Comparison of different solutions</title>
<title>Comparison of Different Solutions</title>
<variablelist>
@ -960,7 +960,7 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass'
</sect1>
<sect1 id="log-shipping-alternative">
<title>Alternative method for log shipping</title>
<title>Alternative Method for Log Shipping</title>
<para>
An alternative to the built-in standby mode described in the previous
@ -1377,7 +1377,7 @@ if (!triggered)
</sect2>
<sect2 id="hot-standby-conflict">
<title>Handling query conflicts</title>
<title>Handling Query Conflicts</title>
<para>
The primary and standby servers are in many ways loosely connected. Actions

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

@ -262,7 +262,7 @@ $ENV{PATH}=$ENV{PATH} . ';c:\some\where\bison\bin';
</sect2>
<sect2>
<title>Special considerations for 64-bit Windows</title>
<title>Special Considerations for 64-bit Windows</title>
<para>
PostgreSQL will only build for the x64 architecture on 64-bit Windows, there
@ -324,7 +324,7 @@ $ENV{CONFIG}="Debug";
</sect2>
<sect2>
<title>Cleaning and installing</title>
<title>Cleaning and Installing</title>
<para>
Most of the time, the automatic dependency tracking in Visual Studio will
@ -349,7 +349,7 @@ $ENV{CONFIG}="Debug";
</sect2>
<sect2>
<title>Running the regression tests</title>
<title>Running the Regression Tests</title>
<para>
To run the regression tests, make sure you have completed the build of all
@ -378,7 +378,7 @@ $ENV{CONFIG}="Debug";
</sect2>
<sect2>
<title>Building the documentation</title>
<title>Building the Documentation</title>
<para>
Building the PostgreSQL documentation in HTML format requires several tools
@ -481,7 +481,7 @@ $ENV{DOCROOT}='c:\docbook';
</para>
<sect2>
<title>Generated files</title>
<title>Generated Files</title>
<para>
The following files will be built:

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

@ -527,7 +527,7 @@ su - postgres
<procedure>
<step id="configure">
<title>Configuration</>
<title>Configuration</title>
<indexterm zone="configure">
<primary>configure</primary>
@ -1676,7 +1676,7 @@ PostgreSQL, contrib and HTML documentation successfully made. Ready to install.
</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:
@ -2184,7 +2184,7 @@ kill `cat /usr/local/pgsql/data/postmaster.pid`
</para>
<sect3>
<title>GCC issues</title>
<title>GCC Issues</title>
<para>
On AIX 5.3, there have been some problems getting PostgreSQL to
@ -2202,7 +2202,7 @@ kill `cat /usr/local/pgsql/data/postmaster.pid`
</sect3>
<sect3>
<title>Unix-domain sockets broken</title>
<title>Unix-Domain Sockets Broken</title>
<para>
AIX 5.3 has a problem
@ -2228,7 +2228,7 @@ kill `cat /usr/local/pgsql/data/postmaster.pid`
</sect3>
<sect3>
<title>Internet address issues</title>
<title>Internet Address Issues</title>
<para>
PostgreSQL relies on the system's <function>getaddrinfo</> function
@ -2300,7 +2300,7 @@ hosts=local4,bind4
</sect3>
<sect3>
<title>Memory management</title>
<title>Memory Management</title>
<!-- http://archives.postgresql.org/message-id/603bgqmpl9.fsf@dba2.int.libertyrms.com -->
<para>
@ -2395,7 +2395,7 @@ createlang: language installation failed: ERROR: could not load library "/opt/d
</para>
<bibliography>
<title>References and resources</title>
<title>References and Resources</title>
<biblioentry>
<biblioset relation="article">
@ -2740,7 +2740,7 @@ cc-1020 cc: ERROR File = pqcomm.c, Line = 427
</para>
<sect3>
<title>Collecting crash dumps on Windows</title>
<title>Collecting Crash Dumps on Windows</title>
<para>
If PostgreSQL on Windows crashes, it has the ability to generate
@ -2862,7 +2862,7 @@ cc-1020 cc: ERROR File = pqcomm.c, Line = 427
</sect3>
<sect3>
<title>Reading the PostgreSQL man pages</title>
<title>Reading the PostgreSQL Man Pages</title>
<para>
By default, the PostgreSQL man pages are installed into
@ -2936,7 +2936,7 @@ MANPATH=/usr/lib/scohelp/%L/man:/usr/dt/man:/usr/man:/usr/share/man:scohelp:/usr
</para>
<sect3>
<title>Required tools</title>
<title>Required Tools</title>
<para>
You can build with either GCC or Sun's compiler suite. For
@ -2986,7 +2986,7 @@ MANPATH=/usr/lib/scohelp/%L/man:/usr/dt/man:/usr/man:/usr/share/man:scohelp:/usr
</sect3>
<sect3>
<title>configure complains about a failed test program</title>
<title>configure Complains About a Failed Test Program</title>
<para>
If <command>configure</command> complains about a failed test
@ -3005,7 +3005,7 @@ configure ... LDFLAGS="-R /usr/sfw/lib:/opt/sfw/lib:/usr/local/lib"
</sect3>
<sect3>
<title>64-bit build sometimes crashes</title>
<title>64-bit Build Sometimes Crashes</title>
<para>
On Solaris 7 and older, the 64-bit version of libc has a buggy
@ -3029,7 +3029,7 @@ LIBOBJS = snprintf.o
</sect3>
<sect3>
<title>Compiling for optimal performance</title>
<title>Compiling for Optimal Performance</title>
<para>
On the SPARC architecture, Sun Studio is strongly recommended for
@ -3062,7 +3062,7 @@ LIBOBJS = snprintf.o
</sect3>
<sect3>
<title>Using DTrace for tracing PostgreSQL</title>
<title>Using DTrace for Tracing PostgreSQL</title>
<para>
Yes, using DTrace is possible. See <![%standalone-include[the

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

@ -22,7 +22,7 @@
</para>
<sect2>
<title>Data types</title>
<title>Data Types</title>
<para>
<xref linkend="isn-datatypes"> shows the data types provided by
@ -30,11 +30,11 @@
</para>
<table id="isn-datatypes">
<title><filename>isn</filename> data types</title>
<title><filename>isn</filename> Data Types</title>
<tgroup cols="2">
<thead>
<row>
<entry>Data type</entry>
<entry>Data Type</entry>
<entry>Description</entry>
</row>
</thead>
@ -228,7 +228,7 @@
</para>
<table id="isn-functions">
<title><filename>isn</> functions</title>
<title><filename>isn</> Functions</title>
<tgroup cols="3">
<thead>
<row>

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

@ -359,7 +359,7 @@ PGconn *PQconnectdbParams(const char **keywords, const char **values, int expand
</para>
<table id="libpq-connect-sslmode-options">
<title><literal>sslmode</literal> options</title>
<title><literal>sslmode</literal> Options</title>
<tgroup cols="2">
<thead>
<row>
@ -7534,7 +7534,7 @@ main(int argc, char **argv)
</example>
<example id="libpq-example-3">
<title><application>libpq</application> Example Program 3</>
<title><application>libpq</application> Example Program 3</title>
<programlisting>
<![CDATA[

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

@ -34,7 +34,7 @@
</para>
<sect1 id="monitoring-ps">
<title>Standard Unix Tools</Title>
<title>Standard Unix Tools</title>
<indexterm zone="monitoring-ps">
<primary>ps</primary>
@ -106,7 +106,7 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
</sect1>
<sect1 id="monitoring-stats">
<title>The Statistics Collector</Title>
<title>The Statistics Collector</title>
<indexterm zone="monitoring-stats">
<primary>statistics</primary>
@ -129,7 +129,7 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
</para>
<sect2 id="monitoring-stats-setup">
<title>Statistics Collection Configuration</Title>
<title>Statistics Collection Configuration</title>
<para>
Since collection of statistics adds some overhead to query execution,
@ -177,7 +177,7 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
</sect2>
<sect2 id="monitoring-stats-views">
<title>Viewing Collected Statistics</Title>
<title>Viewing Collected Statistics</title>
<para>
Several predefined views, listed in <xref

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

@ -432,7 +432,7 @@ ERROR: could not serialize access due to concurrent update
</para>
<sect3 id="mvcc-serializability">
<title>Serializable Isolation versus True Serializability</title>
<title>Serializable Isolation Versus True Serializability</title>
<indexterm>
<primary>serializability</primary>
@ -578,7 +578,7 @@ SELECT SUM(value) FROM mytab WHERE class = 2;
</para>
<variablelist>
<title>Table-level lock modes</title>
<title>Table-level Lock Modes</title>
<varlistentry>
<term>
<literal>ACCESS SHARE</literal>
@ -776,7 +776,7 @@ SELECT SUM(value) FROM mytab WHERE class = 2;
<table tocentry="1" id="table-lock-compatibility">
<title> Conflicting lock modes</title>
<title> Conflicting Lock Modes</title>
<tgroup cols="9">
<colspec colnum="2" colname="lockst">
<colspec colnum="9" colname="lockend">

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

@ -138,7 +138,7 @@ msgstr "another translated"
</sect2>
<sect2>
<title>Creating and maintaining message catalogs</title>
<title>Creating and Maintaining Message Catalogs</title>
<para>
OK, so how does one create a <quote>blank</quote> message
@ -206,7 +206,7 @@ gmake update-po
</sect2>
<sect2>
<title>Editing the PO files</title>
<title>Editing the PO Files</title>
<para>
The PO files can be edited with a regular text editor. The
@ -313,7 +313,7 @@ msgstr "Die Datei %2$s hat %1$u Zeichen."
</para>
<procedure>
<title>Adding NLS support to a program</title>
<title>Adding NLS Support to a Program</title>
<step>
<para>
@ -440,7 +440,7 @@ fprintf(stderr, gettext("panic level %d\n"), lvl);
</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

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

@ -937,7 +937,7 @@ SELECT * FROM x, y, a, b, c WHERE something AND somethingelse;
</sect2>
<sect2 id="populate-pitr">
<title>Disable WAL archival and streaming replication</title>
<title>Disable WAL Archival and Streaming Replication</title>
<para>
When loading large amounts of data into an installation that uses

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

@ -131,7 +131,7 @@ archive_cleanup_command = 'pg_archivecleanup -d /mnt/standby/archive %r 2>>clean
</sect2>
<sect2>
<title>Supported server versions</title>
<title>Supported Server Versions</title>
<para>
<application>pg_archivecleanup</application> is designed to work with

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

@ -409,7 +409,7 @@ pgbench <optional> <replaceable>options</> </optional> <replaceable>dbname</>
</sect2>
<sect2>
<title>What is the <quote>transaction</> actually performed in pgbench?</title>
<title>What is the <quote>Transaction</> Actually Performed in pgbench?</title>
<para>
The default transaction script issues seven commands per transaction:
@ -622,7 +622,7 @@ END;
</sect2>
<sect2>
<title>Per-transaction logging</title>
<title>Per-Transaction Logging</title>
<para>
With the <literal>-l</> option, <application>pgbench</> writes the time
@ -667,7 +667,7 @@ END;
</sect2>
<sect2>
<title>Per-statement latencies</title>
<title>Per-Statement Latencies</title>
<para>
With the <literal>-r</> option, <application>pgbench</> collects

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

@ -25,7 +25,7 @@
</para>
<sect2>
<title>The <structname>pg_buffercache</structname> view</title>
<title>The <structname>pg_buffercache</structname> View</title>
<para>
The definitions of the columns exposed by the view are shown in <xref linkend="pgbuffercache-columns">.
@ -132,7 +132,7 @@
</sect2>
<sect2>
<title>Sample output</title>
<title>Sample Output</title>
<screen>
regression=# SELECT c.relname, count(*) AS buffers

36
doc/src/sgml/pgcrypto.sgml
View File

@ -18,7 +18,7 @@
</para>
<sect2>
<title>General hashing functions</title>
<title>General Hashing Functions</title>
<sect3>
<title><function>digest()</function></title>
@ -77,7 +77,7 @@ hmac(data bytea, key text, type text) returns bytea
</sect2>
<sect2>
<title>Password hashing functions</title>
<title>Password Hashing Functions</title>
<para>
The functions <function>crypt()</> and <function>gen_salt()</>
@ -126,14 +126,14 @@ hmac(data bytea, key text, type text) returns bytea
</para>
<table id="pgcrypto-crypt-algorithms">
<title>Supported algorithms for <function>crypt()</></title>
<title>Supported Algorithms for <function>crypt()</></title>
<tgroup cols="5">
<thead>
<row>
<entry>Algorithm</entry>
<entry>Max password length</entry>
<entry>Max Password Length</entry>
<entry>Adaptive?</entry>
<entry>Salt bits</entry>
<entry>Salt Bits</entry>
<entry>Description</entry>
</row>
</thead>
@ -230,7 +230,7 @@ gen_salt(type text [, iter_count integer ]) returns text
</para>
<table id="pgcrypto-icfc-table">
<title>Iteration counts for <function>crypt()</></title>
<title>Iteration Counts for <function>crypt()</></title>
<tgroup cols="4">
<thead>
<row>
@ -283,7 +283,7 @@ gen_salt(type text [, iter_count integer ]) returns text
</para>
<table id="pgcrypto-hash-speed-table">
<title>Hash algorithm speeds</title>
<title>Hash Algorithm Speeds</title>
<tgroup cols="4">
<thead>
<row>
@ -398,7 +398,7 @@ gen_salt(type text [, iter_count integer ]) returns text
</sect2>
<sect2>
<title>PGP encryption functions</title>
<title>PGP Encryption Functions</title>
<para>
The functions here implement the encryption part of the OpenPGP (RFC 4880)
@ -627,7 +627,7 @@ dearmor(data text) returns bytea
</sect3>
<sect3>
<title>Options for PGP functions</title>
<title>Options for PGP Functions</title>
<para>
Options are named to be similar to GnuPG. An option's value should be
@ -802,7 +802,7 @@ Applies to: pgp_sym_encrypt, pgp_pub_encrypt
</sect3>
<sect3>
<title>Generating PGP keys with GnuPG</title>
<title>Generating PGP Keys with GnuPG</title>
<para>
To generate a new key:
@ -850,7 +850,7 @@ gpg -a --export-secret-keys KEYID > secret.key
</sect3>
<sect3>
<title>Limitations of PGP code</title>
<title>Limitations of PGP Code</title>
<itemizedlist>
<listitem>
@ -878,7 +878,7 @@ gpg -a --export-secret-keys KEYID > secret.key
</sect2>
<sect2>
<title>Raw encryption functions</title>
<title>Raw Encryption Functions</title>
<para>
These functions only run a cipher over data; they don't have any advanced
@ -980,7 +980,7 @@ encrypt(data, 'fooz', 'bf-cbc/pad:pkcs')
</sect2>
<sect2>
<title>Random-data functions</title>
<title>Random-Data Functions</title>
<synopsis>
gen_random_bytes(count integer) returns bytea
@ -1017,7 +1017,7 @@ gen_random_bytes(count integer) returns bytea
</para>
<table id="pgcrypto-with-without-openssl">
<title>Summary of functionality with and without OpenSSL</title>
<title>Summary of Functionality with and without OpenSSL</title>
<tgroup cols="3">
<thead>
<row>
@ -1109,7 +1109,7 @@ gen_random_bytes(count integer) returns bytea
</sect3>
<sect3>
<title>NULL handling</title>
<title>NULL Handling</title>
<para>
As is standard in SQL, all functions return NULL, if any of the arguments
@ -1118,7 +1118,7 @@ gen_random_bytes(count integer) returns bytea
</sect3>
<sect3>
<title>Security limitations</title>
<title>Security Limitations</title>
<para>
All <filename>pgcrypto</> functions run inside the database server.
@ -1142,7 +1142,7 @@ gen_random_bytes(count integer) returns bytea
</sect3>
<sect3>
<title>Useful reading</title>
<title>Useful Reading</title>
<itemizedlist>
<listitem>
@ -1173,7 +1173,7 @@ gen_random_bytes(count integer) returns bytea
</sect3>
<sect3>
<title>Technical references</title>
<title>Technical References</title>
<itemizedlist>
<listitem>

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

@ -72,7 +72,7 @@
</sect2>
<sect2>
<title>Sample output</title>
<title>Sample Output</title>
<screen>
postgres=# SELECT * FROM pg_freespace('foo');

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

@ -26,7 +26,7 @@ pgrowlocks(text) returns setof record
</para>
<table id="pgrowlocks-columns">
<title><function>pgrowlocks</> output columns</title>
<title><function>pgrowlocks</> Output Columns</title>
<tgroup cols="3">
<thead>
@ -112,7 +112,7 @@ SELECT * FROM accounts AS a, pgrowlocks('accounts') AS p
</sect2>
<sect2>
<title>Sample output</title>
<title>Sample Output</title>
<screen>
test=# SELECT * FROM pgrowlocks('t1');

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

@ -342,7 +342,7 @@ recovery_end_command = 'del C:\pgsql.trigger.5442'
</sect2>
<sect2>
<title>Supported server versions</title>
<title>Supported Server Versions</title>
<para>
<application>pg_standby</application> is designed to work with

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

@ -20,7 +20,7 @@
</para>
<sect2>
<title>The <structname>pg_stat_statements</structname> view</title>
<title>The <structname>pg_stat_statements</structname> View</title>
<para>
The statistics gathered by the module are made available via a system view
@ -31,7 +31,7 @@
</para>
<table id="pgstatstatements-columns">
<title><structname>pg_stat_statements</> columns</title>
<title><structname>pg_stat_statements</> Columns</title>
<tgroup cols="4">
<thead>
@ -190,7 +190,7 @@
</sect2>
<sect2>
<title>Configuration parameters</title>
<title>Configuration Parameters</title>
<variablelist>
<varlistentry>
@ -292,7 +292,7 @@ pg_stat_statements.track = all
</sect2>
<sect2>
<title>Sample output</title>
<title>Sample Output</title>
<screen>
bench=# SELECT pg_stat_statements_reset();

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

@ -45,7 +45,7 @@ free_percent | 1.95
</para>
<table id="pgstattuple-columns">
<title><function>pgstattuple</function> output columns</title>
<title><function>pgstattuple</function> Output Columns</title>
<tgroup cols="3">
<thead>
<row>

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

@ -44,7 +44,7 @@
<title>Functions and Operators</title>
<table id="pgtrgm-func-table">
<title><filename>pg_trgm</filename> functions</title>
<title><filename>pg_trgm</filename> Functions</title>
<tgroup cols="3">
<thead>
<row>
@ -97,7 +97,7 @@
</table>
<table id="pgtrgm-op-table">
<title><filename>pg_trgm</filename> operators</title>
<title><filename>pg_trgm</filename> Operators</title>
<tgroup cols="3">
<thead>
<row>

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

@ -602,7 +602,7 @@ SELECT release_hosts_query();
</sect2>
<sect2 id="plperl-utility-functions">
<title>Utility functions in PL/Perl</title>
<title>Utility Functions in PL/Perl</title>
<variablelist>
<varlistentry>

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

@ -1135,7 +1135,7 @@ EXECUTE 'SELECT count(*) FROM '
</note>
<example id="plpgsql-quote-literal-example">
<title>Quoting values in dynamic queries</title>
<title>Quoting Values In Dynamic Queries</title>
<indexterm>
<primary>quote_ident</primary>
@ -2094,7 +2094,7 @@ END LOOP;
</sect3>
<sect3 id="plpgsql-integer-for">
<title><literal>FOR</> (integer variant)</title>
<title><literal>FOR</> (Integer Variant)</title>
<synopsis>
<optional> &lt;&lt;<replaceable>label</replaceable>&gt;&gt; </optional>

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

@ -711,7 +711,7 @@ CREATE TRIGGER trig_mytab_modcount BEFORE INSERT OR UPDATE ON mytab
</sect1>
<sect1 id="pltcl-unknown">
<title>Modules and the <function>unknown</> command</title>
<title>Modules and the <function>unknown</> Command</title>
<para>
PL/Tcl has support for autoloading Tcl code when used.
It recognizes a special table, <literal>pltcl_modules</>, which

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

@ -97,7 +97,7 @@
</sect2>
<sect2>
<title>What to report</title>
<title>What to Report</title>
<para>
The most important thing to remember about bug reporting is to state all
@ -292,7 +292,7 @@
</sect2>
<sect2>
<title>Where to report bugs</title>
<title>Where to Report Bugs</title>
<para>
In general, send bug reports to the bug report mailing list at

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

@ -980,7 +980,7 @@ SELECT product_id, p.name, (sum(s.units) * (p.price - p.cost)) AS profit
</sect2>
<sect2 id="queries-window">
<title>Window Function Processing</>
<title>Window Function Processing</title>
<indexterm zone="queries-window">
<primary>window function</primary>

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

@ -31,7 +31,7 @@
<sect1 id="archive-recovery-settings">
<title>Archive recovery settings</title>
<title>Archive Recovery Settings</title>
<variablelist>
<varlistentry id="restore-command" xreflabel="restore_command">
@ -140,7 +140,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows
<sect1 id="recovery-target-settings">
<title>Recovery target settings</title>
<title>Recovery Target Settings</title>
<variablelist>
<varlistentry id="recovery-target-time" xreflabel="recovery_target_time">
@ -232,7 +232,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows
<sect1 id="standby-settings">
<title>Standby server settings</title>
<title>Standby Server Settings</title>
<variablelist>
<varlistentry id="standby-mode" xreflabel="standby_mode">

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

@ -1369,7 +1369,7 @@ CREATE TABLE employees OF employee_type (
</refsect2>
<refsect2>
<title>Zero-column tables</title>
<title>Zero-Column Tables</title>
<para>
<productname>PostgreSQL</productname> allows a table of no columns
@ -1382,7 +1382,7 @@ CREATE TABLE employees OF employee_type (
</refsect2>
<refsect2>
<title><literal>WITH</> clause</title>
<title><literal>WITH</> Clause</title>
<para>
The <literal>WITH</> clause is a <productname>PostgreSQL</productname>

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

@ -476,7 +476,7 @@ PostgreSQL documentation
</refsect2>
<refsect2>
<title>Options for single-user mode</title>
<title>Options for Single-User Mode</title>
<para>
The following options only apply to the single-user mode.

6
doc/src/sgml/ref/psql-ref.sgml
View File

@ -538,7 +538,7 @@ PostgreSQL documentation
<title>Usage</title>
<refsect2 id="R2-APP-PSQL-connecting">
<title>Connecting To A Database</title>
<title>Connecting to a Database</title>
<para>
<application>psql</application> is a regular
@ -2394,7 +2394,7 @@ lo_import 152801
</refsect2>
<refsect2>
<title>Advanced features</title>
<title>Advanced Features</title>
<refsect3 id="APP-PSQL-variables">
<title id="APP-PSQL-variables-title">Variables</title>
@ -3275,7 +3275,7 @@ $endif
<refsect1>
<title>Notes for Windows users</title>
<title>Notes for Windows Users</title>
<para>
<application>psql</application> is built as a <quote>console

20
doc/src/sgml/regress.sgml
View File

@ -33,7 +33,7 @@
</para>
<sect2>
<title>Running the tests against a temporary installation</title>
<title>Running the Tests Against a Temporary Installation</title>
<para>
To run the parallel regression tests after building but before installation,
@ -110,7 +110,7 @@ gmake MAX_CONNECTIONS=10 check
</sect2>
<sect2>
<title>Running the tests against an existing installation</title>
<title>Running the Tests Against an Existing Installation</title>
<para>
To run the tests after installation<![%standalone-ignore;[ (see <xref linkend="installation">)]]>,
@ -196,7 +196,7 @@ gmake standbycheck
</sect2>
<sect2>
<title>Locale and encoding</title>
<title>Locale and Encoding</title>
<para>
By default, the tests against a temporary installation use the
@ -277,7 +277,7 @@ gmake check LANG=C MULTIBYTE=EUC_JP
</para>
<sect2>
<title>Error message differences</title>
<title>Error Message Differences</title>
<para>
Some of the regression tests involve intentional invalid input
@ -292,7 +292,7 @@ gmake check LANG=C MULTIBYTE=EUC_JP
</sect2>
<sect2>
<title>Locale differences</title>
<title>Locale Differences</title>
<para>
If you run the tests against a server that was
@ -339,7 +339,7 @@ gmake check NO_LOCALE=1
</sect2>
<sect2>
<title>Date and time differences</title>
<title>Date and Time Differences</title>
<para>
Most of the date and time results are dependent on the time zone
@ -353,7 +353,7 @@ gmake check NO_LOCALE=1
</sect2>
<sect2>
<title>Floating-point differences</title>
<title>Floating-Point Differences</title>
<para>
Some of the tests involve computing 64-bit floating-point numbers (<type>double
@ -381,7 +381,7 @@ gmake check NO_LOCALE=1
</sect2>
<sect2>
<title>Row ordering differences</title>
<title>Row Ordering Differences</title>
<para>
You might see differences in which the same rows are output in a
@ -417,7 +417,7 @@ exclusion of those that don't.
</sect2>
<sect2>
<title>Insufficient stack depth</title>
<title>Insufficient Stack Depth</title>
<para>
If the <literal>errors</literal> test results in a server crash
@ -434,7 +434,7 @@ exclusion of those that don't.
</sect2>
<sect2>
<title>The <quote>random</quote> test</title>
<title>The <quote>random</quote> Test</title>
<para>
The <literal>random</literal> test script is intended to produce

62
doc/src/sgml/release-7.4.sgml
View File

@ -5,7 +5,7 @@
<title>Release 7.4.30</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2010-10-04</simpara>
</note>
@ -139,7 +139,7 @@
<title>Release 7.4.29</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2010-05-17</simpara>
</note>
@ -283,7 +283,7 @@
<title>Release 7.4.28</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2010-03-15</simpara>
</note>
@ -402,7 +402,7 @@
<title>Release 7.4.27</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2009-12-14</simpara>
</note>
@ -522,7 +522,7 @@
<title>Release 7.4.26</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2009-09-09</simpara>
</note>
@ -652,7 +652,7 @@
<title>Release 7.4.25</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2009-03-16</simpara>
</note>
@ -732,7 +732,7 @@
<title>Release 7.4.24</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2009-02-02</simpara>
</note>
@ -818,7 +818,7 @@
<title>Release 7.4.23</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2008-11-03</simpara>
</note>
@ -902,7 +902,7 @@
<title>Release 7.4.22</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2008-09-22</simpara>
</note>
@ -978,7 +978,7 @@
<title>Release 7.4.21</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2008-06-12</simpara>
</note>
@ -1032,7 +1032,7 @@
<title>Release 7.4.20</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>never released</simpara>
</note>
@ -1177,7 +1177,7 @@
<title>Release 7.4.19</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2008-01-07</simpara>
</note>
@ -1331,7 +1331,7 @@
<title>Release 7.4.18</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2007-09-17</simpara>
</note>
@ -1407,7 +1407,7 @@
<title>Release 7.4.17</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2007-04-23</simpara>
</note>
@ -1478,7 +1478,7 @@
<title>Release 7.4.16</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2007-02-05</simpara>
</note>
@ -1549,7 +1549,7 @@
<title>Release 7.4.15</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2007-01-08</simpara>
</note>
@ -1638,7 +1638,7 @@
<title>Release 7.4.14</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2006-10-16</simpara>
</note>
@ -1685,7 +1685,7 @@ ANYARRAY</para></listitem>
<title>Release 7.4.13</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2006-05-23</simpara>
</note>
@ -1792,7 +1792,7 @@ Fuhr)</para></listitem>
<title>Release 7.4.12</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2006-02-14</simpara>
</note>
@ -1855,7 +1855,7 @@ and <function>isinf</> during configure (Tom)</para></listitem>
<title>Release 7.4.11</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2006-01-09</simpara>
</note>
@ -1922,7 +1922,7 @@ what's actually returned by the query (Joe)</para></listitem>
<title>Release 7.4.10</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2005-12-12</simpara>
</note>
@ -1975,7 +1975,7 @@ table has been dropped</para></listitem>
<title>Release 7.4.9</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2005-10-04</simpara>
</note>
@ -2044,7 +2044,7 @@ code</para></listitem>
<title>Release 7.4.8</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2005-05-09</simpara>
</note>
@ -2228,7 +2228,7 @@ holder of the lock released it within a very narrow window.
<title>Release 7.4.7</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2005-01-31</simpara>
</note>
@ -2288,7 +2288,7 @@ GMT</para></listitem>
<title>Release 7.4.6</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2004-10-22</simpara>
</note>
@ -2360,7 +2360,7 @@ ECPG prepare statement</para></listitem>
<title>Release 7.4.5</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2004-08-18</simpara>
</note>
@ -2398,7 +2398,7 @@ still worth a re-release. The bug does not exist in pre-7.4 releases.
<title>Release 7.4.4</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2004-08-16</simpara>
</note>
@ -2450,7 +2450,7 @@ aggregate plan</para></listitem>
<title>Release 7.4.3</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2004-06-14</simpara>
</note>
@ -2508,7 +2508,7 @@ names from outer query levels.
<title>Release 7.4.2</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2004-03-08</simpara>
</note>
@ -2651,7 +2651,7 @@ inconveniences associated with the <literal>i/I</> problem.</para></listitem>
<title>Release 7.4.1</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2003-12-22</simpara>
</note>
@ -2765,7 +2765,7 @@ DROP SCHEMA information_schema CASCADE;
<title>Release 7.4</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2003-11-17</simpara>
</note>

54
doc/src/sgml/release-8.0.sgml
View File

@ -5,7 +5,7 @@
<title>Release 8.0.26</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2010-10-04</simpara>
</note>
@ -209,7 +209,7 @@
<title>Release 8.0.25</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2010-05-17</simpara>
</note>
@ -369,7 +369,7 @@
<title>Release 8.0.24</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2010-03-15</simpara>
</note>
@ -546,7 +546,7 @@
<title>Release 8.0.23</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2009-12-14</simpara>
</note>
@ -701,7 +701,7 @@
<title>Release 8.0.22</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2009-09-09</simpara>
</note>
@ -865,7 +865,7 @@
<title>Release 8.0.21</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2009-03-16</simpara>
</note>
@ -945,7 +945,7 @@
<title>Release 8.0.20</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2009-02-02</simpara>
</note>
@ -1031,7 +1031,7 @@
<title>Release 8.0.19</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2008-11-03</simpara>
</note>
@ -1142,7 +1142,7 @@
<title>Release 8.0.18</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2008-09-22</simpara>
</note>
@ -1276,7 +1276,7 @@
<title>Release 8.0.17</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2008-06-12</simpara>
</note>
@ -1330,7 +1330,7 @@
<title>Release 8.0.16</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>never released</simpara>
</note>
@ -1567,7 +1567,7 @@
<title>Release 8.0.15</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2008-01-07</simpara>
</note>
@ -1783,7 +1783,7 @@
<title>Release 8.0.14</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2007-09-17</simpara>
</note>
@ -1891,7 +1891,7 @@
<title>Release 8.0.13</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2007-04-23</simpara>
</note>
@ -1968,7 +1968,7 @@
<title>Release 8.0.12</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2007-02-07</simpara>
</note>
@ -2010,7 +2010,7 @@
<title>Release 8.0.11</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2007-02-05</simpara>
</note>
@ -2081,7 +2081,7 @@
<title>Release 8.0.10</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2007-01-08</simpara>
</note>
@ -2200,7 +2200,7 @@
<title>Release 8.0.9</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2006-10-16</simpara>
</note>
@ -2256,7 +2256,7 @@ Wieland)</para></listitem>
<title>Release 8.0.8</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2006-05-23</simpara>
</note>
@ -2370,7 +2370,7 @@ Fuhr)</para></listitem>
<title>Release 8.0.7</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2006-02-14</simpara>
</note>
@ -2469,7 +2469,7 @@ and <function>isinf</> during configure (Tom)</para></listitem>
<title>Release 8.0.6</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2006-01-09</simpara>
</note>
@ -2554,7 +2554,7 @@ what's actually returned by the query (Joe)</para></listitem>
<title>Release 8.0.5</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2005-12-12</simpara>
</note>
@ -2636,7 +2636,7 @@ to subquery results</para></listitem>
<title>Release 8.0.4</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2005-10-04</simpara>
</note>
@ -2733,7 +2733,7 @@ code</para></listitem>
<title>Release 8.0.3</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2005-05-09</simpara>
</note>
@ -2853,7 +2853,7 @@ data types</para></listitem>
<title>Release 8.0.2</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2005-04-07</simpara>
</note>
@ -3010,7 +3010,7 @@ addresses in <type>INET</> data types (Tom)</para></listitem>
<title>Release 8.0.1</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2005-01-31</simpara>
</note>
@ -3079,7 +3079,7 @@ typedefs (Michael)</para></listitem>
<title>Release 8.0</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2005-01-19</simpara>
</note>

48
doc/src/sgml/release-8.1.sgml
View File

@ -5,7 +5,7 @@
<title>Release 8.1.23</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2010-12-16</simpara>
</note>
@ -224,7 +224,7 @@
<title>Release 8.1.22</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2010-10-04</simpara>
</note>
@ -442,7 +442,7 @@
<title>Release 8.1.21</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2010-05-17</simpara>
</note>
@ -596,7 +596,7 @@
<title>Release 8.1.20</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2010-03-15</simpara>
</note>
@ -786,7 +786,7 @@
<title>Release 8.1.19</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2009-12-14</simpara>
</note>
@ -967,7 +967,7 @@
<title>Release 8.1.18</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2009-09-09</simpara>
</note>
@ -1131,7 +1131,7 @@
<title>Release 8.1.17</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2009-03-16</simpara>
</note>
@ -1254,7 +1254,7 @@
<title>Release 8.1.16</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2009-02-02</simpara>
</note>
@ -1374,7 +1374,7 @@
<title>Release 8.1.15</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2008-11-03</simpara>
</note>
@ -1526,7 +1526,7 @@
<title>Release 8.1.14</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2008-09-22</simpara>
</note>
@ -1702,7 +1702,7 @@
<title>Release 8.1.13</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2008-06-12</simpara>
</note>
@ -1769,7 +1769,7 @@
<title>Release 8.1.12</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>never released</simpara>
</note>
@ -2019,7 +2019,7 @@
<title>Release 8.1.11</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2008-01-07</simpara>
</note>
@ -2271,7 +2271,7 @@
<title>Release 8.1.10</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2007-09-17</simpara>
</note>
@ -2392,7 +2392,7 @@
<title>Release 8.1.9</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2007-04-23</simpara>
</note>
@ -2483,7 +2483,7 @@
<title>Release 8.1.8</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2007-02-07</simpara>
</note>
@ -2525,7 +2525,7 @@
<title>Release 8.1.7</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2007-02-05</simpara>
</note>
@ -2627,7 +2627,7 @@
<title>Release 8.1.6</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2007-01-08</simpara>
</note>
@ -2777,7 +2777,7 @@
<title>Release 8.1.5</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2006-10-16</simpara>
</note>
@ -2854,7 +2854,7 @@ compilers (Hiroshi Saito)</para></listitem>
<title>Release 8.1.4</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2006-05-23</simpara>
</note>
@ -3008,7 +3008,7 @@ documented (Tom)</para></listitem>
<title>Release 8.1.3</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2006-02-14</simpara>
</note>
@ -3130,7 +3130,7 @@ creation (Tom)</para></listitem>
<title>Release 8.1.2</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2006-01-09</simpara>
</note>
@ -3233,7 +3233,7 @@ what's actually returned by the query (Joe)</para></listitem>
<title>Release 8.1.1</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2005-12-12</simpara>
</note>
@ -3325,7 +3325,7 @@ DISTINCT query</para></listitem>
<title>Release 8.1</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2005-11-08</simpara>
</note>

42
doc/src/sgml/release-8.2.sgml
View File

@ -5,7 +5,7 @@
<title>Release 8.2.20</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2011-01-31</simpara>
</note>
@ -137,7 +137,7 @@
<title>Release 8.2.19</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2010-12-16</simpara>
</note>
@ -381,7 +381,7 @@
<title>Release 8.2.18</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2010-10-04</simpara>
</note>
@ -667,7 +667,7 @@
<title>Release 8.2.17</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2010-05-17</simpara>
</note>
@ -868,7 +868,7 @@
<title>Release 8.2.16</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2010-03-15</simpara>
</note>
@ -1139,7 +1139,7 @@
<title>Release 8.2.15</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2009-12-14</simpara>
</note>
@ -1383,7 +1383,7 @@
<title>Release 8.2.14</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2009-09-09</simpara>
</note>
@ -1613,7 +1613,7 @@
<title>Release 8.2.13</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2009-03-16</simpara>
</note>
@ -1779,7 +1779,7 @@
<title>Release 8.2.12</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2009-02-02</simpara>
</note>
@ -1958,7 +1958,7 @@
<title>Release 8.2.11</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2008-11-03</simpara>
</note>
@ -2142,7 +2142,7 @@
<title>Release 8.2.10</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2008-09-22</simpara>
</note>
@ -2374,7 +2374,7 @@
<title>Release 8.2.9</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2008-06-12</simpara>
</note>
@ -2441,7 +2441,7 @@
<title>Release 8.2.8</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>never released</simpara>
</note>
@ -2636,7 +2636,7 @@
<title>Release 8.2.7</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2008-03-17</simpara>
</note>
@ -2905,7 +2905,7 @@
<title>Release 8.2.6</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2008-01-07</simpara>
</note>
@ -3196,7 +3196,7 @@
<title>Release 8.2.5</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2007-09-17</simpara>
</note>
@ -3373,7 +3373,7 @@
<title>Release 8.2.4</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2007-04-23</simpara>
</note>
@ -3517,7 +3517,7 @@
<title>Release 8.2.3</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2007-02-07</simpara>
</note>
@ -3563,7 +3563,7 @@
<title>Release 8.2.2</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2007-02-05</simpara>
</note>
@ -3721,7 +3721,7 @@
<title>Release 8.2.1</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2007-01-08</simpara>
</note>
@ -3856,7 +3856,7 @@
<title>Release 8.2</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2006-12-05</simpara>
</note>

30
doc/src/sgml/release-8.3.sgml
View File

@ -5,7 +5,7 @@
<title>Release 8.3.14</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2011-01-31</simpara>
</note>
@ -137,7 +137,7 @@
<title>Release 8.3.13</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2010-12-16</simpara>
</note>
@ -415,7 +415,7 @@
<title>Release 8.3.12</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2010-10-04</simpara>
</note>
@ -778,7 +778,7 @@
<title>Release 8.3.11</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2010-05-17</simpara>
</note>
@ -1007,7 +1007,7 @@
<title>Release 8.3.10</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2010-03-15</simpara>
</note>
@ -1334,7 +1334,7 @@
<title>Release 8.3.9</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2009-12-14</simpara>
</note>
@ -1667,7 +1667,7 @@
<title>Release 8.3.8</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2009-09-09</simpara>
</note>
@ -1957,7 +1957,7 @@
<title>Release 8.3.7</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2009-03-16</simpara>
</note>
@ -2180,7 +2180,7 @@
<title>Release 8.3.6</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2009-02-02</simpara>
</note>
@ -2474,7 +2474,7 @@
<title>Release 8.3.5</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2008-11-03</simpara>
</note>
@ -2729,7 +2729,7 @@
<title>Release 8.3.4</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2008-09-22</simpara>
</note>
@ -3083,7 +3083,7 @@
<title>Release 8.3.3</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2008-06-12</simpara>
</note>
@ -3150,7 +3150,7 @@
<title>Release 8.3.2</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>never released</simpara>
</note>
@ -3515,7 +3515,7 @@
<title>Release 8.3.1</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2008-03-17</simpara>
</note>
@ -3828,7 +3828,7 @@
<title>Release 8.3</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2008-02-04</simpara>
</note>

16
doc/src/sgml/release-8.4.sgml
View File

@ -5,7 +5,7 @@
<title>Release 8.4.7</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2011-01-31</simpara>
</note>
@ -137,7 +137,7 @@
<title>Release 8.4.6</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2010-12-16</simpara>
</note>
@ -448,7 +448,7 @@
<title>Release 8.4.5</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2010-10-04</simpara>
</note>
@ -970,7 +970,7 @@
<title>Release 8.4.4</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2010-05-17</simpara>
</note>
@ -1261,7 +1261,7 @@
<title>Release 8.4.3</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2010-03-15</simpara>
</note>
@ -1728,7 +1728,7 @@
<title>Release 8.4.2</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2009-12-14</simpara>
</note>
@ -2259,7 +2259,7 @@ WITH w AS (SELECT * FROM foo) SELECT * FROM w, bar ... FOR UPDATE
<title>Release 8.4.1</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2009-09-09</simpara>
</note>
@ -2558,7 +2558,7 @@ WITH w AS (SELECT * FROM foo) SELECT * FROM w, bar ... FOR UPDATE
<title>Release 8.4</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2009-07-01</simpara>
</note>

8
doc/src/sgml/release-9.0.sgml
View File

@ -5,7 +5,7 @@
<title>Release 9.0.3</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2011-01-31</simpara>
</note>
@ -181,7 +181,7 @@
<title>Release 9.0.2</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2010-12-16</simpara>
</note>
@ -628,7 +628,7 @@
<title>Release 9.0.1</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2010-10-04</simpara>
</note>
@ -770,7 +770,7 @@
<title>Release 9.0</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2010-09-20</simpara>
</note>

122
doc/src/sgml/release-old.sgml
View File

@ -5,7 +5,7 @@
<title>Release 7.3.21</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2008-01-07</simpara>
</note>
@ -117,7 +117,7 @@
<title>Release 7.3.20</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2007-09-17</simpara>
</note>
@ -178,7 +178,7 @@
<title>Release 7.3.19</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2007-04-23</simpara>
</note>
@ -234,7 +234,7 @@
<title>Release 7.3.18</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2007-02-05</simpara>
</note>
@ -296,7 +296,7 @@
<title>Release 7.3.17</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2007-01-08</simpara>
</note>
@ -352,7 +352,7 @@
<title>Release 7.3.16</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2006-10-16</simpara>
</note>
@ -394,7 +394,7 @@
<title>Release 7.3.15</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2006-05-23</simpara>
</note>
@ -486,7 +486,7 @@ Fuhr)</para></listitem>
<title>Release 7.3.14</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2006-02-14</simpara>
</note>
@ -543,7 +543,7 @@ and <function>isinf</> during configure (Tom)</para></listitem>
<title>Release 7.3.13</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2006-01-09</simpara>
</note>
@ -605,7 +605,7 @@ what's actually returned by the query (Joe)</para></listitem>
<title>Release 7.3.12</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2005-12-12</simpara>
</note>
@ -652,7 +652,7 @@ table has been dropped</para></listitem>
<title>Release 7.3.11</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2005-10-04</simpara>
</note>
@ -703,7 +703,7 @@ the variable is of pass-by-reference type</para></listitem>
<title>Release 7.3.10</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2005-05-09</simpara>
</note>
@ -829,7 +829,7 @@ month-related formats</para></listitem>
<title>Release 7.3.9</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2005-01-31</simpara>
</note>
@ -885,7 +885,7 @@ datestyles</para></listitem>
<title>Release 7.3.8</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2004-10-22</simpara>
</note>
@ -935,7 +935,7 @@ concern since there is no reason for non-developers to use this script anyway.
<title>Release 7.3.7</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2004-08-16</simpara>
</note>
@ -975,7 +975,7 @@ since <productname>PostgreSQL</productname> 7.1.
<title>Release 7.3.6</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2004-03-02</simpara>
</note>
@ -1040,7 +1040,7 @@ operations on bytea columns (Joe)</para></listitem>
<title>Release 7.3.5</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2003-12-03</simpara>
</note>
@ -1091,7 +1091,7 @@ operations on bytea columns (Joe)</para></listitem>
<title>Release 7.3.4</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2003-07-24</simpara>
</note>
@ -1131,7 +1131,7 @@ operations on bytea columns (Joe)</para></listitem>
<title>Release 7.3.3</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2003-05-22</simpara>
</note>
@ -1241,7 +1241,7 @@ operations on bytea columns (Joe)</para></listitem>
<title>Release 7.3.2</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2003-02-04</simpara>
</note>
@ -1302,7 +1302,7 @@ operations on bytea columns (Joe)</para></listitem>
<title>Release 7.3.1</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2002-12-18</simpara>
</note>
@ -1352,7 +1352,7 @@ operations on bytea columns (Joe)</para></listitem>
<title>Release 7.3</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2002-11-27</simpara>
</note>
@ -1988,7 +1988,7 @@ operations on bytea columns (Joe)</para></listitem>
<title>Release 7.2.8</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2005-05-09</simpara>
</note>
@ -2039,7 +2039,7 @@ month-related formats</para></listitem>
<title>Release 7.2.7</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2005-01-31</simpara>
</note>
@ -2087,7 +2087,7 @@ datestyles</para></listitem>
<title>Release 7.2.6</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2004-10-22</simpara>
</note>
@ -2138,7 +2138,7 @@ concern since there is no reason for non-developers to use this script anyway.
<title>Release 7.2.5</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2004-08-16</simpara>
</note>
@ -2181,7 +2181,7 @@ since <productname>PostgreSQL</productname> 7.1.
<title>Release 7.2.4</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2003-01-30</simpara>
</note>
@ -2220,7 +2220,7 @@ since <productname>PostgreSQL</productname> 7.1.
<title>Release 7.2.3</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2002-10-01</simpara>
</note>
@ -2257,7 +2257,7 @@ since <productname>PostgreSQL</productname> 7.1.
<title>Release 7.2.2</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2002-08-23</simpara>
</note>
@ -2300,7 +2300,7 @@ since <productname>PostgreSQL</productname> 7.1.
<title>Release 7.2.1</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2002-03-21</simpara>
</note>
@ -2346,7 +2346,7 @@ since <productname>PostgreSQL</productname> 7.1.
<title>Release 7.2</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2002-02-04</simpara>
</note>
@ -2902,7 +2902,7 @@ since <productname>PostgreSQL</productname> 7.1.
<title>Release 7.1.3</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2001-08-15</simpara>
</note>
@ -2940,7 +2940,7 @@ Cygwin build (Jason Tishler)
<title>Release 7.1.2</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2001-05-11</simpara>
</note>
@ -2978,7 +2978,7 @@ pg_dump cleanups
<title>Release 7.1.1</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2001-05-05</simpara>
</note>
@ -3025,7 +3025,7 @@ Python fixes (Darcy)
<title>Release 7.1</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2001-04-13</simpara>
</note>
@ -3323,7 +3323,7 @@ New FreeBSD tools ipc_check, start-scripts/freebsd
<title>Release 7.0.3</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2000-11-11</simpara>
</note>
@ -3395,7 +3395,7 @@ Fix for crash of backend, on abort (Tom)
<title>Release 7.0.2</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2000-06-05</simpara>
</note>
@ -3429,7 +3429,7 @@ Added documentation to tarball.
<title>Release 7.0.1</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2000-06-01</simpara>
</note>
@ -3484,7 +3484,7 @@ ecpg changes (Michael)
<title>Release 7.0</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>2000-05-08</simpara>
</note>
@ -3953,7 +3953,7 @@ New multibyte encodings
<title>Release 6.5.3</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>1999-10-13</simpara>
</note>
@ -3989,7 +3989,7 @@ Fix dumping rules on inherited tables
<title>Release 6.5.2</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>1999-09-15</simpara>
</note>
@ -4046,7 +4046,7 @@ Updated version of pgaccess 0.98
<title>Release 6.5.1</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>1999-07-15</simpara>
</note>
@ -4101,7 +4101,7 @@ Add Win1250 (Czech) support (Pavel Behal)
<title>Release 6.5</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>1999-06-09</simpara>
</note>
@ -4501,7 +4501,7 @@ New install commands for plpgsql(Jan)
<title>Release 6.4.2</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>1998-12-20</simpara>
</note>
@ -4536,7 +4536,7 @@ Fix for datetime constant problem on some platforms(Thomas)
<title>Release 6.4.1</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>1998-12-18</simpara>
</note>
@ -4600,7 +4600,7 @@ Upgrade to PyGreSQL 2.2(D'Arcy)
<title>Release 6.4</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>1998-10-30</simpara>
</note>
@ -4897,7 +4897,7 @@ new Makefile.shlib for shared library configuration(Tom)
<title>Release 6.3.2</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>1998-04-07</simpara>
</note>
@ -4967,7 +4967,7 @@ ASSERT fixes(Bruce)
<title>Release 6.3.1</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>1998-03-23</simpara>
</note>
@ -5053,7 +5053,7 @@ Better identify tcl and tk libs and includes(Bruce)
<title>Release 6.3</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>1998-03-01</simpara>
</note>
@ -5365,7 +5365,7 @@ Remove un-needed malloc() calls and replace with palloc()(Bruce)
<title>Release 6.2.1</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>1997-10-17</simpara>
</note>
@ -5447,7 +5447,7 @@ Trigger function for inserting user names for INSERT/UPDATE(Brook Milligan)
<title>Release 6.2</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>1997-10-02</simpara>
</note>
@ -5600,7 +5600,7 @@ SPI and Trigger programming guides (Vadim &amp; D'Arcy)
<title>Release 6.1.1</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>1997-07-22</simpara>
</note>
@ -5645,7 +5645,7 @@ pg_dumpall now returns proper status, portability fix(Bruce)
<title>Release 6.1</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>1997-06-08</simpara>
</note>
@ -5817,7 +5817,7 @@ DG/UX, Ultrix, IRIX, AIX portability fixes
<title>Release 6.0</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>1997-01-29</simpara>
</note>
@ -5961,7 +5961,7 @@ Unused/uninitialized variables corrected
<title>Release 1.09</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>1996-11-04</simpara>
</note>
@ -5976,7 +5976,7 @@ releases.
<title>Release 1.02</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>1996-08-01</simpara>
</note>
@ -6125,7 +6125,7 @@ Contributors (apologies to any missed)
<title>Release 1.01</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>1996-02-23</simpara>
</note>
@ -6317,7 +6317,7 @@ Bug fixes:
<title>Release 1.0</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>1995-09-05</simpara>
</note>
@ -6374,7 +6374,7 @@ Bug fixes:
<title><productname>Postgres95</productname> Release 0.03</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>1995-07-21</simpara>
</note>
@ -6496,7 +6496,7 @@ New documentation:
<title><productname>Postgres95</productname> Release 0.02</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>1995-05-25</simpara>
</note>
@ -6547,7 +6547,7 @@ The following bugs have been fixed in postgres95-beta-0.02:
<title><productname>Postgres95</productname> Release 0.01</title>
<note>
<title>Release date</title>
<title>Release Date</title>
<simpara>1995-05-01</simpara>
</note>

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

@ -1928,7 +1928,7 @@ SELECT * FROM phone_number WHERE tricky(person, phone);
</sect1>
<sect1 id="rules-triggers">
<title>Rules versus Triggers</title>
<title>Rules Versus Triggers</title>
<indexterm zone="rules-triggers">
<primary>rule</primary>

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

@ -552,7 +552,7 @@ psql: could not connect to server: No such file or directory
<table id="sysvipc-parameters">
<title><systemitem class="osname">System V</> <acronym>IPC</> parameters</>
<title><systemitem class="osname">System V</> <acronym>IPC</> Parameters</title>
<tgroup cols="3">
<thead>
@ -738,7 +738,7 @@ psql: could not connect to server: No such file or directory
<indexterm><primary>BSD/OS</><secondary>IPC configuration</></>
<listitem>
<formalpara>
<title>Shared Memory</>
<title>Shared Memory</title>
<para>
By default, only 4 MB of shared memory is supported. Keep in
mind that shared memory is not pageable; it is locked in RAM.
@ -759,7 +759,7 @@ options "SHMMAX=\(SHMALL*PAGE_SIZE\)"
</formalpara>
<formalpara>
<title>Semaphores</>
<title>Semaphores</title>
<para>
You will probably want to increase the number of semaphores
as well; the default system total of 60 will only allow about
@ -1092,7 +1092,7 @@ set semsys:seminfo_semmsl=32
<table id="shared-memory-parameters">
<title><productname>PostgreSQL</productname> shared memory usage</>
<title><productname>PostgreSQL</productname> Shared Memory Usage</>
<tgroup cols="2">
<thead>
@ -1701,7 +1701,7 @@ $ <userinput>kill -INT `head -1 /usr/local/pgsql/data/postmaster.pid`</userinput
</para>
<sect2 id="ssl-client-certificates">
<title>Using client certificates</title>
<title>Using Client Certificates</title>
<para>
To require the client to supply a trusted certificate, place

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

@ -99,7 +99,7 @@ test=> select '6.25 .. 6.50'::seg as "pH";
</para>
<table id="seg-repr-table">
<title><type>seg</> external representations</title>
<title><type>seg</> External Representations</title>
<tgroup cols="2">
<tbody>
<row>
@ -133,7 +133,7 @@ test=> select '6.25 .. 6.50'::seg as "pH";
</table>
<table id="seg-input-examples">
<title>Examples of valid <type>seg</> input</title>
<title>Examples of Valid <type>seg</> Input</title>
<tgroup cols="2">
<tbody>
<row>
@ -241,7 +241,7 @@ test=> select '6.25 .. 6.50'::seg as "pH";
</para>
<table id="seg-gist-operators">
<title>Seg GiST operators</title>
<title>Seg GiST Operators</title>
<tgroup cols="2">
<thead>
<row>

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

@ -293,7 +293,7 @@ $ restorecon -R /usr/local/pgsql/
<sect2 id="sepgsql-features">
<title>Features</title>
<sect3>
<title>controlled object classes</title>
<title>Controlled Object Classes</title>
<para>
The security model of <productname>SELinux</> describes all the access
control rules as a relationship between a subject entity (typically,

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

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

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

@ -326,7 +326,7 @@ ereport(level, (errmsg_internal("format string", ...)));
</para>
<simplesect>
<title>What goes where</title>
<title>What Goes Where</title>
<para>
The primary message should be short, factual, and avoid reference to
@ -388,7 +388,7 @@ Hint: the addendum
</simplesect>
<simplesect>
<title>Quotation marks</title>
<title>Quotation Marks</title>
<para>
English text should use double quotes when quoting is appropriate.
@ -409,7 +409,7 @@ Hint: the addendum
</simplesect>
<simplesect>
<title>Use of quotes</title>
<title>Use of Quotes</title>
<para>
Use quotes always to delimit file names, user-supplied identifiers, and
@ -433,7 +433,7 @@ Hint: the addendum
</simplesect>
<simplesect>
<title>Grammar and punctuation</title>
<title>Grammar and Punctuation</title>
<para>
The rules are different for primary error messages and for detail/hint
@ -472,7 +472,7 @@ Hint: the addendum
</simplesect>
<simplesect>
<title>Upper case vs. lower case</title>
<title>Upper Case vs. Lower Case</title>
<para>
Use lower case for message wording, including the first letter of a
@ -488,7 +488,7 @@ Hint: the addendum
</simplesect>
<simplesect>
<title>Avoid passive voice</title>
<title>Avoid Passive Voice</title>
<para>
Use the active voice. Use complete sentences when there is an acting
@ -504,7 +504,7 @@ Hint: the addendum
</simplesect>
<simplesect>
<title>Present vs past tense</title>
<title>Present vs. Past Tense</title>
<para>
Use past tense if an attempt to do something failed, but could perhaps
@ -544,7 +544,7 @@ cannot open file "%s"
</simplesect>
<simplesect>
<title>Type of the object</title>
<title>Type of the Object</title>
<para>
When citing the name of an object, state what kind of object it is.
@ -573,7 +573,7 @@ cannot open file "%s"
</simplesect>
<simplesect>
<title>Assembling error messages</title>
<title>Assembling Error Messages</title>
<para>
When a message includes text that is generated elsewhere, embed it in
@ -594,7 +594,7 @@ could not open file %s: %m
</simplesect>
<simplesect>
<title>Reasons for errors</title>
<title>Reasons for Errors</title>
<para>
Messages should always state the reason why an error occurred.
@ -609,7 +609,7 @@ BETTER: could not open file %s (I/O failure)
</simplesect>
<simplesect>
<title>Function names</title>
<title>Function Names</title>
<para>
Don't include the name of the reporting routine in the error text. We have
@ -641,7 +641,7 @@ BETTER: could not open file %s: %m
</simplesect>
<simplesect>
<title>Tricky words to avoid</title>
<title>Tricky Words to Avoid</title>
<formalpara>
<title>Unable</title>
@ -717,7 +717,7 @@ BETTER: unrecognized node type: 42
</simplesect>
<simplesect>
<title>Proper spelling</title>
<title>Proper Spelling</title>
<para>
Spell out words in full. For instance, avoid:

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

@ -2296,7 +2296,7 @@ LANGUAGE SQL IMMUTABLE STRICT;
</para>
<sect2 id="sql-syntax-calling-funcs-positional">
<title>Using positional notation</title>
<title>Using Positional Notation</title>
<indexterm>
<primary>function</primary>
@ -2331,7 +2331,7 @@ SELECT concat_lower_or_upper('Hello', 'World');
</sect2>
<sect2 id="sql-syntax-calling-funcs-named">
<title>Using named notation</title>
<title>Using Named Notation</title>
<indexterm>
<primary>function</primary>
@ -2370,7 +2370,7 @@ SELECT concat_lower_or_upper(a := 'Hello', uppercase := true, b := 'World');
</sect2>
<sect2 id="sql-syntax-calling-funcs-mixed">
<title>Using mixed notation</title>
<title>Using Mixed Notation</title>
<indexterm>
<primary>function</primary>

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

@ -23,7 +23,7 @@
</para>
<table id="tablefunc-functions">
<title><filename>tablefunc</> functions</title>
<title><filename>tablefunc</> Functions</title>
<tgroup cols="3">
<thead>
<row>
@ -620,7 +620,7 @@ connectby(text relname, text keyid_fld, text parent_keyid_fld
</para>
<table id="tablefunc-connectby-parameters">
<title><function>connectby</function> parameters</title>
<title><function>connectby</function> Parameters</title>
<tgroup cols="2">
<thead>
<row>

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

@ -13,7 +13,7 @@
</para>
<sect2>
<title>Deprecation notice</title>
<title>Deprecation Notice</title>
<para>
From <productname>PostgreSQL</> 8.3 on, there is XML-related
@ -31,7 +31,7 @@
</sect2>
<sect2>
<title>Description of functions</title>
<title>Description of Functions</title>
<para>
<xref linkend="xml2-functions-table"> shows the functions provided by this module.
@ -339,7 +339,7 @@ WHERE t.author_id = p.person_id;
</para>
<sect3>
<title>Multivalued results</title>
<title>Multivalued Results</title>
<para>
The <function>xpath_table</> function assumes that the results of each XPath query
@ -414,7 +414,7 @@ ORDER BY doc_num, line_num;
</sect2>
<sect2>
<title>XSLT functions</title>
<title>XSLT Functions</title>
<para>
The following functions are available if libxslt is installed: