diff --git a/doc/src/sgml/charset.sgml b/doc/src/sgml/charset.sgml
index 445fd17..c152bd9 100644
--- a/doc/src/sgml/charset.sgml
+++ b/doc/src/sgml/charset.sgml
@@ -939,7 +939,7 @@ CREATE COLLATION german (provider = libc, locale = 'de_DE');
See Unicode
Technical Standard #35
- and BCP 47 for
+ and BCP 47 for
details. The list of possible collation types (co
subtag) can be found in
the CLDR
@@ -2723,7 +2723,7 @@ RESET client_encoding;
- RFC 3629
+ RFC 3629
diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
index 68e73b9..02fa1ec 100644
--- a/doc/src/sgml/client-auth.sgml
+++ b/doc/src/sgml/client-auth.sgml
@@ -627,7 +627,7 @@ hostnogssenc databaseuserDistinguished Name (DN) of the certificate.
This option is probably best used in conjunction with a username map.
The comparison is done with the DN in
- RFC 2253
+ RFC 2253
format. To see the DN of a client certificate
in this format, do
@@ -977,7 +977,7 @@ omicron bryanh guest1
Ident authentication, which
relies on an Identification Protocol
- (RFC 1413)
+ (RFC 1413)
service on the client's machine. (On local Unix-socket connections,
this is treated as peer authentication.)
@@ -1116,7 +1116,7 @@ omicron bryanh guest1
The method scram-sha-256 performs SCRAM-SHA-256
authentication, as described in
- RFC 7677. It
+ RFC 7677. It
is a challenge-response scheme that prevents password sniffing on
untrusted connections and supports storing passwords on the server in a
cryptographically hashed form that is thought to be secure.
@@ -1228,7 +1228,7 @@ omicron bryanh guest1
GSSAPI is an industry-standard protocol
for secure authentication defined in
- RFC 2743.
+ RFC 2743.
PostgreSQL
supports GSSAPI for authentication,
communications encryption, or both.
@@ -1543,7 +1543,7 @@ omicron bryanh guest1
The Identification Protocol is described in
- RFC 1413.
+ RFC 1413.
Virtually every Unix-like
operating system ships with an ident server that listens on TCP
port 113 by default. The basic functionality of an ident server
@@ -1712,7 +1712,7 @@ omicron bryanh guest1
Set to 1 to make the connection between PostgreSQL and the LDAP server
use TLS encryption. This uses the StartTLS
- operation per RFC 4513.
+ operation per RFC 4513.
See also the ldapscheme option for an alternative.
@@ -1807,7 +1807,7 @@ omicron bryanh guest1
ldapurl
- An RFC 4516
+ An RFC 4516
LDAP URL. This is an alternative way to write some of the
other LDAP options in a more compact and standard form. The format is
@@ -1870,7 +1870,7 @@ ldap[s]://host[:port]/OpenLDAP as the LDAP client library, the
ldapserver setting may be omitted. In that case, a
list of host names and ports is looked up via
- RFC 2782 DNS SRV records.
+ RFC 2782 DNS SRV records.
The name _ldap._tcp.DOMAIN is looked up, where
DOMAIN is extracted from ldapbasedn.
diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml
index 5eb0cca..8dac308 100644
--- a/doc/src/sgml/datatype.sgml
+++ b/doc/src/sgml/datatype.sgml
@@ -2452,7 +2452,7 @@ TIMESTAMP WITH TIME ZONE '2004-10-19 10:23:54+02'
the date and time. PostgreSQL accepts that format on
input, but on output it uses a space rather than T, as shown
above. This is for readability and for consistency with
- RFC 3339 as
+ RFC 3339 as
well as some other database systems.
@@ -2850,10 +2850,31 @@ P years-months-
- Field values can have fractional parts: for example, '1.5
+ Internally, interval values are stored as three integral
+ fields: months, days, and microseconds. These fields are kept
+ separate because the number of days in a month varies, while a day
+ can have 23 or 25 hours if a daylight savings time transition is
+ involved. An interval input string that uses other units is
+ normalized into this format, and then reconstructed in a standardized
+ way for output, for example:
+
+
+SELECT '2 years 15 months 100 weeks 99 hours 123456789 milliseconds'::interval;
+ interval
+---------------------------------------
+ 3 years 3 mons 700 days 133:17:36.789
+
+
+ Here weeks, which are understood as 7 days, have been
+ kept separate, while the smaller and larger time units were
+ combined and normalized.
+
+
+
+ Input field values can have fractional parts, for example '1.5
weeks' or '01:02:03.45'. However,
- because interval internally stores only three integer units (months,
- days, microseconds), fractional units must be spilled to smaller
+ because interval internally stores only integral fields,
+ fractional values must be converted into smaller
units. Fractional parts of units greater than months are rounded to
be an integer number of months, e.g. '1.5 years'
becomes '1 year 6 mons'. Fractional parts of
@@ -2903,33 +2924,6 @@ P years-months-
-
- Internally interval values are stored as months, days,
- and microseconds. This is done because the number of days in a month
- varies, and a day can have 23 or 25 hours if a daylight savings
- time adjustment is involved. The months and days fields are integers
- while the microseconds field can store fractional seconds. Because intervals are
- usually created from constant strings or timestamp subtraction,
- this storage method works well in most cases, but can cause unexpected
- results:
-
-
-SELECT EXTRACT(hours from '80 minutes'::interval);
- date_part
------------
- 1
-
-SELECT EXTRACT(days from '80 hours'::interval);
- date_part
------------
- 0
-
-
- Functions justify_days and
- justify_hours are available for adjusting days
- and hours that overflow their normal ranges.
-
-
@@ -2941,6 +2935,23 @@ SELECT EXTRACT(days from '80 hours'::interval);
formatting
+
+ As previously explained, PostgreSQL
+ stores interval values as months, days, and
+ microseconds. For output, the months field is converted to years and
+ months by dividing by 12. The days field is shown as-is. The
+ microseconds field is converted to hours, minutes, seconds, and
+ fractional seconds. Thus months, minutes, and seconds will never be
+ shown as exceeding the ranges 0–11, 0–59, and 0–59
+ respectively, while the displayed years, days, and hours fields can
+ be quite large. (The justify_days
+ and justify_hours
+ functions can be used if it is desirable to transpose large days or
+ hours values into the next higher field.)
+
+
The output format of the interval type can be set to one of the
four styles sql_standard, postgres,
@@ -4337,7 +4348,7 @@ SELECT to_tsvector( 'postgraduate' ), to_tsquery( 'postgres:*' );
The data type uuid stores Universally Unique Identifiers
- (UUID) as defined by RFC 4122,
+ (UUID) as defined by RFC 4122,
ISO/IEC 9834-8:2005, and related standards.
(Some systems refer to this data type as a globally unique identifier, or
GUID,GUID instead.) This
diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml
index e406868..65b2802 100644
--- a/doc/src/sgml/ecpg.sgml
+++ b/doc/src/sgml/ecpg.sgml
@@ -3279,7 +3279,7 @@ int PGTYPEStimestamp_fmt_asc(timestamp *ts, char *output, int str_len, char *fmt
%z - is replaced by the time zone offset from
UTC; a leading plus sign stands for east of UTC, a minus sign for
west of UTC, hours and minutes follow with two digits each and no
- delimiter between them (common form for RFC 822 date headers).
+ delimiter between them (common form for RFC 822 date headers).
@@ -5753,6 +5753,14 @@ EXEC SQL UPDATE Tbl SET col = MYNUMBER;
embedded SQL query because in this case the embedded SQL precompiler is not
able to see this declaration.
+
+
+ If multiple input files are named on the ecpg
+ preprocessor's command line, the effects of EXEC SQL
+ DEFINE and EXEC SQL UNDEF do not carry
+ across files: each file starts with only the symbols defined
+ by switches on the command line.
+
@@ -8845,7 +8853,7 @@ int dectodbl(decimal *np, double *dblp);
dectoint
- Convert a variable to type decimal to an integer.
+ Convert a variable of type decimal to an integer.
int dectoint(decimal *np, int *ip);
@@ -8871,7 +8879,7 @@ int dectoint(decimal *np, int *ip);
dectolong
- Convert a variable to type decimal to a long integer.
+ Convert a variable of type decimal to a long integer.
int dectolong(decimal *np, long *lngp);
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 4dec679..48e5809 100644
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -4724,7 +4724,7 @@ SELECT format('Testing %3$s, %2$s, %s', 'one', 'two', 'three');
The base64 format is that
- of RFC
+ of RFC
2045 Section 6.8. As per the RFC, encoded lines are
broken at 76 characters. However instead of the MIME CRLF
end-of-line marker, only a newline is used for end-of-line.
@@ -8226,11 +8226,11 @@ SELECT regexp_match('abc01234xyz', '(?:(.*?)(\d+)(.*)){1,1}');
use some non-digit character or template after YYYY,
otherwise the year is always interpreted as 4 digits. For example
(with the year 20000):
- to_date('200001131', 'YYYYMMDD') will be
+ to_date('200001130', 'YYYYMMDD') will be
interpreted as a 4-digit year; instead use a non-digit
separator after the year, like
- to_date('20000-1131', 'YYYY-MMDD') or
- to_date('20000Nov31', 'YYYYMonDD').
+ to_date('20000-1130', 'YYYY-MMDD') or
+ to_date('20000Nov30', 'YYYYMonDD').
@@ -9018,7 +9018,8 @@ SELECT regexp_match('abc01234xyz', '(?:(.*?)(\d+)(.*)){1,1}');
Subtract timestamps (converting 24-hour intervals into days,
- similarly to justify_hours())
+ similarly to justify_hours())
timestamp '2001-09-29 03:00' - timestamp '2001-07-27 12:00'
@@ -9387,35 +9388,35 @@ SELECT regexp_match('abc01234xyz', '(?:(.*?)(\d+)(.*)){1,1}');
-
+ justify_daysjustify_days ( interval )
interval
- Adjust interval so 30-day time periods are represented as months
+ Adjust interval, converting 30-day time periods to months
- justify_days(interval '35 days')
- 1 mon 5 days
+ justify_days(interval '1 year 65 days')
+ 1 year 2 mons 5 days
-
+ justify_hoursjustify_hours ( interval )
interval
- Adjust interval so 24-hour time periods are represented as days
+ Adjust interval, converting 24-hour time periods to days
- justify_hours(interval '27 hours')
- 1 day 03:00:00
+ justify_hours(interval '50 hours 10 minutes')
+ 2 days 02:10:00
@@ -9838,13 +9839,19 @@ EXTRACT(field FROM source)
The extract function retrieves subfields
such as year or hour from date/time values.
source must be a value expression of
- type timestamp, time, or interval.
- (Expressions of type date are
- cast to timestamp and can therefore be used as
- well.) field is an identifier or
+ type timestamp, date, time,
+ or interval. (Timestamps and times can be with or
+ without time zone.)
+ field is an identifier or
string that selects what field to extract from the source value.
+ Not all fields are valid for every input data type; for example, fields
+ smaller than a day cannot be extracted from a date, while
+ fields of a day or more cannot be extracted from a time.
The extract function returns values of type
numeric.
+
+
+
The following are valid field names:
@@ -9853,7 +9860,8 @@ EXTRACT(field FROM source)
century
- The century
+ The century; for interval values, the year field
+ divided by 100
@@ -9861,17 +9869,13 @@ SELECT EXTRACT(CENTURY FROM TIMESTAMP '2000-12-16 12:21:13');
Result: 20
SELECT EXTRACT(CENTURY FROM TIMESTAMP '2001-02-16 20:38:40');
Result: 21
+SELECT EXTRACT(CENTURY FROM DATE '0001-01-01 AD');
+Result: 1
+SELECT EXTRACT(CENTURY FROM DATE '0001-12-31 BC');
+Result: -1
+SELECT EXTRACT(CENTURY FROM INTERVAL '2001 years');
+Result: 20
-
-
- The first century starts at 0001-01-01 00:00:00 AD, although
- they did not know it at the time. This definition applies to all
- Gregorian calendar countries. There is no century number 0,
- you go from -1 century to 1 century.
-
- If you disagree with this, please write your complaint to:
- Pope, Cathedral Saint-Peter of Roma, Vatican.
-
@@ -9879,14 +9883,13 @@ SELECT EXTRACT(CENTURY FROM TIMESTAMP '2001-02-16 20:38:40');
day
- For timestamp values, the day (of the month) field
- (1–31) ; for interval values, the number of days
+ The day of the month (1–31); for interval
+ values, the number of days
SELECT EXTRACT(DAY FROM TIMESTAMP '2001-02-16 20:38:40');
Result: 16
-
SELECT EXTRACT(DAY FROM INTERVAL '40 days 1 minute');
Result: 40
@@ -9960,10 +9963,8 @@ SELECT EXTRACT(DOY FROM TIMESTAMP '2001-02-16 20:38:40');
SELECT EXTRACT(EPOCH FROM TIMESTAMP WITH TIME ZONE '2001-02-16 20:38:40.12-08');
Result: 982384720.120000
-
SELECT EXTRACT(EPOCH FROM TIMESTAMP '2001-02-16 20:38:40.12');
Result: 982355920.120000
-
SELECT EXTRACT(EPOCH FROM INTERVAL '5 days 3 hours');
Result: 442800.000000
@@ -9991,7 +9992,8 @@ SELECT to_timestamp(982384720.12);
hour
- The hour field (0–23)
+ The hour field (0–23 in timestamps, unrestricted in
+ intervals)
@@ -10026,7 +10028,7 @@ SELECT EXTRACT(ISODOW FROM TIMESTAMP '2001-02-18 20:38:40');
The ISO 8601 week-numbering year that the date
- falls in (not applicable to intervals)
+ falls in
@@ -10043,9 +10045,6 @@ SELECT EXTRACT(ISOYEAR FROM DATE '2006-01-02');
different from the Gregorian year. See the week
field for more information.
-
- This field is not available in PostgreSQL releases prior to 8.3.
-
@@ -10054,7 +10053,7 @@ SELECT EXTRACT(ISOYEAR FROM DATE '2006-01-02');
The Julian Date corresponding to the
- date or timestamp (not applicable to intervals). Timestamps
+ date or timestamp. Timestamps
that are not local midnight result in a fractional value. See
for more information.
@@ -10087,12 +10086,15 @@ SELECT EXTRACT(MICROSECONDS FROM TIME '17:12:28.5');
millennium
- The millennium
+ The millennium; for interval values, the year field
+ divided by 1000
SELECT EXTRACT(MILLENNIUM FROM TIMESTAMP '2001-02-16 20:38:40');
Result: 3
+SELECT EXTRACT(MILLENNIUM FROM INTERVAL '2001 years');
+Result: 2
@@ -10135,18 +10137,16 @@ SELECT EXTRACT(MINUTE FROM TIMESTAMP '2001-02-16 20:38:40');
month
- For timestamp values, the number of the month
- within the year (1–12) ; for interval values,
- the number of months, modulo 12 (0–11)
+ The number of the month within the year (1–12);
+ for interval values, the number of months modulo 12
+ (0–11)
SELECT EXTRACT(MONTH FROM TIMESTAMP '2001-02-16 20:38:40');
Result: 2
-
SELECT EXTRACT(MONTH FROM INTERVAL '2 years 3 months');
Result: 3
-
SELECT EXTRACT(MONTH FROM INTERVAL '2 years 13 months');
Result: 1
@@ -10177,7 +10177,6 @@ SELECT EXTRACT(QUARTER FROM TIMESTAMP '2001-02-16 20:38:40');
SELECT EXTRACT(SECOND FROM TIMESTAMP '2001-02-16 20:38:40');
Result: 40.000000
-
SELECT EXTRACT(SECOND FROM TIME '17:12:28.5');
Result: 28.500000
@@ -10259,6 +10258,20 @@ SELECT EXTRACT(YEAR FROM TIMESTAMP '2001-02-16 20:38:40');
+
+ When processing an interval value,
+ the extract function produces field values that
+ match the interpretation used by the interval output function. This
+ can produce surprising results if one starts with a non-normalized
+ interval representation, for example:
+
+SELECT INTERVAL '80 minutes';
+Result: 01:20:00
+SELECT EXTRACT(MINUTES FROM INTERVAL '80 minutes');
+Result: 20
+
+
+
When the input value is +/-Infinity, extract returns
@@ -10296,7 +10309,6 @@ date_part('field', source)
SELECT date_part('day', TIMESTAMP '2001-02-16 20:38:40');
Result: 16
-
SELECT date_part('hour', INTERVAL '4 hours 3 minutes');
Result: 4
@@ -10374,16 +10386,12 @@ date_trunc(field, source [
SELECT date_trunc('hour', TIMESTAMP '2001-02-16 20:38:40');
Result: 2001-02-16 20:00:00
-
SELECT date_trunc('year', TIMESTAMP '2001-02-16 20:38:40');
Result: 2001-01-01 00:00:00
-
SELECT date_trunc('day', TIMESTAMP WITH TIME ZONE '2001-02-16 20:38:40+00');
Result: 2001-02-16 00:00:00-05
-
SELECT date_trunc('day', TIMESTAMP WITH TIME ZONE '2001-02-16 20:38:40+00', 'Australia/Sydney');
Result: 2001-02-16 08:00:00-05
-
SELECT date_trunc('hour', INTERVAL '3 days 02:47:33');
Result: 3 days 02:00:00
@@ -10422,7 +10430,6 @@ date_bin(stride, source, <
SELECT date_bin('15 minutes', TIMESTAMP '2020-02-11 15:44:17', TIMESTAMP '2001-01-01');
Result: 2020-02-11 15:30:00
-
SELECT date_bin('15 minutes', TIMESTAMP '2020-02-11 15:44:17', TIMESTAMP '2001-01-01 00:02:30');
Result: 2020-02-11 15:32:30
@@ -10546,10 +10553,8 @@ SELECT date_bin('15 minutes', TIMESTAMP '2020-02-11 15:44:17', TIMESTAMP '2001-0
SELECT TIMESTAMP '2001-02-16 20:38:40' AT TIME ZONE 'America/Denver';
Result: 2001-02-16 19:38:40-08
-
SELECT TIMESTAMP WITH TIME ZONE '2001-02-16 20:38:40-05' AT TIME ZONE 'America/Denver';
Result: 2001-02-16 18:38:40
-
SELECT TIMESTAMP '2001-02-16 20:38:40' AT TIME ZONE 'Asia/Tokyo' AT TIME ZONE 'America/Chicago';
Result: 2001-02-16 05:38:40
@@ -10624,16 +10629,12 @@ LOCALTIMESTAMP(precision)
SELECT CURRENT_TIME;
Result: 14:39:53.662522-05
-
SELECT CURRENT_DATE;
Result: 2019-12-23
-
SELECT CURRENT_TIMESTAMP;
Result: 2019-12-23 14:39:53.662522-05
-
SELECT CURRENT_TIMESTAMP(2);
Result: 2019-12-23 14:39:53.66-05
-
SELECT LOCALTIMESTAMP;
Result: 2019-12-23 14:39:53.662522
@@ -25551,7 +25552,7 @@ SELECT collation for ('foo' COLLATE "de_DE");
of its children.) You can use the
pg_file_settings,
pg_hba_file_rules and
- pg_ident_file_mappings views
+ pg_ident_file_mappings views
to check the configuration files for possible errors, before reloading.
diff --git a/doc/src/sgml/gist.sgml b/doc/src/sgml/gist.sgml
index 9ac6b03..1311f24 100644
--- a/doc/src/sgml/gist.sgml
+++ b/doc/src/sgml/gist.sgml
@@ -66,9 +66,9 @@
- box_ops
+ box_ops<< (box, box)
- <-> (box, point)
+ <-> (box, point)&< (box, box)&& (box, box)
@@ -81,13 +81,11 @@
<<| (box, box)|>> (box, box)|&> (box, box)
- ~ (box, box)
- @ (box, box)
- circle_ops
+ circle_ops<< (circle, circle)
- <-> (circle, point)
+ <-> (circle, point)&< (circle, circle)&> (circle, circle)
@@ -100,8 +98,6 @@
<<| (circle, circle)&<| (circle, circle)|&> (circle, circle)
- @ (circle, circle)
- ~ (circle, circle)inet_ops
@@ -156,9 +152,9 @@
<@ (point, circle)
- poly_ops
+ poly_ops<< (polygon, polygon)
- <-> (polygon, point)
+ <-> (polygon, point)&< (polygon, polygon)&> (polygon, polygon)
@@ -171,8 +167,6 @@
&<| (polygon, polygon)|&> (polygon, polygon)|>> (polygon, polygon)
- @ (polygon, polygon)
- ~ (polygon, polygon)range_ops
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index 7aa6fef..5fbdb46 100644
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -1296,7 +1296,7 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)'
synchronous_commit is set to on,
remote_apply or remote_write will wait for
responses from. Such transaction commits may never be completed
- if any one of synchronous standbys should crash.
+ if any one of the synchronous standbys should crash.
diff --git a/doc/src/sgml/html/acronyms.html b/doc/src/sgml/html/acronyms.html
index a732381..ba40789 100644
--- a/doc/src/sgml/html/acronyms.html
+++ b/doc/src/sgml/html/acronyms.html
@@ -1,5 +1,5 @@
-Appendix L. Acronyms
This is a list of acronyms commonly used in the PostgreSQL
documentation and in discussions about PostgreSQL.
@@ -137,7 +137,7 @@
Pluggable
Authentication Modules
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/admin.html b/doc/src/sgml/html/admin.html
index 592bbaa..1679e21 100644
--- a/doc/src/sgml/html/admin.html
+++ b/doc/src/sgml/html/admin.html
@@ -1,5 +1,5 @@
-Part III. Server Administration
This part covers topics that are of interest to a
PostgreSQL database administrator. This includes
installation of the software, set up and configuration of the
@@ -23,4 +23,4 @@
the PostgreSQL database system. Readers are
encouraged to look at Part I and Part II for additional information.
\ No newline at end of file
diff --git a/doc/src/sgml/html/adminpack.html b/doc/src/sgml/html/adminpack.html
index 974ee3d..0e175d7 100644
--- a/doc/src/sgml/html/adminpack.html
+++ b/doc/src/sgml/html/adminpack.html
@@ -1,5 +1,5 @@
-F.1. adminpack
adminpack provides a number of support functions which
pgAdmin and other administration and management tools can
use to provide additional functionality, such as remote management
@@ -86,4 +86,4 @@
directory. The log_filename parameter must have its
default setting (postgresql-%Y-%m-%d_%H%M%S.log) to use this
function.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/amcheck.html b/doc/src/sgml/html/amcheck.html
index a896fdc..52701bc 100644
--- a/doc/src/sgml/html/amcheck.html
+++ b/doc/src/sgml/html/amcheck.html
@@ -1,5 +1,5 @@
-F.2. amcheck
The amcheck module provides functions that allow you to
verify the logical consistency of the structure of relations.
@@ -374,4 +374,4 @@ SET client_min_messages = DEBUG1;
an invariant violation should be sought. pageinspect may play a useful role in diagnosing
corruption that amcheck detects. A REINDEX
may not be effective in repairing corruption.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-clusterdb.html b/doc/src/sgml/html/app-clusterdb.html
index f0821fa..493b665 100644
--- a/doc/src/sgml/html/app-clusterdb.html
+++ b/doc/src/sgml/html/app-clusterdb.html
@@ -1,5 +1,5 @@
-clusterdb
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-createdb.html b/doc/src/sgml/html/app-createdb.html
index f54a08f..85d283f 100644
--- a/doc/src/sgml/html/app-createdb.html
+++ b/doc/src/sgml/html/app-createdb.html
@@ -1,5 +1,5 @@
-createdb
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-createuser.html b/doc/src/sgml/html/app-createuser.html
index 7663ceb..a926c77 100644
--- a/doc/src/sgml/html/app-createuser.html
+++ b/doc/src/sgml/html/app-createuser.html
@@ -1,5 +1,5 @@
-createuser
createuser creates a
new PostgreSQL user (or more precisely, a role).
Only superusers and users with CREATEROLE privilege can create
@@ -187,4 +187,4 @@
In the above example, the new password isn't actually echoed when typed,
but we show what was typed for clarity. As you see, the password is
encrypted before it is sent to the client.
-
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-dropdb.html b/doc/src/sgml/html/app-dropdb.html
index 122227e..c26da35 100644
--- a/doc/src/sgml/html/app-dropdb.html
+++ b/doc/src/sgml/html/app-dropdb.html
@@ -1,5 +1,5 @@
-dropdb
dropdb destroys an existing
PostgreSQL database.
The user who executes this command must be a database
@@ -108,4 +108,4 @@
Database "demo" will be permanently deleted.
Are you sure? (y/n) yDROP DATABASE demo;
-
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-dropuser.html b/doc/src/sgml/html/app-dropuser.html
index 795d411..2e55407 100644
--- a/doc/src/sgml/html/app-dropuser.html
+++ b/doc/src/sgml/html/app-dropuser.html
@@ -1,5 +1,5 @@
-dropuser
dropuser removes an existing
PostgreSQL user.
Only superusers and users with the CREATEROLE privilege can
@@ -100,4 +100,4 @@
Role "joe" will be permanently removed.
Are you sure? (y/n) yDROP ROLE joe;
-
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-ecpg.html b/doc/src/sgml/html/app-ecpg.html
index 2b48acf..597ea74 100644
--- a/doc/src/sgml/html/app-ecpg.html
+++ b/doc/src/sgml/html/app-ecpg.html
@@ -1,5 +1,5 @@
-ecpg
ecpg is the embedded SQL preprocessor for C
programs. It converts C programs with embedded SQL statements to
normal C code by replacing the SQL invocations with special
@@ -32,8 +32,10 @@
Set a compatibility mode. mode can
be INFORMIX,
INFORMIX_SE, or ORACLE.
-
-D symbol
- Define a C preprocessor symbol.
+
-D symbol[=value]
+ Define a preprocessor symbol, equivalently to the EXEC SQL
+ DEFINE directive. If no value is
+ specified, the symbol is defined with the value 1.
-h
Process header files. When this option is specified, the output file
extension becomes .h not .c,
@@ -103,4 +105,4 @@
ecpg prog1.pgc
cc -I/usr/local/pgsql/include -c prog1.c
cc -o prog1 prog1.o -L/usr/local/pgsql/lib -lecpg
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-initdb.html b/doc/src/sgml/html/app-initdb.html
index b02c604..21f2c40 100644
--- a/doc/src/sgml/html/app-initdb.html
+++ b/doc/src/sgml/html/app-initdb.html
@@ -1,5 +1,5 @@
-initdb
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-pg-ctl.html b/doc/src/sgml/html/app-pg-ctl.html
index aa490cd..e104ea1 100644
--- a/doc/src/sgml/html/app-pg-ctl.html
+++ b/doc/src/sgml/html/app-pg-ctl.html
@@ -1,5 +1,5 @@
-pg_ctl
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-pg-dumpall.html b/doc/src/sgml/html/app-pg-dumpall.html
index 1d374d6..0928c6e 100644
--- a/doc/src/sgml/html/app-pg-dumpall.html
+++ b/doc/src/sgml/html/app-pg-dumpall.html
@@ -1,5 +1,5 @@
-pg_dumpall
pg_dumpall — extract a PostgreSQL database cluster into a script file
Synopsis
pg_dumpall [connection-option...] [option...]
Description
pg_dumpall is a utility for writing out
(“dumping”) all PostgreSQL databases
of a cluster into one script file. The script file contains
@@ -361,4 +361,4 @@
See Also
Check pg_dump for details on possible
error conditions.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-pg-isready.html b/doc/src/sgml/html/app-pg-isready.html
index 31a2f67..1a2a65b 100644
--- a/doc/src/sgml/html/app-pg-isready.html
+++ b/doc/src/sgml/html/app-pg-isready.html
@@ -1,5 +1,5 @@
-pg_isready
pg_isready — check the connection status of a PostgreSQL server
Synopsis
pg_isready [connection-option...] [option...]
Description
pg_isready is a utility for checking the connection
status of a PostgreSQL database server. The exit
status specifies the result of the connection check.
@@ -76,4 +76,4 @@
$echo $?2
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-pgamcheck.html b/doc/src/sgml/html/app-pgamcheck.html
index 1fdcc18..f5994e4 100644
--- a/doc/src/sgml/html/app-pgamcheck.html
+++ b/doc/src/sgml/html/app-pgamcheck.html
@@ -1,5 +1,5 @@
-pg_amcheck
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-pgbasebackup.html b/doc/src/sgml/html/app-pgbasebackup.html
index c987d24..29cb212 100644
--- a/doc/src/sgml/html/app-pgbasebackup.html
+++ b/doc/src/sgml/html/app-pgbasebackup.html
@@ -1,5 +1,5 @@
-pg_basebackup
pg_basebackup — take a base backup of a PostgreSQL cluster
Synopsis
pg_basebackup [option...]
Description
pg_basebackup is used to take a base backup of
a running PostgreSQL database cluster. The backup
is taken without affecting other clients of the database, and can be used
@@ -483,7 +483,8 @@
The backup will include all files in the data directory and tablespaces,
including the configuration files and any additional files placed in the
directory by third parties, except certain temporary files managed by
- PostgreSQL. But only regular files and directories are copied, except that
+ PostgreSQL and operating system files. But only regular files and
+ directories are copied, except that
symbolic links used for tablespaces are preserved. Symbolic links pointing
to certain directories known to PostgreSQL are copied as empty directories.
Other symbolic links and special device files are skipped.
@@ -547,4 +548,4 @@
directory backup:
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-pgchecksums.html b/doc/src/sgml/html/app-pgchecksums.html
index bc90b0e..e6be629 100644
--- a/doc/src/sgml/html/app-pgchecksums.html
+++ b/doc/src/sgml/html/app-pgchecksums.html
@@ -1,5 +1,5 @@
-pg_checksums
pg_checksums checks, enables or disables data
checksums in a PostgreSQL cluster. The server
must be shut down cleanly before running
@@ -72,4 +72,4 @@
enabling or disabling checksums, the cluster's data checksum configuration
remains unchanged, and pg_checksums can be
re-run to perform the same operation.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-pgconfig.html b/doc/src/sgml/html/app-pgconfig.html
index 124c73d..8a458c8 100644
--- a/doc/src/sgml/html/app-pgconfig.html
+++ b/doc/src/sgml/html/app-pgconfig.html
@@ -1,5 +1,5 @@
-pg_config
pg_config — retrieve information about the installed version of PostgreSQL
Synopsis
pg_config [option...]
Description
The pg_config utility prints configuration parameters
of the currently installed version of PostgreSQL. It is
intended, for example, to be used by software packages that want to interface
@@ -107,4 +107,4 @@ eval ./configure `pg_config --configure`
shell quotation marks so arguments with spaces are represented
correctly. Therefore, using eval is required
for proper results.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-pgcontroldata.html b/doc/src/sgml/html/app-pgcontroldata.html
index cccb75e..524376c 100644
--- a/doc/src/sgml/html/app-pgcontroldata.html
+++ b/doc/src/sgml/html/app-pgcontroldata.html
@@ -1,5 +1,5 @@
-pg_controldata
pg_controldata prints information initialized during
initdb, such as the catalog version.
It also shows information about write-ahead logging and checkpoint
@@ -20,4 +20,4 @@
Specifies whether to use color in diagnostic messages. Possible values
are always, auto and
never.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-pgdump.html b/doc/src/sgml/html/app-pgdump.html
index 0add9b8..35c3607 100644
--- a/doc/src/sgml/html/app-pgdump.html
+++ b/doc/src/sgml/html/app-pgdump.html
@@ -1,5 +1,5 @@
-pg_dump
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-pgreceivewal.html b/doc/src/sgml/html/app-pgreceivewal.html
index e82e98b..571241e 100644
--- a/doc/src/sgml/html/app-pgreceivewal.html
+++ b/doc/src/sgml/html/app-pgreceivewal.html
@@ -1,5 +1,5 @@
-pg_receivewal
pg_receivewal — stream write-ahead logs from a PostgreSQL server
Synopsis
pg_receivewal [option...]
Description
pg_receivewal is used to stream the write-ahead log
from a running PostgreSQL cluster. The write-ahead
log is streamed using the streaming replication protocol, and is written
@@ -246,4 +246,4 @@
/usr/local/pgsql/archive:
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-pgreceivexlog.html b/doc/src/sgml/html/app-pgreceivexlog.html
index 18edb30..6e0b1e1 100644
--- a/doc/src/sgml/html/app-pgreceivexlog.html
+++ b/doc/src/sgml/html/app-pgreceivexlog.html
@@ -1,10 +1,10 @@
-O.5. pg_receivexlog renamed to pg_receivewal
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-pgrecvlogical.html b/doc/src/sgml/html/app-pgrecvlogical.html
index 3e547c2..b690d48 100644
--- a/doc/src/sgml/html/app-pgrecvlogical.html
+++ b/doc/src/sgml/html/app-pgrecvlogical.html
@@ -1,5 +1,5 @@
-pg_recvlogical
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-pgresetwal.html b/doc/src/sgml/html/app-pgresetwal.html
index 12f6173..c9dd504 100644
--- a/doc/src/sgml/html/app-pgresetwal.html
+++ b/doc/src/sgml/html/app-pgresetwal.html
@@ -1,5 +1,5 @@
-pg_resetwal
pg_resetwal clears the write-ahead log (WAL) and
optionally resets some other control information stored in the
pg_control file. This function is sometimes needed
@@ -166,4 +166,4 @@
pg_resetwal works only with servers of the same
major version.
-
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-pgresetxlog.html b/doc/src/sgml/html/app-pgresetxlog.html
index 12a52d9..98aa9ed 100644
--- a/doc/src/sgml/html/app-pgresetxlog.html
+++ b/doc/src/sgml/html/app-pgresetxlog.html
@@ -1,10 +1,10 @@
-O.4. pg_resetxlog renamed to pg_resetwal
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-pgrestore.html b/doc/src/sgml/html/app-pgrestore.html
index 29f8ab4..069a09c 100644
--- a/doc/src/sgml/html/app-pgrestore.html
+++ b/doc/src/sgml/html/app-pgrestore.html
@@ -1,5 +1,5 @@
-pg_restore
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-pgrewind.html b/doc/src/sgml/html/app-pgrewind.html
index 3ef9414..8e59127 100644
--- a/doc/src/sgml/html/app-pgrewind.html
+++ b/doc/src/sgml/html/app-pgrewind.html
@@ -1,5 +1,5 @@
-pg_rewind
pg_rewind is a tool for synchronizing a PostgreSQL cluster
with another copy of the same cluster, after the clusters' timelines have
diverged. A typical scenario is to bring an old primary server back online
@@ -199,8 +199,9 @@ GRANT EXECUTE ON function pg_catalog.pg_read_binary_file(text, bigint, bigint, b
backup_label,
tablespace_map,
pg_internal.init,
- postmaster.opts, and
- postmaster.pid, as well as any file or directory
+ postmaster.opts,
+ postmaster.pid and
+ .DS_Store as well as any file or directory
beginning with pgsql_tmp, are omitted.
Create a backup_label file to begin WAL replay at
@@ -213,4 +214,4 @@ GRANT EXECUTE ON function pg_catalog.pg_read_binary_file(text, bigint, bigint, b
When starting the target, PostgreSQL replays
all the required WAL, resulting in a data directory in a consistent
state.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-pgverifybackup.html b/doc/src/sgml/html/app-pgverifybackup.html
index b2ced0f..0c76b3e 100644
--- a/doc/src/sgml/html/app-pgverifybackup.html
+++ b/doc/src/sgml/html/app-pgverifybackup.html
@@ -1,5 +1,5 @@
-pg_verifybackup
pg_verifybackup — verify the integrity of a base backup of a
PostgreSQL cluster
Synopsis
pg_verifybackup [option...]
Description
pg_verifybackup is used to check the
integrity of a database cluster backup taken using
@@ -141,4 +141,4 @@
$pg_basebackup -h mydbserver -D /usr/local/pgsql/data$edit /usr/local/pgsql/data/note.to.self$pg_verifybackup --ignore=note.to.self --skip-checksums /usr/local/pgsql/data
-
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-postgres.html b/doc/src/sgml/html/app-postgres.html
index 8b834d9..0940848 100644
--- a/doc/src/sgml/html/app-postgres.html
+++ b/doc/src/sgml/html/app-postgres.html
@@ -1,5 +1,5 @@
-postgres
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-postmaster.html b/doc/src/sgml/html/app-postmaster.html
index ceb75e8..16907d0 100644
--- a/doc/src/sgml/html/app-postmaster.html
+++ b/doc/src/sgml/html/app-postmaster.html
@@ -1,6 +1,6 @@
-postmaster
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-psql.html b/doc/src/sgml/html/app-psql.html
index c3f9696..9d790b6 100644
--- a/doc/src/sgml/html/app-psql.html
+++ b/doc/src/sgml/html/app-psql.html
@@ -1,5 +1,5 @@
-psql
Turn on the expanded table formatting mode. This is equivalent to
\x or \pset expanded.
-
-X, --no-psqlrc
+
-X --no-psqlrc
Do not read the start-up file (neither the system-wide
psqlrc file nor the user's
~/.psqlrc file).
@@ -345,7 +345,7 @@ $ psql postgresql://dbmaster:5433/mydb?sslmode=r
the string =>. For example:
$ psql testdb
-psql (15.6)
+psql (15.7)
Type "help" for help.
testdb=>
@@ -1675,7 +1675,7 @@ lo_import 152801
writes column values separated by commas, applying the quoting
rules described in
- RFC 4180.
+ RFC 4180.
This output is compatible with the CSV format of the server's
COPY command.
A header line with column names is generated unless
@@ -2725,7 +2725,7 @@ PSQL_EDITOR_LINENUMBER_ARG='--line '
by appending a dash and the PostgreSQL
major or minor release identifier to the file name,
for example ~/.psqlrc-15 or
- ~/.psqlrc-15.6.
+ ~/.psqlrc-15.7.
The most specific version-matching file will be read in preference
to a non-version-specific file.
These version suffixes are added after determining the file path
@@ -2956,4 +2956,4 @@ testdb(> \crosstabview "A" "B" "AxB" ord
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-reindexdb.html b/doc/src/sgml/html/app-reindexdb.html
index f339b67..f7cbf95 100644
--- a/doc/src/sgml/html/app-reindexdb.html
+++ b/doc/src/sgml/html/app-reindexdb.html
@@ -1,5 +1,5 @@
-reindexdb
\ No newline at end of file
diff --git a/doc/src/sgml/html/app-vacuumdb.html b/doc/src/sgml/html/app-vacuumdb.html
index 3dd8984..be628d5 100644
--- a/doc/src/sgml/html/app-vacuumdb.html
+++ b/doc/src/sgml/html/app-vacuumdb.html
@@ -1,5 +1,5 @@
-vacuumdb
\ No newline at end of file
diff --git a/doc/src/sgml/html/appendix-obsolete.html b/doc/src/sgml/html/appendix-obsolete.html
index db375f2..3e8ab9c 100644
--- a/doc/src/sgml/html/appendix-obsolete.html
+++ b/doc/src/sgml/html/appendix-obsolete.html
@@ -1,8 +1,8 @@
-Appendix O. Obsolete or Renamed Features
Functionality is sometimes removed from PostgreSQL, feature, setting
and file names sometimes change, or documentation moves to different
places. This section directs users coming from old versions of the
documentation or from external links to the appropriate new location
for the information they need.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/appendixes.html b/doc/src/sgml/html/appendixes.html
index fed3a4c..4d51d01 100644
--- a/doc/src/sgml/html/appendixes.html
+++ b/doc/src/sgml/html/appendixes.html
@@ -1,2 +1,2 @@
-Part VIII. Appendixes
\ No newline at end of file
diff --git a/doc/src/sgml/html/applevel-consistency.html b/doc/src/sgml/html/applevel-consistency.html
index dc66d8f..e10557b 100644
--- a/doc/src/sgml/html/applevel-consistency.html
+++ b/doc/src/sgml/html/applevel-consistency.html
@@ -1,5 +1,5 @@
-13.4. Data Consistency Checks at the Application Level
13.4. Data Consistency Checks at the Application Level
It is very difficult to enforce business rules regarding data integrity
using Read Committed transactions because the view of the data is
shifting with each statement, and even a single statement may not
@@ -111,4 +111,4 @@
UPDATE, DELETE, or
MERGE), so it is possible to obtain locks explicitly
before the snapshot is frozen.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/archive-module-callbacks.html b/doc/src/sgml/html/archive-module-callbacks.html
index 4b3517b..afb8624 100644
--- a/doc/src/sgml/html/archive-module-callbacks.html
+++ b/doc/src/sgml/html/archive-module-callbacks.html
@@ -1,5 +1,5 @@
-51.2. Archive Module Callbacks
\ No newline at end of file
diff --git a/doc/src/sgml/html/archive-module-init.html b/doc/src/sgml/html/archive-module-init.html
index 9623dcc..e5a732e 100644
--- a/doc/src/sgml/html/archive-module-init.html
+++ b/doc/src/sgml/html/archive-module-init.html
@@ -1,5 +1,5 @@
-51.1. Initialization Functions
An archive library is loaded by dynamically loading a shared library with the
archive_library's name as the library base name. The
normal library search path is used to locate the library. To provide the
@@ -21,4 +21,4 @@ typedef void (*ArchiveModuleInit) (struct ArchiveModuleCallbacks *cb);
Only the archive_file_cb callback is required. The
others are optional.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/archive-modules.html b/doc/src/sgml/html/archive-modules.html
index 6f72471..1133e91 100644
--- a/doc/src/sgml/html/archive-modules.html
+++ b/doc/src/sgml/html/archive-modules.html
@@ -1,5 +1,5 @@
-Chapter 51. Archive Modules
PostgreSQL provides infrastructure to create custom modules for continuous
archiving (see Section 26.3). While archiving via
a shell command (i.e., archive_command) is much
@@ -21,4 +21,4 @@
The contrib/basic_archive module contains a working
example, which demonstrates some useful techniques.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/arrays.html b/doc/src/sgml/html/arrays.html
index 091b1f5..c5fd36b 100644
--- a/doc/src/sgml/html/arrays.html
+++ b/doc/src/sgml/html/arrays.html
@@ -1,5 +1,5 @@
-8.15. Arrays
PostgreSQL allows columns of a table to be
defined as variable-length multidimensional arrays. Arrays of any
built-in or user-defined base type, enum type, composite type, range type,
@@ -644,4 +644,4 @@ SELECT f1[1][-2][3] AS e1, f1[1][-1][5] AS e2
with than the array-literal syntax when writing array values in SQL
commands. In ARRAY, individual element values are written the
same way they would be written when not members of an array.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/auth-bsd.html b/doc/src/sgml/html/auth-bsd.html
index 1f5c038..5de892e 100644
--- a/doc/src/sgml/html/auth-bsd.html
+++ b/doc/src/sgml/html/auth-bsd.html
@@ -1,5 +1,5 @@
-21.14. BSD Authentication
This authentication method operates similarly to
password except that it uses BSD Authentication
to verify the password. BSD Authentication is used only
@@ -18,4 +18,4 @@
operating system user running the server) must first be added to
the auth group. The auth group
exists by default on OpenBSD systems.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/auth-cert.html b/doc/src/sgml/html/auth-cert.html
index 781da73..43353e7 100644
--- a/doc/src/sgml/html/auth-cert.html
+++ b/doc/src/sgml/html/auth-cert.html
@@ -1,5 +1,5 @@
-21.12. Certificate Authentication
This authentication method uses SSL client certificates to perform
authentication. It is therefore only available for SSL connections;
see Section 19.9.2 for SSL configuration instructions.
@@ -22,4 +22,4 @@
cert authentication because cert
authentication is effectively trust authentication
with clientcert=verify-full.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/auth-delay.html b/doc/src/sgml/html/auth-delay.html
index 2d7addb..efd62a8 100644
--- a/doc/src/sgml/html/auth-delay.html
+++ b/doc/src/sgml/html/auth-delay.html
@@ -1,5 +1,5 @@
-F.3. auth_delay
auth_delay causes the server to pause briefly before
reporting authentication failure, to make brute-force attacks on database
passwords more difficult. Note that it does nothing to prevent
@@ -25,4 +25,4 @@ shared_preload_libraries = 'auth_delay'
auth_delay.milliseconds = '500'
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/auth-ident.html b/doc/src/sgml/html/auth-ident.html
index fcf6b20..58fdb2d 100644
--- a/doc/src/sgml/html/auth-ident.html
+++ b/doc/src/sgml/html/auth-ident.html
@@ -1,5 +1,5 @@
-21.8. Ident Authentication
The ident authentication method works by obtaining the client's
operating system user name from an ident server and using it as
the allowed database user name (with an optional user name mapping).
@@ -16,7 +16,7 @@
The “Identification Protocol” is described in
- RFC 1413.
+ RFC 1413.
Virtually every Unix-like
operating system ships with an ident server that listens on TCP
port 113 by default. The basic functionality of an ident server
@@ -49,4 +49,4 @@
used when using the ident server with PostgreSQL,
since PostgreSQL does not have any way to decrypt the
returned string to determine the actual user name.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/auth-ldap.html b/doc/src/sgml/html/auth-ldap.html
index 5f87020..31ff76f 100644
--- a/doc/src/sgml/html/auth-ldap.html
+++ b/doc/src/sgml/html/auth-ldap.html
@@ -1,5 +1,5 @@
-21.10. LDAP Authentication
This authentication method operates similarly to
password except that it uses LDAP
as the password verification method. LDAP is used only to validate
@@ -49,7 +49,7 @@
ldaptls
Set to 1 to make the connection between PostgreSQL and the LDAP server
use TLS encryption. This uses the StartTLS
- operation per RFC 4513.
+ operation per RFC 4513.
See also the ldapscheme option for an alternative.
@@ -88,7 +88,7 @@
user name. This allows for more flexible search filters than
ldapsearchattribute.
ldapurl
- An RFC 4516
+ An RFC 4516
LDAP URL. This is an alternative way to write some of the
other LDAP options in a more compact and standard form. The format is
@@ -136,7 +136,7 @@ ldap[s]://host[:OpenLDAP as the LDAP client library, the
ldapserver setting may be omitted. In that case, a
list of host names and ports is looked up via
- RFC 2782 DNS SRV records.
+ RFC 2782 DNS SRV records.
The name _ldap._tcp.DOMAIN is looked up, where
DOMAIN is extracted from ldapbasedn.
@@ -187,4 +187,4 @@ host ... ldap ldapbasedn="dc=example,dc=net"
Since LDAP often uses commas and spaces to separate the different
parts of a DN, it is often necessary to use double-quoted parameter
values when configuring LDAP options, as shown in the examples.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/auth-methods.html b/doc/src/sgml/html/auth-methods.html
index 0f6f712..39cf1c3 100644
--- a/doc/src/sgml/html/auth-methods.html
+++ b/doc/src/sgml/html/auth-methods.html
@@ -1,5 +1,5 @@
-21.3. Authentication Methods
PostgreSQL provides various methods for
authenticating users:
@@ -20,7 +20,7 @@
Ident authentication, which
relies on an “Identification Protocol”
- (RFC 1413)
+ (RFC 1413)
service on the client's machine. (On local Unix-socket connections,
this is treated as peer authentication.)
@@ -56,4 +56,4 @@
The following sections describe each of these authentication methods
in more detail.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/auth-pam.html b/doc/src/sgml/html/auth-pam.html
index 4e5c411..7951c5d 100644
--- a/doc/src/sgml/html/auth-pam.html
+++ b/doc/src/sgml/html/auth-pam.html
@@ -1,5 +1,5 @@
-21.13. PAM Authentication
This authentication method operates similarly to
password except that it uses PAM (Pluggable
Authentication Modules) as the authentication mechanism. The
@@ -28,4 +28,4 @@
will fail because the PostgreSQL server is started by a non-root
user. However, this is not an issue when PAM is configured to use
LDAP or other authentication methods.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/auth-password.html b/doc/src/sgml/html/auth-password.html
index afa7927..67ed974 100644
--- a/doc/src/sgml/html/auth-password.html
+++ b/doc/src/sgml/html/auth-password.html
@@ -1,5 +1,5 @@
-21.5. Password Authentication
There are several password-based authentication methods. These methods
operate similarly but differ in how the users' passwords are stored on the
server and how the password provided by a client is sent across the
@@ -7,7 +7,7 @@
scram-sha-256
The method scram-sha-256 performs SCRAM-SHA-256
authentication, as described in
- RFC 7677. It
+ RFC 7677. It
is a challenge-response scheme that prevents password sniffing on
untrusted connections and supports storing passwords on the server in a
cryptographically hashed form that is thought to be secure.
@@ -77,4 +77,4 @@
in postgresql.conf, make all users set new passwords,
and change the authentication method specifications
in pg_hba.conf to scram-sha-256.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/auth-peer.html b/doc/src/sgml/html/auth-peer.html
index 01c76d5..5df0bfb 100644
--- a/doc/src/sgml/html/auth-peer.html
+++ b/doc/src/sgml/html/auth-peer.html
@@ -1,5 +1,5 @@
-21.9. Peer Authentication
The peer authentication method works by obtaining the client's
operating system user name from the kernel and using it as the
allowed database user name (with optional user name mapping). This
@@ -18,4 +18,4 @@
most flavors of BSD including
macOS,
and Solaris.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/auth-pg-hba-conf.html b/doc/src/sgml/html/auth-pg-hba-conf.html
index c1adeb4..7e79b5d 100644
--- a/doc/src/sgml/html/auth-pg-hba-conf.html
+++ b/doc/src/sgml/html/auth-pg-hba-conf.html
@@ -1,5 +1,5 @@
-21.1. The pg_hba.conf File
Client authentication is controlled by a configuration file,
which traditionally is named
pg_hba.conf and is stored in the database
@@ -337,7 +337,7 @@ hostnogssenc databaseDistinguished Name (DN) of the certificate.
This option is probably best used in conjunction with a username map.
The comparison is done with the DN in
- RFC 2253
+ RFC 2253
format. To see the DN of a client certificate
in this format, do
@@ -489,4 +489,4 @@ local all @admins,+support md5
# The database column can also use lists and file names:
local db1,db2,@demodbs all md5
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/auth-radius.html b/doc/src/sgml/html/auth-radius.html
index 733297e..6ef9a22 100644
--- a/doc/src/sgml/html/auth-radius.html
+++ b/doc/src/sgml/html/auth-radius.html
@@ -1,5 +1,5 @@
-21.11. RADIUS Authentication
This authentication method operates similarly to
password except that it uses RADIUS
as the password verification method. RADIUS is used only to validate
@@ -62,4 +62,4 @@
\ No newline at end of file
diff --git a/doc/src/sgml/html/auth-trust.html b/doc/src/sgml/html/auth-trust.html
index c1a3abf..673af9b 100644
--- a/doc/src/sgml/html/auth-trust.html
+++ b/doc/src/sgml/html/auth-trust.html
@@ -1,5 +1,5 @@
-21.4. Trust Authentication
When trust authentication is specified,
PostgreSQL assumes that anyone who can
connect to the server is authorized to access the database with
@@ -34,4 +34,4 @@
to the server by the pg_hba.conf lines that specify
trust. It is seldom reasonable to use trust
for any TCP/IP connections other than those from localhost (127.0.0.1).
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/auth-username-maps.html b/doc/src/sgml/html/auth-username-maps.html
index d7c2575..6f28d67 100644
--- a/doc/src/sgml/html/auth-username-maps.html
+++ b/doc/src/sgml/html/auth-username-maps.html
@@ -1,5 +1,5 @@
-21.2. User Name Maps
When using an external authentication system such as Ident or GSSAPI,
the name of the operating system user that initiated the connection
might not be the same as the database user (role) that is to be used.
@@ -99,4 +99,4 @@ omicron ann ann
omicron robert bob
# bryanh can also connect as guest1
omicron bryanh guest1
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/auto-explain.html b/doc/src/sgml/html/auto-explain.html
index 8132672..ec07f9d 100644
--- a/doc/src/sgml/html/auto-explain.html
+++ b/doc/src/sgml/html/auto-explain.html
@@ -1,5 +1,5 @@
-F.4. auto_explain
The auto_explain module provides a means for
logging execution plans of slow statements automatically, without
having to run EXPLAIN
@@ -186,4 +186,4 @@ LOG: duration: 3.651 ms plan:
Filter: indisunique
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/backup-dump.html b/doc/src/sgml/html/backup-dump.html
index 4bdd695..0b7003c 100644
--- a/doc/src/sgml/html/backup-dump.html
+++ b/doc/src/sgml/html/backup-dump.html
@@ -1,5 +1,5 @@
-26.1. SQL Dump
The idea behind this dump method is to generate a file with SQL
commands that, when fed back to the server, will recreate the
database in the same state as it was at the time of the dump.
@@ -244,4 +244,4 @@ pg_dump -j num -F d -f pg_restore -j to restore a dump in parallel.
This will work for any archive of either the "custom" or the "directory"
archive mode, whether or not it has been created with pg_dump -j.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/backup-file.html b/doc/src/sgml/html/backup-file.html
index 6e460b1..30ca65b 100644
--- a/doc/src/sgml/html/backup-file.html
+++ b/doc/src/sgml/html/backup-file.html
@@ -1,5 +1,5 @@
-26.2. File System Level Backup
An alternative backup strategy is to directly copy the files that
PostgreSQL uses to store the data in the database;
Section 19.2 explains where these files
@@ -88,4 +88,4 @@ tar -cf backup.tar /usr/local/pgsql/data
than an SQL dump. (pg_dump does not need to dump
the contents of indexes for example, just the commands to recreate
them.) However, taking a file system backup might be faster.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/backup-manifest-files.html b/doc/src/sgml/html/backup-manifest-files.html
index 5ab0d3d..4198944 100644
--- a/doc/src/sgml/html/backup-manifest-files.html
+++ b/doc/src/sgml/html/backup-manifest-files.html
@@ -1,5 +1,5 @@
-76.2. Backup Manifest File Object
The object which describes a single file contains either a
Path key or an Encoded-Path key.
Normally, the Path key will be present. The
@@ -36,4 +36,4 @@
Checksum
The checksum computed for this file, stored as a series of
hexadecimal characters, two for each byte of the checksum.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/backup-manifest-format.html b/doc/src/sgml/html/backup-manifest-format.html
index 7d5fd40..0c4d0c2 100644
--- a/doc/src/sgml/html/backup-manifest-format.html
+++ b/doc/src/sgml/html/backup-manifest-format.html
@@ -1,5 +1,5 @@
-Chapter 76. Backup Manifest Format
The backup manifest generated by pg_basebackup is
primarily intended to permit the backup to be verified using
pg_verifybackup. However, it is
@@ -13,4 +13,4 @@
supported server encoding. There is no similar exception for backup
manifests.) The JSON document is always an object; the keys that are present
in this object are described in the next section.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/backup-manifest-toplevel.html b/doc/src/sgml/html/backup-manifest-toplevel.html
index 71300d5..ccffe7d 100644
--- a/doc/src/sgml/html/backup-manifest-toplevel.html
+++ b/doc/src/sgml/html/backup-manifest-toplevel.html
@@ -1,5 +1,5 @@
-76.1. Backup Manifest Top-level Object
The backup manifest JSON document contains the following keys.
PostgreSQL-Backup-Manifest-Version
The associated value is always the integer 1.
@@ -22,4 +22,4 @@
is significantly more expensive than a CRC32C checksum, the manifest
should normally be small enough that the extra computation won't matter
very much.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/backup-manifest-wal-ranges.html b/doc/src/sgml/html/backup-manifest-wal-ranges.html
index d5248b2..29624aa 100644
--- a/doc/src/sgml/html/backup-manifest-wal-ranges.html
+++ b/doc/src/sgml/html/backup-manifest-wal-ranges.html
@@ -1,5 +1,5 @@
-76.3. Backup Manifest WAL Range Object
The object which describes a WAL range always has three keys:
Timeline
The timeline for this range of WAL records, as an integer.
@@ -19,4 +19,4 @@
upstream promotion, it is possible for multiple ranges to be present, each
with a different timeline. There will never be multiple WAL ranges present
for the same timeline.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/backup.html b/doc/src/sgml/html/backup.html
index 8ee82fe..d804b2e 100644
--- a/doc/src/sgml/html/backup.html
+++ b/doc/src/sgml/html/backup.html
@@ -1,5 +1,5 @@
-Chapter 26. Backup and Restore
As with everything that contains valuable data, PostgreSQL
databases should be backed up regularly. While the procedure is
essentially simple, it is important to have a clear understanding of
@@ -10,4 +10,4 @@
SQL dump
File system level backup
Continuous archiving
Each has its own strengths and weaknesses; each is discussed in turn
in the following sections.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/basebackup-to-shell.html b/doc/src/sgml/html/basebackup-to-shell.html
index 19b4283..36e5371 100644
--- a/doc/src/sgml/html/basebackup-to-shell.html
+++ b/doc/src/sgml/html/basebackup-to-shell.html
@@ -1,5 +1,5 @@
-F.5. basebackup_to_shell
basebackup_to_shell adds a custom basebackup target
called shell. This makes it possible to run
pg_basebackup --target=shell or, depending on how this
@@ -40,4 +40,4 @@
the shell backup target.
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/basic-archive.html b/doc/src/sgml/html/basic-archive.html
index 6baee14..fe292fc 100644
--- a/doc/src/sgml/html/basic-archive.html
+++ b/doc/src/sgml/html/basic-archive.html
@@ -1,5 +1,5 @@
-F.6. basic_archive
basic_archive is an example of an archive module. This
module copies completed WAL segment files to the specified directory. This
may not be especially useful, but it can serve as a starting point for
@@ -35,4 +35,4 @@ basic_archive.archive_directory = '/path/to/archive/directory'
doing so.
F.6.3. Author
Nathan Bossart
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/bgworker.html b/doc/src/sgml/html/bgworker.html
index 75af21c..e1970a0 100644
--- a/doc/src/sgml/html/bgworker.html
+++ b/doc/src/sgml/html/bgworker.html
@@ -1,5 +1,5 @@
-Chapter 48. Background Worker Processes
PostgreSQL can be extended to run user-supplied code in separate processes.
Such processes are started, stopped and monitored by postgres,
which permits them to have a lifetime closely linked to the server's status.
@@ -228,4 +228,4 @@ typedef struct BackgroundWorker
The maximum number of registered background workers is limited by
max_worker_processes.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/biblio.html b/doc/src/sgml/html/biblio.html
index ea909fa..f304677 100644
--- a/doc/src/sgml/html/biblio.html
+++ b/doc/src/sgml/html/biblio.html
@@ -1,5 +1,5 @@
-Bibliography
[ston90a] “The
implementation of POSTGRES”. M.Stonebraker, L. A.Rowe, and M.Hirohama. Transactions on Knowledge and Data Engineering 2(1). IEEE. March 1990.
\ No newline at end of file
+ Rules, Procedures, Caching and Views in Database Systems”. M.Stonebraker, A.Jhingran, J.Goh, and S.Potamianos. ACM-SIGMOD Conference on Management of Data, June 1990.
\ No newline at end of file
diff --git a/doc/src/sgml/html/bki-commands.html b/doc/src/sgml/html/bki-commands.html
index 722bd78..f656a47 100644
--- a/doc/src/sgml/html/bki-commands.html
+++ b/doc/src/sgml/html/bki-commands.html
@@ -1,5 +1,5 @@
-74.4. BKI Commands
createtablenametableoid
@@ -108,4 +108,4 @@
is postponed.
build indices
Fill in the indices that have previously been declared.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/bki-example.html b/doc/src/sgml/html/bki-example.html
index 941ec24..d0af249 100644
--- a/doc/src/sgml/html/bki-example.html
+++ b/doc/src/sgml/html/bki-example.html
@@ -1,5 +1,5 @@
-74.6. BKI Example
The following sequence of commands will create the table
test_table with OID 420, having three columns
oid, cola and colb
@@ -12,4 +12,4 @@ insert ( 421 1 'value 1' )
insert ( 422 2 _null_ )
close test_table
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/bki-format.html b/doc/src/sgml/html/bki-format.html
index 8bf3865..a9d0743 100644
--- a/doc/src/sgml/html/bki-format.html
+++ b/doc/src/sgml/html/bki-format.html
@@ -1,5 +1,5 @@
-74.3. BKI File Format
This section describes how the PostgreSQL
backend interprets BKI files. This description
will be easier to understand if the postgres.bki
@@ -16,4 +16,4 @@
single-quoted strings. Everything is case sensitive.
Lines starting with # are ignored.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/bki-structure.html b/doc/src/sgml/html/bki-structure.html
index 841f335..ebf40f9 100644
--- a/doc/src/sgml/html/bki-structure.html
+++ b/doc/src/sgml/html/bki-structure.html
@@ -1,5 +1,5 @@
-74.5. Structure of the Bootstrap BKI File
The open command cannot be used until the tables it uses
exist and have entries for the table that is to be opened.
(These minimum tables are pg_class,
@@ -39,4 +39,4 @@
There are doubtless other, undocumented ordering dependencies.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/bki.html b/doc/src/sgml/html/bki.html
index b0993ef..5246532 100644
--- a/doc/src/sgml/html/bki.html
+++ b/doc/src/sgml/html/bki.html
@@ -1,5 +1,5 @@
-Chapter 74. System Catalog Declarations and Initial Contents
Chapter 74. System Catalog Declarations and Initial Contents
PostgreSQL uses many different system catalogs
to keep track of the existence and properties of database objects, such as
tables and functions. Physically there is no difference between a system
@@ -53,4 +53,4 @@
and/or initial data files. The rest of this chapter gives some
information about that, and for completeness describes
the BKI file format.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/bloom.html b/doc/src/sgml/html/bloom.html
index 71a879f..ac235f9 100644
--- a/doc/src/sgml/html/bloom.html
+++ b/doc/src/sgml/html/bloom.html
@@ -1,5 +1,5 @@
-F.7. bloom
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/bookindex.html b/doc/src/sgml/html/bookindex.html
index 35d7413..b689aeb 100644
--- a/doc/src/sgml/html/bookindex.html
+++ b/doc/src/sgml/html/bookindex.html
@@ -1,5 +1,5 @@
-Index
The core PostgreSQL distribution
includes the BRIN operator classes shown in
Table 71.1.
@@ -43,4 +43,4 @@
minmax indexes to summarize a block range. Each value may represent
either a point, or a boundary of an interval. Values must be between
8 and 256, and the default value is 32.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/brin-extensibility.html b/doc/src/sgml/html/brin-extensibility.html
index 9ac0995..c54813f 100644
--- a/doc/src/sgml/html/brin-extensibility.html
+++ b/doc/src/sgml/html/brin-extensibility.html
@@ -1,5 +1,5 @@
-71.3. Extensibility
The BRIN interface has a high level of abstraction,
requiring the access method implementer only to implement the semantics
of the data type being accessed. The BRIN layer
@@ -165,4 +165,4 @@ typedef struct BrinOpcInfo
right-hand-side argument of the supported operator. See
float4_minmax_ops as an example of minmax, and
box_inclusion_ops as an example of inclusion.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/brin-intro.html b/doc/src/sgml/html/brin-intro.html
index 2b4a11f..8224322 100644
--- a/doc/src/sgml/html/brin-intro.html
+++ b/doc/src/sgml/html/brin-intro.html
@@ -1,5 +1,5 @@
-71.1. Introduction
BRIN stands for Block Range Index.
BRIN is designed for handling very large tables
in which certain columns have some natural correlation with their
@@ -96,4 +96,4 @@ LOG: request for BRIN range summarization for index "brin_wi_idx" page 128 was
which is useful when the index tuple is no longer a very good
representation because the existing values have changed.
See Section 9.27.8 for details.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/brin.html b/doc/src/sgml/html/brin.html
index d5cd72b..e38c2d6 100644
--- a/doc/src/sgml/html/brin.html
+++ b/doc/src/sgml/html/brin.html
@@ -1,2 +1,2 @@
-Chapter 71. BRIN Indexes
\ No newline at end of file
diff --git a/doc/src/sgml/html/btree-behavior.html b/doc/src/sgml/html/btree-behavior.html
index ae71a0b..444511e 100644
--- a/doc/src/sgml/html/btree-behavior.html
+++ b/doc/src/sgml/html/btree-behavior.html
@@ -1,5 +1,5 @@
-67.2. Behavior of B-Tree Operator Classes
As shown in Table 38.3, a btree operator
class must provide five comparison operators,
<,
@@ -115,4 +115,4 @@
data types. The extensions to three or more data types within a family
are not strictly required by the btree index mechanism itself, but the
planner relies on them for optimization purposes.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/btree-gin.html b/doc/src/sgml/html/btree-gin.html
index 990b8ba..41365cd 100644
--- a/doc/src/sgml/html/btree-gin.html
+++ b/doc/src/sgml/html/btree-gin.html
@@ -1,5 +1,5 @@
-F.8. btree_gin
btree_gin provides sample GIN operator classes that
implement B-tree equivalent behavior for the data types
int2, int4, int8, float4,
@@ -35,4 +35,4 @@ SELECT * FROM test WHERE a < 10;
Oleg Bartunov (<oleg@sai.msu.su>). See
http://www.sai.msu.su/~megera/oddmuse/index.cgi/Gin
for additional information.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/btree-gist.html b/doc/src/sgml/html/btree-gist.html
index c7cf399..b9594cf 100644
--- a/doc/src/sgml/html/btree-gist.html
+++ b/doc/src/sgml/html/btree-gist.html
@@ -1,5 +1,5 @@
-F.9. btree_gist
btree_gist provides GiST index operator classes that
implement B-tree equivalent behavior for the data types
int2, int4, int8, float4,
@@ -77,4 +77,4 @@ INSERT 0 1
Paul Jungwirth (<pj@illuminatedcomputing.com>). See
http://www.sai.msu.su/~megera/postgres/gist/
for additional information.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/btree-implementation.html b/doc/src/sgml/html/btree-implementation.html
index 96eecba..94fcebc 100644
--- a/doc/src/sgml/html/btree-implementation.html
+++ b/doc/src/sgml/html/btree-implementation.html
@@ -1,5 +1,5 @@
-67.4. Implementation
This section covers B-Tree index implementation details that may be
of use to advanced users. See
src/backend/access/nbtree/README in the source
@@ -251,4 +251,4 @@
INCLUDE indexes can never use deduplication.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/btree-intro.html b/doc/src/sgml/html/btree-intro.html
index 4423300..d0f58e5 100644
--- a/doc/src/sgml/html/btree-intro.html
+++ b/doc/src/sgml/html/btree-intro.html
@@ -1,5 +1,5 @@
-67.1. Introduction
PostgreSQL includes an implementation of the
standard btree (multi-way balanced tree) index data
structure. Any data type that can be sorted into a well-defined linear
@@ -14,4 +14,4 @@
some features that go beyond what would be needed just to support btree
indexes, and parts of the system that are quite distant from the
btree AM make use of them.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/btree-support-funcs.html b/doc/src/sgml/html/btree-support-funcs.html
index a9e7cee..97683d0 100644
--- a/doc/src/sgml/html/btree-support-funcs.html
+++ b/doc/src/sgml/html/btree-support-funcs.html
@@ -1,5 +1,5 @@
-67.3. B-Tree Support Functions
As shown in Table 38.9, btree defines
one required and four optional support functions. The five
user-defined methods are:
@@ -288,4 +288,4 @@ options(reloptsloc
access method. Nevertheless, this support function was added to B-tree
for uniformity, and will probably find uses during further
evolution of B-tree in PostgreSQL.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/btree.html b/doc/src/sgml/html/btree.html
index ed4ecbd..36984ab 100644
--- a/doc/src/sgml/html/btree.html
+++ b/doc/src/sgml/html/btree.html
@@ -1,2 +1,2 @@
-Chapter 67. B-Tree Indexes
When you find a bug in PostgreSQL we want to
hear about it. Your bug reports play an important part in making
PostgreSQL more reliable because even the utmost
@@ -154,7 +154,7 @@
subversion the package might have. If you are talking about a Git
snapshot, mention that, including the commit hash.
- If your version is older than 15.6 we will almost certainly
+ If your version is older than 15.7 we will almost certainly
tell you to upgrade. There are many bug fixes and improvements
in each new release, so it is quite possible that a bug you have
encountered in an older release of PostgreSQL
@@ -245,4 +245,4 @@
will be some delay before the email is delivered. If you wish to subscribe
to the lists, please visit
https://lists.postgresql.org/ for instructions.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-aggregate.html b/doc/src/sgml/html/catalog-pg-aggregate.html
index ae4b7cd..27b9f44 100644
--- a/doc/src/sgml/html/catalog-pg-aggregate.html
+++ b/doc/src/sgml/html/catalog-pg-aggregate.html
@@ -1,5 +1,5 @@
-53.2. pg_aggregate
The catalog pg_aggregate stores information about
aggregate functions. An aggregate function is a function that
operates on a set of values (typically one column from each row
@@ -167,4 +167,4 @@
command. See Section 38.12 for more information about
writing aggregate functions and the meaning of the transition
functions, etc.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-am.html b/doc/src/sgml/html/catalog-pg-am.html
index 01b7476..8d4fd00 100644
--- a/doc/src/sgml/html/catalog-pg-am.html
+++ b/doc/src/sgml/html/catalog-pg-am.html
@@ -1,5 +1,5 @@
-53.3. pg_am
The catalog pg_am stores information about
relation access methods. There is one row for each access method supported
by the system.
@@ -41,4 +41,4 @@
However, pg_index_column_has_property() and related
functions have been added to allow SQL queries to inspect index access
method properties; see Table 9.71.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-amop.html b/doc/src/sgml/html/catalog-pg-amop.html
index 0882002..0ff128d 100644
--- a/doc/src/sgml/html/catalog-pg-amop.html
+++ b/doc/src/sgml/html/catalog-pg-amop.html
@@ -1,5 +1,5 @@
-53.4. pg_amop
The catalog pg_amop stores information about
operators associated with access method operator families. There is one
row for each operator that is a member of an operator family. A family
@@ -101,4 +101,4 @@
amoplefttype and amoprighttype must match
the oprleft and oprright fields of the
referenced pg_operator entry.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-amproc.html b/doc/src/sgml/html/catalog-pg-amproc.html
index 7bb2479..e632991 100644
--- a/doc/src/sgml/html/catalog-pg-amproc.html
+++ b/doc/src/sgml/html/catalog-pg-amproc.html
@@ -1,5 +1,5 @@
-53.5. pg_amproc
The catalog pg_amproc stores information about
support functions associated with access method operator families. There
is one row for each support function belonging to an operator family.
@@ -52,4 +52,4 @@
an index, which are those with amproclefttype and
amprocrighttype both equal to the index operator class's
opcintype.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-attrdef.html b/doc/src/sgml/html/catalog-pg-attrdef.html
index 1cea5a6..39e98a2 100644
--- a/doc/src/sgml/html/catalog-pg-attrdef.html
+++ b/doc/src/sgml/html/catalog-pg-attrdef.html
@@ -1,5 +1,5 @@
-53.6. pg_attrdef
The catalog pg_attrdef stores column default
values. The main information about columns is stored in
pg_attribute.
@@ -34,4 +34,4 @@
The column default value, in nodeToString()
representation. Use pg_get_expr(adbin, adrelid) to
convert it to an SQL expression.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-attribute.html b/doc/src/sgml/html/catalog-pg-attribute.html
index fcff141..d9dd627 100644
--- a/doc/src/sgml/html/catalog-pg-attribute.html
+++ b/doc/src/sgml/html/catalog-pg-attribute.html
@@ -1,5 +1,5 @@
-53.7. pg_attribute
The catalog pg_attribute stores information about
table columns. There will be exactly one
pg_attribute row for every column in every
@@ -208,4 +208,4 @@
later dropped, and so there is no pg_type row anymore.
attlen and the other fields can be used
to interpret the contents of a row of the table.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-auth-members.html b/doc/src/sgml/html/catalog-pg-auth-members.html
index 9a3b7b4..aaf7510 100644
--- a/doc/src/sgml/html/catalog-pg-auth-members.html
+++ b/doc/src/sgml/html/catalog-pg-auth-members.html
@@ -1,5 +1,5 @@
-53.9. pg_auth_members
The catalog pg_auth_members shows the membership
relations between roles. Any non-circular set of relationships is allowed.
@@ -37,4 +37,4 @@
True if member can grant membership in
roleid to others
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-authid.html b/doc/src/sgml/html/catalog-pg-authid.html
index 290ef27..889c4be 100644
--- a/doc/src/sgml/html/catalog-pg-authid.html
+++ b/doc/src/sgml/html/catalog-pg-authid.html
@@ -1,5 +1,5 @@
-53.8. pg_authid
The catalog pg_authid contains information about
database authorization identifiers (roles). A role subsumes the concepts
of “users” and “groups”. A user is essentially just a
@@ -106,8 +106,8 @@ SCRAM-SHA-256$<iteration count>:
where salt, StoredKey and
ServerKey are in Base64 encoded format. This format is
- the same as that specified by RFC 5803.
+ the same as that specified by RFC 5803.
A password that does not follow either of those formats is assumed to be
unencrypted.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-cast.html b/doc/src/sgml/html/catalog-pg-cast.html
index 116d34c..91a95bd 100644
--- a/doc/src/sgml/html/catalog-pg-cast.html
+++ b/doc/src/sgml/html/catalog-pg-cast.html
@@ -1,5 +1,5 @@
-53.10. pg_cast
The catalog pg_cast stores data type conversion
paths, both built-in and user-defined.
@@ -83,4 +83,4 @@
coercion in a single step. When no such entry is available, coercion
to a type that uses a type modifier involves two steps, one to
convert between data types and a second to apply the modifier.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-class.html b/doc/src/sgml/html/catalog-pg-class.html
index 620aef8..4878739 100644
--- a/doc/src/sgml/html/catalog-pg-class.html
+++ b/doc/src/sgml/html/catalog-pg-class.html
@@ -1,5 +1,5 @@
-53.11. pg_class
The catalog pg_class describes tables and
other objects that have columns or are otherwise similar to a
table. This includes indexes (but see also pg_index),
@@ -71,9 +71,12 @@
(references pg_tablespace.oid)
- The tablespace in which this relation is stored. If zero,
- the database's default tablespace is implied. (Not meaningful
- if the relation has no on-disk file.)
+ The tablespace in which this relation is stored.
+ If zero, the database's default tablespace is implied.
+ Not meaningful if the relation has no on-disk file,
+ except for partitioned tables, where this is the tablespace
+ in which partitions will be created when one is not
+ specified in the creation command.
relpagesint4
@@ -261,4 +264,4 @@
DROP INDEX. Instead, VACUUM clears
relhasindex if it finds the table has no indexes. This
arrangement avoids race conditions and improves concurrency.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-collation.html b/doc/src/sgml/html/catalog-pg-collation.html
index e8223d6..c8df7eb 100644
--- a/doc/src/sgml/html/catalog-pg-collation.html
+++ b/doc/src/sgml/html/catalog-pg-collation.html
@@ -1,5 +1,5 @@
-53.12. pg_collation
The catalog pg_collation describes the
available collations, which are essentially mappings from an SQL
name to operating system locale categories.
@@ -90,4 +90,4 @@
collations whose encoding does not match the database encoding,
since they could match the encodings of databases later cloned from
template0. This would currently have to be done manually.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-constraint.html b/doc/src/sgml/html/catalog-pg-constraint.html
index f7ec105..efe02d0 100644
--- a/doc/src/sgml/html/catalog-pg-constraint.html
+++ b/doc/src/sgml/html/catalog-pg-constraint.html
@@ -1,5 +1,5 @@
-53.13. pg_constraint
The catalog pg_constraint stores check, primary
key, unique, foreign key, and exclusion constraints on tables.
(Column constraints are not treated specially. Every column constraint is
@@ -203,4 +203,4 @@
pg_class.relchecks needs to agree with the
number of check-constraint entries found in this table for each
relation.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-conversion.html b/doc/src/sgml/html/catalog-pg-conversion.html
index 525043c..f095538 100644
--- a/doc/src/sgml/html/catalog-pg-conversion.html
+++ b/doc/src/sgml/html/catalog-pg-conversion.html
@@ -1,5 +1,5 @@
-53.14. pg_conversion
The catalog pg_conversion describes
encoding conversion functions. See CREATE CONVERSION
for more information.
@@ -53,4 +53,4 @@
True if this is the default conversion
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-database.html b/doc/src/sgml/html/catalog-pg-database.html
index 3e34e04..6d50758 100644
--- a/doc/src/sgml/html/catalog-pg-database.html
+++ b/doc/src/sgml/html/catalog-pg-database.html
@@ -1,5 +1,5 @@
-53.15. pg_database
The catalog pg_database stores information about
the available databases. Databases are created with the CREATE DATABASE command.
Consult Chapter 23 for details about the meaning
@@ -121,4 +121,4 @@
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-db-role-setting.html b/doc/src/sgml/html/catalog-pg-db-role-setting.html
index 441b48f..f6cfd2d 100644
--- a/doc/src/sgml/html/catalog-pg-db-role-setting.html
+++ b/doc/src/sgml/html/catalog-pg-db-role-setting.html
@@ -1,5 +1,5 @@
-53.16. pg_db_role_setting
The catalog pg_db_role_setting records the default
values that have been set for run-time configuration variables,
for each role and database combination.
@@ -30,4 +30,4 @@
Defaults for run-time configuration variables
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-default-acl.html b/doc/src/sgml/html/catalog-pg-default-acl.html
index 28f972a..5ac2d99 100644
--- a/doc/src/sgml/html/catalog-pg-default-acl.html
+++ b/doc/src/sgml/html/catalog-pg-default-acl.html
@@ -1,5 +1,5 @@
-53.17. pg_default_acl
The catalog pg_default_acl stores initial
privileges to be assigned to newly created objects.
Table 53.17. pg_default_acl Columns
@@ -55,4 +55,4 @@
not whatever might be in pg_default_acl
at the moment. pg_default_acl is only consulted during
object creation.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-depend.html b/doc/src/sgml/html/catalog-pg-depend.html
index e0cdc38..efca8c9 100644
--- a/doc/src/sgml/html/catalog-pg-depend.html
+++ b/doc/src/sgml/html/catalog-pg-depend.html
@@ -1,5 +1,5 @@
-53.18. pg_depend
The catalog pg_depend records the dependency
relationships between database objects. This information allows
DROP commands to find which other objects must be dropped
@@ -172,4 +172,4 @@
a NORMAL dependency on the numeric
data type, but no such entry actually appears
in pg_depend.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-description.html b/doc/src/sgml/html/catalog-pg-description.html
index 585a597..5e2ac3b 100644
--- a/doc/src/sgml/html/catalog-pg-description.html
+++ b/doc/src/sgml/html/catalog-pg-description.html
@@ -1,5 +1,5 @@
-53.19. pg_description
The catalog pg_description stores optional descriptions
(comments) for each database object. Descriptions can be manipulated
with the COMMENT command and viewed with
@@ -40,4 +40,4 @@
Arbitrary text that serves as the description of this object
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-enum.html b/doc/src/sgml/html/catalog-pg-enum.html
index 812c987..e8d3ccb 100644
--- a/doc/src/sgml/html/catalog-pg-enum.html
+++ b/doc/src/sgml/html/catalog-pg-enum.html
@@ -1,5 +1,5 @@
-53.20. pg_enum
The pg_enum catalog contains entries
showing the values and labels for each enum type. The
internal representation of a given enum value is actually the OID
@@ -46,4 +46,4 @@
negative or fractional values of enumsortorder.
The only requirement on these values is that they be correctly
ordered and unique within each enum type.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-event-trigger.html b/doc/src/sgml/html/catalog-pg-event-trigger.html
index 495f0b4..d4a132d 100644
--- a/doc/src/sgml/html/catalog-pg-event-trigger.html
+++ b/doc/src/sgml/html/catalog-pg-event-trigger.html
@@ -1,5 +1,5 @@
-53.21. pg_event_trigger
The catalog pg_event_trigger stores event triggers.
See Chapter 40 for more information.
Table 53.21. pg_event_trigger Columns
@@ -50,4 +50,4 @@
Command tags for which this trigger will fire. If NULL, the firing
of this trigger is not restricted on the basis of the command tag.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-extension.html b/doc/src/sgml/html/catalog-pg-extension.html
index 4013e76..c8b505a 100644
--- a/doc/src/sgml/html/catalog-pg-extension.html
+++ b/doc/src/sgml/html/catalog-pg-extension.html
@@ -1,5 +1,5 @@
-53.22. pg_extension
The catalog pg_extension stores information
about the installed extensions. See Section 38.17
for details about extensions.
@@ -62,4 +62,4 @@
objects. If extrelocatable is true, then
this schema must in fact contain all schema-qualifiable objects
belonging to the extension.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-foreign-data-wrapper.html b/doc/src/sgml/html/catalog-pg-foreign-data-wrapper.html
index 565a6d8..3ac3d03 100644
--- a/doc/src/sgml/html/catalog-pg-foreign-data-wrapper.html
+++ b/doc/src/sgml/html/catalog-pg-foreign-data-wrapper.html
@@ -1,5 +1,5 @@
-53.23. pg_foreign_data_wrapper
The catalog pg_foreign_data_wrapper stores
foreign-data wrapper definitions. A foreign-data wrapper is the
mechanism by which external data, residing on foreign servers, is
@@ -53,4 +53,4 @@
Foreign-data wrapper specific options, as “keyword=value” strings
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-foreign-server.html b/doc/src/sgml/html/catalog-pg-foreign-server.html
index f094cca..021c720 100644
--- a/doc/src/sgml/html/catalog-pg-foreign-server.html
+++ b/doc/src/sgml/html/catalog-pg-foreign-server.html
@@ -1,5 +1,5 @@
-53.24. pg_foreign_server
The catalog pg_foreign_server stores
foreign server definitions. A foreign server describes a source
of external data, such as a remote server. Foreign
@@ -51,4 +51,4 @@
Foreign server specific options, as “keyword=value” strings
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-foreign-table.html b/doc/src/sgml/html/catalog-pg-foreign-table.html
index 7bd5b93..9cb8f5a 100644
--- a/doc/src/sgml/html/catalog-pg-foreign-table.html
+++ b/doc/src/sgml/html/catalog-pg-foreign-table.html
@@ -1,5 +1,5 @@
-53.25. pg_foreign_table
The catalog pg_foreign_table contains
auxiliary information about foreign tables. A foreign table is
primarily represented by a
@@ -29,4 +29,4 @@
Foreign table options, as “keyword=value” strings
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-index.html b/doc/src/sgml/html/catalog-pg-index.html
index 083c36e..d209100 100644
--- a/doc/src/sgml/html/catalog-pg-index.html
+++ b/doc/src/sgml/html/catalog-pg-index.html
@@ -1,5 +1,5 @@
-53.26. pg_index
The catalog pg_index contains part of the information
about indexes. The rest is mostly in
pg_class.
@@ -160,4 +160,4 @@
Expression tree (in nodeToString()
representation) for partial index predicate. Null if not a
partial index.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-inherits.html b/doc/src/sgml/html/catalog-pg-inherits.html
index 545beb9..5fd12b7 100644
--- a/doc/src/sgml/html/catalog-pg-inherits.html
+++ b/doc/src/sgml/html/catalog-pg-inherits.html
@@ -1,5 +1,5 @@
-53.27. pg_inherits
The catalog pg_inherits records information about
table and index inheritance hierarchies. There is one entry for each direct
parent-child table or index relationship in the database. (Indirect
@@ -38,4 +38,4 @@
true for a partition that is in the process of
being detached; false otherwise.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-init-privs.html b/doc/src/sgml/html/catalog-pg-init-privs.html
index af3c4ac..39ebd5a 100644
--- a/doc/src/sgml/html/catalog-pg-init-privs.html
+++ b/doc/src/sgml/html/catalog-pg-init-privs.html
@@ -1,5 +1,5 @@
-53.28. pg_init_privs
The catalog pg_init_privs records information about
the initial privileges of objects in the system. There is one entry
for each object in the database which has a non-default (non-NULL)
@@ -58,4 +58,4 @@
The initial access privileges; see
Section 5.7 for details
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-language.html b/doc/src/sgml/html/catalog-pg-language.html
index b527065..6980056 100644
--- a/doc/src/sgml/html/catalog-pg-language.html
+++ b/doc/src/sgml/html/catalog-pg-language.html
@@ -1,5 +1,5 @@
-53.29. pg_language
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-largeobject-metadata.html b/doc/src/sgml/html/catalog-pg-largeobject-metadata.html
index 61a1dbf..11f96e0 100644
--- a/doc/src/sgml/html/catalog-pg-largeobject-metadata.html
+++ b/doc/src/sgml/html/catalog-pg-largeobject-metadata.html
@@ -1,5 +1,5 @@
-53.31. pg_largeobject_metadata
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-largeobject.html b/doc/src/sgml/html/catalog-pg-largeobject.html
index ae4ffe8..6605b61 100644
--- a/doc/src/sgml/html/catalog-pg-largeobject.html
+++ b/doc/src/sgml/html/catalog-pg-largeobject.html
@@ -1,5 +1,5 @@
-53.30. pg_largeobject
The catalog pg_largeobject holds the data making up
“large objects”. A large object is identified by an OID
assigned when it is created. Each large object is broken into
@@ -45,4 +45,4 @@
allows sparse storage: pages might be missing, and might be shorter than
LOBLKSIZE bytes even if they are not the last page of the object.
Missing regions within a large object read as zeroes.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-namespace.html b/doc/src/sgml/html/catalog-pg-namespace.html
index 5fd2aff..66d0561 100644
--- a/doc/src/sgml/html/catalog-pg-namespace.html
+++ b/doc/src/sgml/html/catalog-pg-namespace.html
@@ -1,5 +1,5 @@
-53.32. pg_namespace
The catalog pg_namespace stores namespaces.
A namespace is the structure underlying SQL schemas: each namespace
can have a separate collection of relations, types, etc. without name
@@ -30,4 +30,4 @@
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-opclass.html b/doc/src/sgml/html/catalog-pg-opclass.html
index 6909f84..391bd43 100644
--- a/doc/src/sgml/html/catalog-pg-opclass.html
+++ b/doc/src/sgml/html/catalog-pg-opclass.html
@@ -1,5 +1,5 @@
-53.33. pg_opclass
The catalog pg_opclass defines
index access method operator classes. Each operator class defines
semantics for index columns of a particular data type and a particular
@@ -72,4 +72,4 @@
Also, there must be no more than one pg_opclass
row having opcdefault true for any given combination of
opcmethod and opcintype.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-operator.html b/doc/src/sgml/html/catalog-pg-operator.html
index face19d..4fdabf9 100644
--- a/doc/src/sgml/html/catalog-pg-operator.html
+++ b/doc/src/sgml/html/catalog-pg-operator.html
@@ -1,5 +1,5 @@
-53.34. pg_operator
The catalog pg_operator stores information about operators.
See CREATE OPERATOR
and Section 38.14 for more information.
@@ -98,4 +98,4 @@
Join selectivity estimation function for this operator
(zero if none)
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-opfamily.html b/doc/src/sgml/html/catalog-pg-opfamily.html
index a29f068..040d482 100644
--- a/doc/src/sgml/html/catalog-pg-opfamily.html
+++ b/doc/src/sgml/html/catalog-pg-opfamily.html
@@ -1,5 +1,5 @@
-53.35. pg_opfamily
The catalog pg_opfamily defines operator families.
Each operator family is a collection of operators and associated
support routines that implement the semantics specified for a particular
@@ -50,4 +50,4 @@
pg_amproc,
and
pg_opclass.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-parameter-acl.html b/doc/src/sgml/html/catalog-pg-parameter-acl.html
index 79fdf07..0cb36d6 100644
--- a/doc/src/sgml/html/catalog-pg-parameter-acl.html
+++ b/doc/src/sgml/html/catalog-pg-parameter-acl.html
@@ -1,5 +1,5 @@
-53.36. pg_parameter_acl
The catalog pg_parameter_acl records configuration
parameters for which privileges have been granted to one or more roles.
No entry is made for parameters that have default privileges.
@@ -28,4 +28,4 @@
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-partitioned-table.html b/doc/src/sgml/html/catalog-pg-partitioned-table.html
index 0ef28a2..530eab6 100644
--- a/doc/src/sgml/html/catalog-pg-partitioned-table.html
+++ b/doc/src/sgml/html/catalog-pg-partitioned-table.html
@@ -1,5 +1,5 @@
-53.37. pg_partitioned_table
The catalog pg_partitioned_table stores
information about how tables are partitioned.
Table 53.37. pg_partitioned_table Columns
@@ -68,4 +68,4 @@
references. This is a list with one element for each zero
entry in partattrs. Null if all partition key columns
are simple references.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-policy.html b/doc/src/sgml/html/catalog-pg-policy.html
index bab4e6f..c581074 100644
--- a/doc/src/sgml/html/catalog-pg-policy.html
+++ b/doc/src/sgml/html/catalog-pg-policy.html
@@ -1,5 +1,5 @@
-53.38. pg_policy
The catalog pg_policy stores row-level
security policies for tables. A policy includes the kind of
command that it applies to (possibly all commands), the roles that it
@@ -65,4 +65,4 @@
Policies stored in pg_policy are applied only when
pg_class.relrowsecurity is set for
their table.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-proc.html b/doc/src/sgml/html/catalog-pg-proc.html
index 8783850..148e401 100644
--- a/doc/src/sgml/html/catalog-pg-proc.html
+++ b/doc/src/sgml/html/catalog-pg-proc.html
@@ -1,5 +1,5 @@
-53.39. pg_proc
The catalog pg_proc stores information about
functions, procedures, aggregate functions, and window functions
(collectively also known as routines). See CREATE FUNCTION, CREATE PROCEDURE, and
@@ -253,4 +253,4 @@
text. probin is null except for
dynamically-loaded C functions, for which it gives the name of the
shared library file containing the function.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-publication-namespace.html b/doc/src/sgml/html/catalog-pg-publication-namespace.html
index 8d19494..cdd5a4c 100644
--- a/doc/src/sgml/html/catalog-pg-publication-namespace.html
+++ b/doc/src/sgml/html/catalog-pg-publication-namespace.html
@@ -1,5 +1,5 @@
-53.41. pg_publication_namespace
The catalog pg_publication_namespace contains the
mapping between schemas and publications in the database. This is a
many-to-many mapping.
@@ -25,4 +25,4 @@
Reference to schema
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-publication-rel.html b/doc/src/sgml/html/catalog-pg-publication-rel.html
index c81398b..2825411 100644
--- a/doc/src/sgml/html/catalog-pg-publication-rel.html
+++ b/doc/src/sgml/html/catalog-pg-publication-rel.html
@@ -1,5 +1,5 @@
-53.42. pg_publication_rel
The catalog pg_publication_rel contains the
mapping between relations and publications in the database. This is a
many-to-many mapping. See also Section 54.17
@@ -40,4 +40,4 @@
part of the publication. For example, a value of 1 3
would mean that the first and the third table columns are published.
A null value indicates that all columns are published.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-publication.html b/doc/src/sgml/html/catalog-pg-publication.html
index 75a04f3..9a172f6 100644
--- a/doc/src/sgml/html/catalog-pg-publication.html
+++ b/doc/src/sgml/html/catalog-pg-publication.html
@@ -1,5 +1,5 @@
-53.40. pg_publication
The catalog pg_publication contains all
publications created in the database. For more on publications see
Section 31.1.
@@ -61,4 +61,4 @@
If true, operations on a leaf partition are replicated using the
identity and schema of its topmost partitioned ancestor mentioned in the
publication instead of its own.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-range.html b/doc/src/sgml/html/catalog-pg-range.html
index df9bfe5..211fee7 100644
--- a/doc/src/sgml/html/catalog-pg-range.html
+++ b/doc/src/sgml/html/catalog-pg-range.html
@@ -1,5 +1,5 @@
-53.43. pg_range
The catalog pg_range stores information about
range types. This is in addition to the types' entries in
pg_type.
@@ -58,4 +58,4 @@
type. rngcanonical is used when the element type is
discrete. rngsubdiff is optional but should be supplied to
improve performance of GiST indexes on the range type.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-replication-origin.html b/doc/src/sgml/html/catalog-pg-replication-origin.html
index 299e305..0e73b8a 100644
--- a/doc/src/sgml/html/catalog-pg-replication-origin.html
+++ b/doc/src/sgml/html/catalog-pg-replication-origin.html
@@ -1,5 +1,5 @@
-53.44. pg_replication_origin
The pg_replication_origin catalog contains
all replication origins created. For more on replication origins
see Chapter 50.
@@ -25,4 +25,4 @@
The external, user defined, name of a replication
origin.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-rewrite.html b/doc/src/sgml/html/catalog-pg-rewrite.html
index 7c9f11d..a924511 100644
--- a/doc/src/sgml/html/catalog-pg-rewrite.html
+++ b/doc/src/sgml/html/catalog-pg-rewrite.html
@@ -1,5 +1,5 @@
-53.45. pg_rewrite
The catalog pg_rewrite stores rewrite rules for tables and views.
Table 53.45. pg_rewrite Columns
Column Type
@@ -61,4 +61,4 @@
Note
pg_class.relhasrules
must be true if a table has any rules in this catalog.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-seclabel.html b/doc/src/sgml/html/catalog-pg-seclabel.html
index a6dd2a3..6e9427a 100644
--- a/doc/src/sgml/html/catalog-pg-seclabel.html
+++ b/doc/src/sgml/html/catalog-pg-seclabel.html
@@ -1,5 +1,5 @@
-53.46. pg_seclabel
The catalog pg_seclabel stores security
labels on database objects. Security labels can be manipulated
with the SECURITY LABEL command. For an easier
@@ -43,4 +43,4 @@
The security label applied to this object.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-sequence.html b/doc/src/sgml/html/catalog-pg-sequence.html
index 8b4a76a..1ae419a 100644
--- a/doc/src/sgml/html/catalog-pg-sequence.html
+++ b/doc/src/sgml/html/catalog-pg-sequence.html
@@ -1,5 +1,5 @@
-53.47. pg_sequence
The catalog pg_sequence contains information about
sequences. Some of the information about sequences, such as the name and
the schema, is in
@@ -51,4 +51,4 @@
Whether the sequence cycles
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-shdepend.html b/doc/src/sgml/html/catalog-pg-shdepend.html
index a3aaef0..dfcc5f9 100644
--- a/doc/src/sgml/html/catalog-pg-shdepend.html
+++ b/doc/src/sgml/html/catalog-pg-shdepend.html
@@ -1,5 +1,5 @@
-53.48. pg_shdepend
The catalog pg_shdepend records the
dependency relationships between database objects and shared objects,
such as roles. This information allows
@@ -95,4 +95,4 @@
considered “pinned”. No entries are made
in pg_shdepend that would have a pinned
object as either referenced or dependent object.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-shdescription.html b/doc/src/sgml/html/catalog-pg-shdescription.html
index 54d9e48..6b5e861 100644
--- a/doc/src/sgml/html/catalog-pg-shdescription.html
+++ b/doc/src/sgml/html/catalog-pg-shdescription.html
@@ -1,5 +1,5 @@
-53.49. pg_shdescription
The catalog pg_shdescription stores optional
descriptions (comments) for shared database objects. Descriptions can be
manipulated with the COMMENT command and viewed with
@@ -35,4 +35,4 @@
Arbitrary text that serves as the description of this object
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-shseclabel.html b/doc/src/sgml/html/catalog-pg-shseclabel.html
index 52d91ee..2975e55 100644
--- a/doc/src/sgml/html/catalog-pg-shseclabel.html
+++ b/doc/src/sgml/html/catalog-pg-shseclabel.html
@@ -1,5 +1,5 @@
-53.50. pg_shseclabel
The catalog pg_shseclabel stores security
labels on shared database objects. Security labels can be manipulated
with the SECURITY LABEL command. For an easier
@@ -40,4 +40,4 @@
The security label applied to this object.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-statistic-ext-data.html b/doc/src/sgml/html/catalog-pg-statistic-ext-data.html
index 5860d87..f2986ec 100644
--- a/doc/src/sgml/html/catalog-pg-statistic-ext-data.html
+++ b/doc/src/sgml/html/catalog-pg-statistic-ext-data.html
@@ -1,5 +1,5 @@
-53.53. pg_statistic_ext_data
The catalog pg_statistic_ext_data
holds data for extended planner statistics defined in
pg_statistic_ext.
@@ -26,8 +26,7 @@
is a publicly readable view
on pg_statistic_ext_data (after joining
with pg_statistic_ext) that only exposes
- information about those tables and columns that are readable by the
- current user.
+ information about tables the current user owns.
Table 53.53. pg_statistic_ext_data Columns
Column Type
@@ -68,4 +67,4 @@
Per-expression statistics, serialized as an array of
pg_statistic type
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-statistic-ext.html b/doc/src/sgml/html/catalog-pg-statistic-ext.html
index 5123439..2f68a04 100644
--- a/doc/src/sgml/html/catalog-pg-statistic-ext.html
+++ b/doc/src/sgml/html/catalog-pg-statistic-ext.html
@@ -1,5 +1,5 @@
-53.52. pg_statistic_ext
The catalog pg_statistic_ext
holds definitions of extended planner statistics.
Each row in this catalog corresponds to a statistics object
@@ -85,4 +85,4 @@
and populate an entry in the
pg_statistic_ext_data
catalog.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-statistic.html b/doc/src/sgml/html/catalog-pg-statistic.html
index cb4bca1..9465583 100644
--- a/doc/src/sgml/html/catalog-pg-statistic.html
+++ b/doc/src/sgml/html/catalog-pg-statistic.html
@@ -1,5 +1,5 @@
-53.51. pg_statistic
The catalog pg_statistic stores
statistical data about the contents of the database. Entries are
created by ANALYZE
@@ -131,4 +131,4 @@
values are actually of the specific column's data type, or a related
type such as an array's element type, so there is no way to define
these columns' type more specifically than anyarray.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-subscription-rel.html b/doc/src/sgml/html/catalog-pg-subscription-rel.html
index b84860d..58e361c 100644
--- a/doc/src/sgml/html/catalog-pg-subscription-rel.html
+++ b/doc/src/sgml/html/catalog-pg-subscription-rel.html
@@ -1,5 +1,5 @@
-53.55. pg_subscription_rel
The catalog pg_subscription_rel contains the
state for each replicated relation in each subscription. This is a
many-to-many mapping.
@@ -42,4 +42,4 @@
Remote LSN of the state change used for synchronization coordination
when in s or r states,
otherwise null
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-subscription.html b/doc/src/sgml/html/catalog-pg-subscription.html
index 057f1ab..462459b 100644
--- a/doc/src/sgml/html/catalog-pg-subscription.html
+++ b/doc/src/sgml/html/catalog-pg-subscription.html
@@ -1,5 +1,5 @@
-53.54. pg_subscription
The catalog pg_subscription contains all existing
logical replication subscriptions. For more information about logical
replication see Chapter 31.
@@ -100,4 +100,4 @@
Array of subscribed publication names. These reference
publications defined in the upstream database. For more on publications
see Section 31.1.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-tablespace.html b/doc/src/sgml/html/catalog-pg-tablespace.html
index 5bdec93..bab3e3c 100644
--- a/doc/src/sgml/html/catalog-pg-tablespace.html
+++ b/doc/src/sgml/html/catalog-pg-tablespace.html
@@ -1,5 +1,5 @@
-53.56. pg_tablespace
The catalog pg_tablespace stores information
about the available tablespaces. Tables can be placed in particular
tablespaces to aid administration of disk layout.
@@ -39,4 +39,4 @@
Tablespace-level options, as “keyword=value” strings
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-transform.html b/doc/src/sgml/html/catalog-pg-transform.html
index d7169e9..cf909e1 100644
--- a/doc/src/sgml/html/catalog-pg-transform.html
+++ b/doc/src/sgml/html/catalog-pg-transform.html
@@ -1,5 +1,5 @@
-53.57. pg_transform
The catalog pg_transform stores information about
transforms, which are a mechanism to adapt data types to procedural
languages. See CREATE TRANSFORM for more information.
@@ -41,4 +41,4 @@
The OID of the function to use when converting output from the
procedural language (e.g., return values) to the data type. Zero is
stored if the default behavior should be used.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-trigger.html b/doc/src/sgml/html/catalog-pg-trigger.html
index ce4212d..e746521 100644
--- a/doc/src/sgml/html/catalog-pg-trigger.html
+++ b/doc/src/sgml/html/catalog-pg-trigger.html
@@ -1,5 +1,5 @@
-53.58. pg_trigger
The catalog pg_trigger stores triggers on tables
and views.
See CREATE TRIGGER
@@ -145,4 +145,4 @@
Note
pg_class.relhastriggers
must be true if a relation has any triggers in this catalog.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-ts-config-map.html b/doc/src/sgml/html/catalog-pg-ts-config-map.html
index 9e7d34f..f1587c6 100644
--- a/doc/src/sgml/html/catalog-pg-ts-config-map.html
+++ b/doc/src/sgml/html/catalog-pg-ts-config-map.html
@@ -1,5 +1,5 @@
-53.60. pg_ts_config_map
The pg_ts_config_map catalog contains entries
showing which text search dictionaries should be consulted, and in
what order, for each output token type of each text search configuration's
@@ -35,4 +35,4 @@
The OID of the text search dictionary to consult
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-ts-config.html b/doc/src/sgml/html/catalog-pg-ts-config.html
index 17d31f6..e66b27c 100644
--- a/doc/src/sgml/html/catalog-pg-ts-config.html
+++ b/doc/src/sgml/html/catalog-pg-ts-config.html
@@ -1,5 +1,5 @@
-53.59. pg_ts_config
The pg_ts_config catalog contains entries
representing text search configurations. A configuration specifies
a particular text search parser and a list of dictionaries to use
@@ -42,4 +42,4 @@
The OID of the text search parser for this configuration
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-ts-dict.html b/doc/src/sgml/html/catalog-pg-ts-dict.html
index 703fdc7..fc5d0fb 100644
--- a/doc/src/sgml/html/catalog-pg-ts-dict.html
+++ b/doc/src/sgml/html/catalog-pg-ts-dict.html
@@ -1,5 +1,5 @@
-53.61. pg_ts_dict
The pg_ts_dict catalog contains entries
defining text search dictionaries. A dictionary depends on a text
search template, which specifies all the implementation functions
@@ -49,4 +49,4 @@
Initialization option string for the template
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-ts-parser.html b/doc/src/sgml/html/catalog-pg-ts-parser.html
index 1342510..47e8fb3 100644
--- a/doc/src/sgml/html/catalog-pg-ts-parser.html
+++ b/doc/src/sgml/html/catalog-pg-ts-parser.html
@@ -1,5 +1,5 @@
-53.62. pg_ts_parser
The pg_ts_parser catalog contains entries
defining text search parsers. A parser is responsible for splitting
input text into lexemes and assigning a token type to each lexeme.
@@ -59,4 +59,4 @@
OID of the parser's lextype function
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-ts-template.html b/doc/src/sgml/html/catalog-pg-ts-template.html
index 4b794b9..8eca6f6 100644
--- a/doc/src/sgml/html/catalog-pg-ts-template.html
+++ b/doc/src/sgml/html/catalog-pg-ts-template.html
@@ -1,5 +1,5 @@
-53.63. pg_ts_template
The pg_ts_template catalog contains entries
defining text search templates. A template is the implementation
skeleton for a class of text search dictionaries.
@@ -41,4 +41,4 @@
OID of the template's lexize function
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-type.html b/doc/src/sgml/html/catalog-pg-type.html
index 6361d4a..a0b5be9 100644
--- a/doc/src/sgml/html/catalog-pg-type.html
+++ b/doc/src/sgml/html/catalog-pg-type.html
@@ -1,5 +1,5 @@
-53.64. pg_type
The catalog pg_type stores information about data
types. Base types and enum types (scalar types) are created with
CREATE TYPE, and
@@ -307,4 +307,4 @@
of typcategory. Any future additions to this list will
also be upper-case ASCII letters. All other ASCII characters are reserved
for user-defined categories.
-
Table 53.65. typcategory Codes
Code
Category
A
Array types
B
Boolean types
C
Composite types
D
Date/time types
E
Enum types
G
Geometric types
I
Network address types
N
Numeric types
P
Pseudo-types
R
Range types
S
String types
T
Timespan types
U
User-defined types
V
Bit-string types
X
unknown type
Z
Internal-use types
\ No newline at end of file
+
Table 53.65. typcategory Codes
Code
Category
A
Array types
B
Boolean types
C
Composite types
D
Date/time types
E
Enum types
G
Geometric types
I
Network address types
N
Numeric types
P
Pseudo-types
R
Range types
S
String types
T
Timespan types
U
User-defined types
V
Bit-string types
X
unknown type
Z
Internal-use types
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalog-pg-user-mapping.html b/doc/src/sgml/html/catalog-pg-user-mapping.html
index ec8887f..000f754 100644
--- a/doc/src/sgml/html/catalog-pg-user-mapping.html
+++ b/doc/src/sgml/html/catalog-pg-user-mapping.html
@@ -1,5 +1,5 @@
-53.65. pg_user_mapping
The catalog pg_user_mapping stores
the mappings from local user to remote. Access to this catalog is
restricted from normal users, use the view
@@ -32,4 +32,4 @@
User mapping specific options, as “keyword=value” strings
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalogs-overview.html b/doc/src/sgml/html/catalogs-overview.html
index 41ac125..2ffbe76 100644
--- a/doc/src/sgml/html/catalogs-overview.html
+++ b/doc/src/sgml/html/catalogs-overview.html
@@ -1,5 +1,5 @@
-53.1. Overview
Table 53.1 lists the system catalogs.
More detailed documentation of each catalog follows below.
@@ -7,4 +7,4 @@
database creation and are thereafter database-specific. A few
catalogs are physically shared across all databases in a cluster;
these are noted in the descriptions of the individual catalogs.
-
\ No newline at end of file
diff --git a/doc/src/sgml/html/catalogs.html b/doc/src/sgml/html/catalogs.html
index 61c0135..5c06bc4 100644
--- a/doc/src/sgml/html/catalogs.html
+++ b/doc/src/sgml/html/catalogs.html
@@ -1,5 +1,5 @@
-Chapter 53. System Catalogs
The system catalogs are the place where a relational database
management system stores schema metadata, such as information about
tables and columns, and internal bookkeeping information.
@@ -14,4 +14,4 @@
particularly esoteric operations, but many of those have been made
available as SQL commands over time, and so the need for direct manipulation
of the system catalogs is ever decreasing.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/charset.html b/doc/src/sgml/html/charset.html
index b236814..fe72057 100644
--- a/doc/src/sgml/html/charset.html
+++ b/doc/src/sgml/html/charset.html
@@ -1,5 +1,5 @@
-Chapter 24. Localization
This chapter describes the available localization features from the
point of view of the administrator.
PostgreSQL supports two localization
@@ -17,4 +17,4 @@
between client and server.
This is covered in Section 24.3.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/checksums.html b/doc/src/sgml/html/checksums.html
index 3b93b09..1ae7d9f 100644
--- a/doc/src/sgml/html/checksums.html
+++ b/doc/src/sgml/html/checksums.html
@@ -1,5 +1,5 @@
-30.2. Data Checksums
By default, data pages are not protected by checksums, but this can
optionally be enabled for a cluster. When enabled, each data page includes
a checksum that is updated when the page is written and verified each time
@@ -22,4 +22,4 @@
The pg_checksums
application can be used to enable or disable data checksums, as well as
verify checksums, on an offline cluster.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/citext.html b/doc/src/sgml/html/citext.html
index 40ec3aa..4932acd 100644
--- a/doc/src/sgml/html/citext.html
+++ b/doc/src/sgml/html/citext.html
@@ -1,5 +1,5 @@
-F.10. citext
The citext module provides a case-insensitive
character string type, citext. Essentially, it internally calls
lower when comparing values. Otherwise, it behaves almost
@@ -163,4 +163,4 @@ SELECT * FROM users WHERE nick = 'Larry';
David E. Wheeler <david@kineticode.com>
Inspired by the original citext module by Donald Fraser.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/client-authentication-problems.html b/doc/src/sgml/html/client-authentication-problems.html
index f17bfed..a08ec91 100644
--- a/doc/src/sgml/html/client-authentication-problems.html
+++ b/doc/src/sgml/html/client-authentication-problems.html
@@ -1,5 +1,5 @@
-21.15. Authentication Problems
Authentication failures and related problems generally
manifest themselves through error messages like the following:
@@ -37,4 +37,4 @@ FATAL: database "testdb" does not exist
The server log might contain more information about an
authentication failure than is reported to the client. If you are
confused about the reason for a failure, check the server log.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/client-authentication.html b/doc/src/sgml/html/client-authentication.html
index 685d3d2..7be9280 100644
--- a/doc/src/sgml/html/client-authentication.html
+++ b/doc/src/sgml/html/client-authentication.html
@@ -1,5 +1,5 @@
-Chapter 21. Client Authentication
When a client application connects to the database server, it
specifies which PostgreSQL database user name it
wants to connect as, much the same way one logs into a Unix computer
@@ -34,4 +34,4 @@
operating system
account, and in such cases there need be no connection between
database user names and OS user names.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/client-interfaces.html b/doc/src/sgml/html/client-interfaces.html
index 1ce7191..8b032dd 100644
--- a/doc/src/sgml/html/client-interfaces.html
+++ b/doc/src/sgml/html/client-interfaces.html
@@ -1,5 +1,5 @@
-Part IV. Client Interfaces
This part describes the client programming interfaces distributed
with PostgreSQL. Each of these chapters can be
read independently. Note that there are many other programming
@@ -9,4 +9,4 @@
familiar with using SQL commands to manipulate
and query the database (see Part II) and of course
with the programming language that the interface uses.
-
\ No newline at end of file
diff --git a/doc/src/sgml/html/collation.html b/doc/src/sgml/html/collation.html
index 2eeb947..4999778 100644
--- a/doc/src/sgml/html/collation.html
+++ b/doc/src/sgml/html/collation.html
@@ -1,5 +1,5 @@
-24.2. Collation Support
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/color-when.html b/doc/src/sgml/html/color-when.html
index 8197e68..ca9fd87 100644
--- a/doc/src/sgml/html/color-when.html
+++ b/doc/src/sgml/html/color-when.html
@@ -1,5 +1,5 @@
-N.1. When Color is Used
To use colorized output, set the environment variable
PG_COLOR
as follows:
@@ -12,4 +12,4 @@
Otherwise, color is not used.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/color-which.html b/doc/src/sgml/html/color-which.html
index f3d6829..375235c 100644
--- a/doc/src/sgml/html/color-which.html
+++ b/doc/src/sgml/html/color-which.html
@@ -1,5 +1,5 @@
-N.2. Configuring the Colors
The actual colors to be used are configured using the environment variable
PG_COLORS
(note plural). The value is a colon-separated list of
@@ -23,4 +23,4 @@
This color specification format is also used by other software packages
such as GCC, GNU
coreutils, and GNU grep.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/color.html b/doc/src/sgml/html/color.html
index 0b5c321..af1e68b 100644
--- a/doc/src/sgml/html/color.html
+++ b/doc/src/sgml/html/color.html
@@ -1,5 +1,5 @@
-Appendix N. Color Support
Most programs in the PostgreSQL package can produce colorized console
output. This appendix describes how that is configured.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/config-setting.html b/doc/src/sgml/html/config-setting.html
index 06f6339..a991297 100644
--- a/doc/src/sgml/html/config-setting.html
+++ b/doc/src/sgml/html/config-setting.html
@@ -1,5 +1,5 @@
-20.1. Setting Parameters
All parameter names are case-insensitive. Every parameter takes a
value of one of five types: boolean, string, integer, floating point,
or enumerated (enum). The type determines the syntax for setting the
@@ -333,4 +333,4 @@ include_dir 'conf.d'
their configurations all stored in one place, such as in a version
control repository. (Storing database configuration files under version
control is another good practice to consider.)
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/connect-estab.html b/doc/src/sgml/html/connect-estab.html
index c1d4192..c11f6e3 100644
--- a/doc/src/sgml/html/connect-estab.html
+++ b/doc/src/sgml/html/connect-estab.html
@@ -1,5 +1,5 @@
-52.2. How Connections Are Established
PostgreSQL implements a
“process per user” client/server model.
In this model, every
@@ -33,4 +33,4 @@
process parses the query, creates an execution plan,
executes the plan, and returns the retrieved rows to the client
by transmitting them over the established connection.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/continuous-archiving.html b/doc/src/sgml/html/continuous-archiving.html
index a25d960..f3cee99 100644
--- a/doc/src/sgml/html/continuous-archiving.html
+++ b/doc/src/sgml/html/continuous-archiving.html
@@ -1,5 +1,5 @@
-26.3. Continuous Archiving and Point-in-Time Recovery (PITR)
26.3. Continuous Archiving and Point-in-Time Recovery (PITR)
At all times, PostgreSQL maintains a
write ahead log (WAL) in the pg_wal/
subdirectory of the cluster's data directory. The log records
@@ -754,4 +754,4 @@ archive_command = 'local_backup_script.sh "%p" "%f"'
on. In the meantime, administrators might wish to reduce the number
of page snapshots included in WAL by increasing the checkpoint
interval parameters as much as feasible.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/contrib-dblink-build-sql-delete.html b/doc/src/sgml/html/contrib-dblink-build-sql-delete.html
index 16f026c..7769bcd 100644
--- a/doc/src/sgml/html/contrib-dblink-build-sql-delete.html
+++ b/doc/src/sgml/html/contrib-dblink-build-sql-delete.html
@@ -1,5 +1,5 @@
-dblink_build_sql_delete
dblink_build_sql_delete — builds a DELETE statement using supplied values for primary
key field values
Synopsis
dblink_build_sql_delete(text relname,
@@ -39,4 +39,4 @@ SELECT dblink_build_sql_delete('"MyFoo"', '1 2', 2, '{"1", "b"}');
---------------------------------------------
DELETE FROM "MyFoo" WHERE f1='1' AND f2='b'
(1 row)
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/contrib-dblink-build-sql-insert.html b/doc/src/sgml/html/contrib-dblink-build-sql-insert.html
index 6e137ff..b641a86 100644
--- a/doc/src/sgml/html/contrib-dblink-build-sql-insert.html
+++ b/doc/src/sgml/html/contrib-dblink-build-sql-insert.html
@@ -1,5 +1,5 @@
-dblink_build_sql_insert
\ No newline at end of file
diff --git a/doc/src/sgml/html/contrib-dblink-build-sql-update.html b/doc/src/sgml/html/contrib-dblink-build-sql-update.html
index 29a8f68..0ab0b76 100644
--- a/doc/src/sgml/html/contrib-dblink-build-sql-update.html
+++ b/doc/src/sgml/html/contrib-dblink-build-sql-update.html
@@ -1,5 +1,5 @@
-dblink_build_sql_update
dblink_build_sql_update — builds an UPDATE statement using a local tuple, replacing
the primary key field values with alternative supplied values
Synopsis
dblink_build_sql_update(text relname,
@@ -51,4 +51,4 @@ SELECT dblink_build_sql_update('foo', '1 2', 2, '{"1", "a"}', '{"1", "b"}');
-------------------------------------------------------------
UPDATE foo SET f1='1',f2='b',f3='1' WHERE f1='1' AND f2='b'
(1 row)
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/contrib-dblink-cancel-query.html b/doc/src/sgml/html/contrib-dblink-cancel-query.html
index a83a5d9..f4979b8 100644
--- a/doc/src/sgml/html/contrib-dblink-cancel-query.html
+++ b/doc/src/sgml/html/contrib-dblink-cancel-query.html
@@ -1,5 +1,5 @@
-dblink_cancel_query
dblink_cancel_query — cancels any active query on the named connection
Synopsis
dblink_cancel_query(text connname) returns text
Description
dblink_cancel_query attempts to cancel any query that
@@ -16,4 +16,4 @@ dblink_cancel_query(text connname) returns text
the text of an error message on failure.
Examples
SELECT dblink_cancel_query('dtest1');
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/contrib-dblink-close.html b/doc/src/sgml/html/contrib-dblink-close.html
index 1a44973..2feb895 100644
--- a/doc/src/sgml/html/contrib-dblink-close.html
+++ b/doc/src/sgml/html/contrib-dblink-close.html
@@ -1,5 +1,5 @@
-dblink_close
\ No newline at end of file
diff --git a/doc/src/sgml/html/contrib-dblink-connect-u.html b/doc/src/sgml/html/contrib-dblink-connect-u.html
index 83168b4..b42c0f4 100644
--- a/doc/src/sgml/html/contrib-dblink-connect-u.html
+++ b/doc/src/sgml/html/contrib-dblink-connect-u.html
@@ -1,5 +1,5 @@
-dblink_connect_u
dblink_connect_u — opens a persistent connection to a remote database, insecurely
Synopsis
dblink_connect_u(text connstr) returns text
dblink_connect_u(text connname, text connstr) returns text
Description
@@ -26,4 +26,4 @@ dblink_connect_u(text connname, text connstr) returns text
not contain any records specifying a wildcard host name.
For further details see dblink_connect().
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/contrib-dblink-connect.html b/doc/src/sgml/html/contrib-dblink-connect.html
index 0510872..2db191a 100644
--- a/doc/src/sgml/html/contrib-dblink-connect.html
+++ b/doc/src/sgml/html/contrib-dblink-connect.html
@@ -1,5 +1,5 @@
-dblink_connect
dblink_connect — opens a persistent connection to a remote database
Synopsis
dblink_connect(text connstr) returns text
dblink_connect(text connname, text connstr) returns text
Description
@@ -102,4 +102,4 @@ REVOKE SELECT ON TABLE foo FROM regress_dblink_user;
DROP USER MAPPING FOR regress_dblink_user SERVER fdtest;
DROP USER regress_dblink_user;
DROP SERVER fdtest;
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/contrib-dblink-disconnect.html b/doc/src/sgml/html/contrib-dblink-disconnect.html
index 45e680f..3b709ce 100644
--- a/doc/src/sgml/html/contrib-dblink-disconnect.html
+++ b/doc/src/sgml/html/contrib-dblink-disconnect.html
@@ -1,5 +1,5 @@
-dblink_disconnect
\ No newline at end of file
diff --git a/doc/src/sgml/html/contrib-dblink-error-message.html b/doc/src/sgml/html/contrib-dblink-error-message.html
index 496906b..6e103e6 100644
--- a/doc/src/sgml/html/contrib-dblink-error-message.html
+++ b/doc/src/sgml/html/contrib-dblink-error-message.html
@@ -1,5 +1,5 @@
-dblink_error_message
dblink_error_message — gets last error message on the named connection
Synopsis
dblink_error_message(text connname) returns text
Description
dblink_error_message fetches the most recent remote
@@ -19,4 +19,4 @@ dblink_error_message(text connname) returns text
the asynchronous query will be visible.
Examples
SELECT dblink_error_message('dtest1');
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/contrib-dblink-exec.html b/doc/src/sgml/html/contrib-dblink-exec.html
index aaea2f6..4b082e3 100644
--- a/doc/src/sgml/html/contrib-dblink-exec.html
+++ b/doc/src/sgml/html/contrib-dblink-exec.html
@@ -1,5 +1,5 @@
-dblink_exec
dblink_exec — executes a command in a remote database
Synopsis
dblink_exec(text connname, text sql [, bool fail_on_error]) returns text
dblink_exec(text connstr, text sql [, bool fail_on_error]) returns text
dblink_exec(text sql [, bool fail_on_error]) returns text
@@ -62,4 +62,4 @@ DETAIL: ERROR: null value in column "relnamespace" violates not-null constrain
-------------
ERROR
(1 row)
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/contrib-dblink-fetch.html b/doc/src/sgml/html/contrib-dblink-fetch.html
index a2f9e35..7785023 100644
--- a/doc/src/sgml/html/contrib-dblink-fetch.html
+++ b/doc/src/sgml/html/contrib-dblink-fetch.html
@@ -1,5 +1,5 @@
-dblink_fetch
dblink_fetch — returns rows from an open cursor in a remote database
Synopsis
dblink_fetch(text cursorname, int howmany [, bool fail_on_error]) returns setof record
dblink_fetch(text connname, text cursorname, int howmany [, bool fail_on_error]) returns setof record
\ No newline at end of file
diff --git a/doc/src/sgml/html/contrib-dblink-function.html b/doc/src/sgml/html/contrib-dblink-function.html
index bf95197..418c921 100644
--- a/doc/src/sgml/html/contrib-dblink-function.html
+++ b/doc/src/sgml/html/contrib-dblink-function.html
@@ -1,5 +1,5 @@
-dblink
dblink(text connname, text sql [, bool fail_on_error]) returns setof record
dblink(text connstr, text sql [, bool fail_on_error]) returns setof record
dblink(text sql [, bool fail_on_error]) returns setof record
@@ -140,4 +140,4 @@ SELECT * FROM dblink('myconn', 'select proname, prosrc from pg_proc')
byteain | byteain
byteaout | byteaout
(14 rows)
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/contrib-dblink-get-connections.html b/doc/src/sgml/html/contrib-dblink-get-connections.html
index 08019eb..dc117bf 100644
--- a/doc/src/sgml/html/contrib-dblink-get-connections.html
+++ b/doc/src/sgml/html/contrib-dblink-get-connections.html
@@ -1,9 +1,9 @@
-dblink_get_connections
dblink_get_connections — returns the names of all open named dblink connections
Synopsis
dblink_get_connections() returns text[]
Description
dblink_get_connections returns an array of the names
of all open named dblink connections.
Return Value
Returns a text array of connection names, or NULL if none.
Examples
SELECT dblink_get_connections();
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/contrib-dblink-get-notify.html b/doc/src/sgml/html/contrib-dblink-get-notify.html
index 69406a2..b051635 100644
--- a/doc/src/sgml/html/contrib-dblink-get-notify.html
+++ b/doc/src/sgml/html/contrib-dblink-get-notify.html
@@ -1,5 +1,5 @@
-dblink_get_notify
\ No newline at end of file
diff --git a/doc/src/sgml/html/contrib-dblink-get-pkey.html b/doc/src/sgml/html/contrib-dblink-get-pkey.html
index 986bca9..349caa2 100644
--- a/doc/src/sgml/html/contrib-dblink-get-pkey.html
+++ b/doc/src/sgml/html/contrib-dblink-get-pkey.html
@@ -1,5 +1,5 @@
-dblink_get_pkey
\ No newline at end of file
diff --git a/doc/src/sgml/html/contrib-dblink-get-result.html b/doc/src/sgml/html/contrib-dblink-get-result.html
index aa5710e..34ccc45 100644
--- a/doc/src/sgml/html/contrib-dblink-get-result.html
+++ b/doc/src/sgml/html/contrib-dblink-get-result.html
@@ -1,5 +1,5 @@
-dblink_get_result
dblink_get_result(text connname [, bool fail_on_error]) returns setof record
Description
dblink_get_result collects the results of an
@@ -95,4 +95,4 @@ contrib_regression=# SELECT * FROM dblink_get_result('dtest1') AS t1(f1 int, f2
f1 | f2 | f3
----+----+----
(0 rows)
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/contrib-dblink-is-busy.html b/doc/src/sgml/html/contrib-dblink-is-busy.html
index 9926f6e..31cb91e 100644
--- a/doc/src/sgml/html/contrib-dblink-is-busy.html
+++ b/doc/src/sgml/html/contrib-dblink-is-busy.html
@@ -1,5 +1,5 @@
-dblink_is_busy
dblink_is_busy — checks if connection is busy with an async query
Synopsis
dblink_is_busy(text connname) returns int
Description
dblink_is_busy tests whether an async query is in progress.
@@ -11,4 +11,4 @@ dblink_is_busy(text connname) returns int
dblink_get_result will not block.
Examples
SELECT dblink_is_busy('dtest1');
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/contrib-dblink-open.html b/doc/src/sgml/html/contrib-dblink-open.html
index c18d744..c2e22ed 100644
--- a/doc/src/sgml/html/contrib-dblink-open.html
+++ b/doc/src/sgml/html/contrib-dblink-open.html
@@ -1,5 +1,5 @@
-dblink_open
dblink_open(text cursorname, text sql [, bool fail_on_error]) returns text
dblink_open(text connname, text cursorname, text sql [, bool fail_on_error]) returns text
Description
@@ -45,4 +45,4 @@ SELECT dblink_open('foo', 'select proname, prosrc from pg_proc');
-------------
OK
(1 row)
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/contrib-dblink-send-query.html b/doc/src/sgml/html/contrib-dblink-send-query.html
index 1813448..6b2bdef 100644
--- a/doc/src/sgml/html/contrib-dblink-send-query.html
+++ b/doc/src/sgml/html/contrib-dblink-send-query.html
@@ -1,5 +1,5 @@
-dblink_send_query
dblink_send_query — sends an async query to a remote database
Synopsis
dblink_send_query(text connname, text sql) returns int
Description
dblink_send_query sends a query to be executed
@@ -21,4 +21,4 @@ dblink_send_query(text connname, text sql) returns int
Returns 1 if the query was successfully dispatched, 0 otherwise.
Examples
SELECT dblink_send_query('dtest1', 'SELECT * FROM foo WHERE f1 < 3');
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/contrib-prog-client.html b/doc/src/sgml/html/contrib-prog-client.html
index e0f0372..b0ec438 100644
--- a/doc/src/sgml/html/contrib-prog-client.html
+++ b/doc/src/sgml/html/contrib-prog-client.html
@@ -1,9 +1,9 @@
-G.1. Client Applications
oid2name — resolve OIDs and file nodes in a PostgreSQL data directory
vacuumlo — remove orphaned large objects from a PostgreSQL database
This section covers PostgreSQL client
applications in contrib. They can be run from anywhere,
independent of where the database server resides. See
also PostgreSQL Client Applications for information about client
applications that are part of the core PostgreSQL
distribution.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/contrib-prog-server.html b/doc/src/sgml/html/contrib-prog-server.html
index 42e6f1d..5de681b 100644
--- a/doc/src/sgml/html/contrib-prog-server.html
+++ b/doc/src/sgml/html/contrib-prog-server.html
@@ -1,7 +1,7 @@
-G.2. Server Applications
Some applications run on the PostgreSQL server
itself. Currently, no such applications are included in the
contrib directory. See also PostgreSQL Server Applications for information about server applications that
are part of the core PostgreSQL distribution.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/contrib-prog.html b/doc/src/sgml/html/contrib-prog.html
index 685da92..2b0c04a 100644
--- a/doc/src/sgml/html/contrib-prog.html
+++ b/doc/src/sgml/html/contrib-prog.html
@@ -1,5 +1,5 @@
-Appendix G. Additional Supplied Programs
This appendix and the previous one contain information regarding the modules that
can be found in the contrib directory of the
PostgreSQL distribution. See Appendix F for
@@ -12,4 +12,4 @@
the bin directory of the
PostgreSQL installation and can be used like any
other program.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/contrib-spi.html b/doc/src/sgml/html/contrib-spi.html
index c9febd9..f751e65 100644
--- a/doc/src/sgml/html/contrib-spi.html
+++ b/doc/src/sgml/html/contrib-spi.html
@@ -1,5 +1,5 @@
-F.41. spi
The spi module provides several workable examples
of using the Server Programming Interface
(SPI) and triggers. While these functions are of
@@ -78,4 +78,4 @@
time zone.
There is an example in moddatetime.example.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/contrib.html b/doc/src/sgml/html/contrib.html
index 1f0f43b..7483062 100644
--- a/doc/src/sgml/html/contrib.html
+++ b/doc/src/sgml/html/contrib.html
@@ -1,5 +1,5 @@
-Appendix F. Additional Supplied Modules
dblink_get_pkey — returns the positions and field names of a relation's
primary key fields
dblink_build_sql_insert —
builds an INSERT statement using a local tuple, replacing the
@@ -84,4 +84,4 @@ CREATE EXTENSION module_name;
by way of
shared_preload_libraries. See the documentation of each
module for details.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/creating-cluster.html b/doc/src/sgml/html/creating-cluster.html
index 182603c..c7bbee8 100644
--- a/doc/src/sgml/html/creating-cluster.html
+++ b/doc/src/sgml/html/creating-cluster.html
@@ -1,5 +1,5 @@
-19.2. Creating a Database Cluster
Before you can do anything, you must initialize a database storage
area on disk. We call this a database cluster.
(The SQL standard uses the term catalog cluster.) A
@@ -200,4 +200,4 @@ postgres$ initdb -D /usr/local/pgsql/data
it. That approach might relieve the DBA from having to deal with some of
the idiosyncrasies of NFS, but of course the complexity of managing
remote storage then happens at other levels.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/cube.html b/doc/src/sgml/html/cube.html
index a73f02e..7c53fc6 100644
--- a/doc/src/sgml/html/cube.html
+++ b/doc/src/sgml/html/cube.html
@@ -1,5 +1,5 @@
-F.11. cube
This module implements a data type cube for
representing multidimensional cubes.
@@ -388,4 +388,4 @@ t
July 2006. These include cube(float8[], float8[]) and
cleaning up the code to use the V1 call protocol instead of the deprecated
V0 protocol.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/custom-rmgr.html b/doc/src/sgml/html/custom-rmgr.html
index 462d875..4492e4a 100644
--- a/doc/src/sgml/html/custom-rmgr.html
+++ b/doc/src/sgml/html/custom-rmgr.html
@@ -1,5 +1,5 @@
-Chapter 66. Custom WAL Resource Managers
This chapter explains the interface between the core
PostgreSQL system and custom WAL resource
managers, which enable extensions to integrate directly with the WAL.
@@ -78,4 +78,4 @@ extern void RegisterCustomRmgr(RmgrId rmid, RmgrData *rmgr);
custom WAL records may exist in the system. Otherwise
PostgreSQL will not be able to apply or decode
the custom WAL records, which may prevent the server from starting.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/custom-scan-execution.html b/doc/src/sgml/html/custom-scan-execution.html
index a18841f..6e813e3 100644
--- a/doc/src/sgml/html/custom-scan-execution.html
+++ b/doc/src/sgml/html/custom-scan-execution.html
@@ -1,5 +1,5 @@
-61.3. Executing Custom Scans
When a CustomScan is executed, its execution state is
represented by a CustomScanState, which is declared as
follows:
@@ -136,4 +136,4 @@ void (*ExplainCustomScan) (CustomScanState *node,
ScanState, such as the target list and scan relation, will
be shown even without this callback, but the callback allows the display
of additional, private state.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/custom-scan-path.html b/doc/src/sgml/html/custom-scan-path.html
index a1f9924..036f3dd 100644
--- a/doc/src/sgml/html/custom-scan-path.html
+++ b/doc/src/sgml/html/custom-scan-path.html
@@ -1,5 +1,5 @@
-61.1. Creating Custom Scan Paths
A custom scan provider will typically add paths for a base relation by
setting the following hook, which is called after the core code has
generated all the access paths it can for the relation (except for
@@ -98,4 +98,4 @@ List *(*ReparameterizeCustomPathByChild) (PlannerInfo *root,
reparameterize_path_by_child,
adjust_appendrel_attrs or
adjust_appendrel_attrs_multilevel as required.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/custom-scan-plan.html b/doc/src/sgml/html/custom-scan-plan.html
index b16656f..43b3067 100644
--- a/doc/src/sgml/html/custom-scan-plan.html
+++ b/doc/src/sgml/html/custom-scan-plan.html
@@ -1,5 +1,5 @@
-61.2. Creating Custom Scan Plans
A custom scan is represented in a finished plan tree using the following
structure:
@@ -64,4 +64,4 @@ Node *(*CreateCustomScanState) (CustomScan *cscan);
stage; after ExecInitCustomScan performs basic initialization,
the BeginCustomScan callback will be invoked to give the
custom scan provider a chance to do whatever else is needed.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/custom-scan.html b/doc/src/sgml/html/custom-scan.html
index 4a57578..b72c861 100644
--- a/doc/src/sgml/html/custom-scan.html
+++ b/doc/src/sgml/html/custom-scan.html
@@ -1,5 +1,5 @@
-Chapter 61. Writing a Custom Scan Provider
PostgreSQL supports a set of experimental facilities which
are intended to allow extension modules to add new scan types to the system.
Unlike a foreign data wrapper, which is only
@@ -18,4 +18,4 @@
Finally, it must be possible to execute the plan and generate the same
results that would have been generated for any other access path targeting
the same relation.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/database-roles.html b/doc/src/sgml/html/database-roles.html
index 48a7f8b..8557ab3 100644
--- a/doc/src/sgml/html/database-roles.html
+++ b/doc/src/sgml/html/database-roles.html
@@ -1,5 +1,5 @@
-22.1. Database Roles
Database roles are conceptually completely separate from
operating system users. In practice it might be convenient to
maintain a correspondence, but this is not required. Database roles
@@ -67,4 +67,4 @@ SELECT rolname FROM pg_roles;
identity determines the set of privileges available to a connected
client, it is important to carefully configure privileges when setting up
a multiuser environment.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/datatype-binary.html b/doc/src/sgml/html/datatype-binary.html
index 4020ebe..2baf53a 100644
--- a/doc/src/sgml/html/datatype-binary.html
+++ b/doc/src/sgml/html/datatype-binary.html
@@ -1,5 +1,5 @@
-8.4. Binary Data Types
The bytea data type allows storage of binary strings;
see Table 8.6.
Table 8.6. Binary Data Types
Name
Storage Size
Description
bytea
1 or 4 bytes plus the actual binary string
variable-length binary string
@@ -129,4 +129,4 @@ SELECT 'abc \153\154\155 \052\251\124'::bytea;
unescaping bytea strings. For example, you might also
have to escape line feeds and carriage returns if your interface
automatically translates these.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/datatype-bit.html b/doc/src/sgml/html/datatype-bit.html
index 03992d5..dbc21d2 100644
--- a/doc/src/sgml/html/datatype-bit.html
+++ b/doc/src/sgml/html/datatype-bit.html
@@ -1,5 +1,5 @@
-8.10. Bit String Types
Bit strings are strings of 1's and 0's. They can be used to store
or visualize bit masks. There are two SQL bit types:
bit(n) and bit
@@ -46,4 +46,4 @@ SELECT * FROM test;
5 or 8 bytes overhead depending on the length of the string
(but long values may be compressed or moved out-of-line, as explained
in Section 8.3 for character strings).
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/datatype-boolean.html b/doc/src/sgml/html/datatype-boolean.html
index 2e58a8b..b10d5c7 100644
--- a/doc/src/sgml/html/datatype-boolean.html
+++ b/doc/src/sgml/html/datatype-boolean.html
@@ -1,5 +1,5 @@
-8.6. Boolean Type
PostgreSQL provides the
standard SQL type boolean;
see Table 8.19.
@@ -55,4 +55,4 @@ SELECT * FROM test1 WHERE a;
example NULL::boolean. Conversely, the cast can be
omitted from a string-literal Boolean value in contexts where the parser
can deduce that the literal must be of type boolean.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/datatype-character.html b/doc/src/sgml/html/datatype-character.html
index b1b9a10..349f3b4 100644
--- a/doc/src/sgml/html/datatype-character.html
+++ b/doc/src/sgml/html/datatype-character.html
@@ -1,5 +1,5 @@
-8.3. Character Types
Table 8.4 shows the
general-purpose character types available in
PostgreSQL.
@@ -139,4 +139,4 @@ SELECT b, char_length(b) FROM test2;
only uses one byte of storage, and therefore can store only a single
ASCII character. It is used in the system
catalogs as a simplistic enumeration type.
-
Table 8.5. Special Character Types
Name
Storage Size
Description
"char"
1 byte
single-byte internal type
name
64 bytes
internal type for object names
\ No newline at end of file
+
Table 8.5. Special Character Types
Name
Storage Size
Description
"char"
1 byte
single-byte internal type
name
64 bytes
internal type for object names
\ No newline at end of file
diff --git a/doc/src/sgml/html/datatype-datetime.html b/doc/src/sgml/html/datatype-datetime.html
index 8a4534d..a70596d 100644
--- a/doc/src/sgml/html/datatype-datetime.html
+++ b/doc/src/sgml/html/datatype-datetime.html
@@ -1,5 +1,5 @@
-8.5. Date/Time Types
PostgreSQL supports the full set of
SQL date and time types, shown in Table 8.9. The operations available
on these data types are described in
@@ -244,7 +244,7 @@ TIMESTAMP WITH TIME ZONE '2004-10-19 10:23:54+02'
the date and time. PostgreSQL accepts that format on
input, but on output it uses a space rather than T, as shown
above. This is for readability and for consistency with
- RFC 3339 as
+ RFC 3339 as
well as some other database systems.
In the SQL and POSTGRES styles, day appears before
@@ -479,10 +479,29 @@ P [years-
- Field values can have fractional parts: for example, '1.5
+ Internally, interval values are stored as three integral
+ fields: months, days, and microseconds. These fields are kept
+ separate because the number of days in a month varies, while a day
+ can have 23 or 25 hours if a daylight savings time transition is
+ involved. An interval input string that uses other units is
+ normalized into this format, and then reconstructed in a standardized
+ way for output, for example:
+
+
+SELECT '2 years 15 months 100 weeks 99 hours 123456789 milliseconds'::interval;
+ interval
+---------------------------------------
+ 3 years 3 mons 700 days 133:17:36.789
+
+
+ Here weeks, which are understood as “7 days”, have been
+ kept separate, while the smaller and larger time units were
+ combined and normalized.
+
+ Input field values can have fractional parts, for example '1.5
weeks' or '01:02:03.45'. However,
- because interval internally stores only three integer units (months,
- days, microseconds), fractional units must be spilled to smaller
+ because interval internally stores only integral fields,
+ fractional values must be converted into smaller
units. Fractional parts of units greater than months are rounded to
be an integer number of months, e.g. '1.5 years'
becomes '1 year 6 mons'. Fractional parts of
@@ -494,32 +513,20 @@ P [years-
Table 8.17 shows some examples
of valid interval input.
-
Table 8.17. Interval Input
Example
Description
1-2
SQL standard format: 1 year 2 months
3 4:05:06
SQL standard format: 3 days 4 hours 5 minutes 6 seconds
1 year 2 months 3 days 4 hours 5 minutes 6 seconds
Traditional Postgres format: 1 year 2 months 3 days 4 hours 5 minutes 6 seconds
P1Y2M3DT4H5M6S
ISO 8601 “format with designators”: same meaning as above
P0001-02-03T04:05:06
ISO 8601 “alternative format”: same meaning as above
- Internally interval values are stored as months, days,
- and microseconds. This is done because the number of days in a month
- varies, and a day can have 23 or 25 hours if a daylight savings
- time adjustment is involved. The months and days fields are integers
- while the microseconds field can store fractional seconds. Because intervals are
- usually created from constant strings or timestamp subtraction,
- this storage method works well in most cases, but can cause unexpected
- results:
-
-
-
- Functions justify_days and
- justify_hours are available for adjusting days
- and hours that overflow their normal ranges.
-
8.5.5. Interval Output
+
Table 8.17. Interval Input
Example
Description
1-2
SQL standard format: 1 year 2 months
3 4:05:06
SQL standard format: 3 days 4 hours 5 minutes 6 seconds
1 year 2 months 3 days 4 hours 5 minutes 6 seconds
Traditional Postgres format: 1 year 2 months 3 days 4 hours 5 minutes 6 seconds
P1Y2M3DT4H5M6S
ISO 8601 “format with designators”: same meaning as above
P0001-02-03T04:05:06
ISO 8601 “alternative format”: same meaning as above
8.5.5. Interval Output
+ As previously explained, PostgreSQL
+ stores interval values as months, days, and
+ microseconds. For output, the months field is converted to years and
+ months by dividing by 12. The days field is shown as-is. The
+ microseconds field is converted to hours, minutes, seconds, and
+ fractional seconds. Thus months, minutes, and seconds will never be
+ shown as exceeding the ranges 0–11, 0–59, and 0–59
+ respectively, while the displayed years, days, and hours fields can
+ be quite large. (The justify_days
+ and justify_hours
+ functions can be used if it is desirable to transpose large days or
+ hours values into the next higher field.)
+
The output format of the interval type can be set to one of the
four styles sql_standard, postgres,
postgres_verbose, or iso_8601,
@@ -547,4 +554,4 @@ SELECT EXTRACT(days from '80 hours'::interval);
The output of the iso_8601 style matches the “format
with designators” described in section 4.4.3.2 of the
ISO 8601 standard.
-
Table 8.18. Interval Output Style Examples
Style Specification
Year-Month Interval
Day-Time Interval
Mixed Interval
sql_standard
1-2
3 4:05:06
-1-2 +3 -4:05:06
postgres
1 year 2 mons
3 days 04:05:06
-1 year -2 mons +3 days -04:05:06
postgres_verbose
@ 1 year 2 mons
@ 3 days 4 hours 5 mins 6 secs
@ 1 year 2 mons -3 days 4 hours 5 mins 6 secs ago
iso_8601
P1Y2M
P3DT4H5M6S
P-1Y-2M3DT-4H-5M-6S
\ No newline at end of file
+
Table 8.18. Interval Output Style Examples
Style Specification
Year-Month Interval
Day-Time Interval
Mixed Interval
sql_standard
1-2
3 4:05:06
-1-2 +3 -4:05:06
postgres
1 year 2 mons
3 days 04:05:06
-1 year -2 mons +3 days -04:05:06
postgres_verbose
@ 1 year 2 mons
@ 3 days 4 hours 5 mins 6 secs
@ 1 year 2 mons -3 days 4 hours 5 mins 6 secs ago
iso_8601
P1Y2M
P3DT4H5M6S
P-1Y-2M3DT-4H-5M-6S
\ No newline at end of file
diff --git a/doc/src/sgml/html/datatype-enum.html b/doc/src/sgml/html/datatype-enum.html
index c54620c..4e1a908 100644
--- a/doc/src/sgml/html/datatype-enum.html
+++ b/doc/src/sgml/html/datatype-enum.html
@@ -1,5 +1,5 @@
-8.7. Enumerated Types
Enumerated (enum) types are data types that
comprise a static, ordered set of values.
They are equivalent to the enum
@@ -112,4 +112,4 @@ SELECT person.name, holidays.num_weeks FROM person, holidays
kept in the system catalog
pg_enum.
Querying this catalog directly can be useful.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/datatype-geometric.html b/doc/src/sgml/html/datatype-geometric.html
index 2f876e2..69522a3 100644
--- a/doc/src/sgml/html/datatype-geometric.html
+++ b/doc/src/sgml/html/datatype-geometric.html
@@ -1,5 +1,5 @@
-8.8. Geometric Types
Geometric data types represent two-dimensional spatial
objects. Table 8.20 shows the geometric
types available in PostgreSQL.
@@ -149,4 +149,4 @@
circle.
Circles are output using the first syntax.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/datatype-json.html b/doc/src/sgml/html/datatype-json.html
index 54cab9a..d7ceac3 100644
--- a/doc/src/sgml/html/datatype-json.html
+++ b/doc/src/sgml/html/datatype-json.html
@@ -1,7 +1,7 @@
-8.14. JSON Types
JSON data types are for storing JSON (JavaScript Object Notation)
- data, as specified in RFC
+ data, as specified in RFC
7159. Such data can also be stored as text, but
the JSON data types have the advantage of enforcing that each
stored value is valid according to the JSON rules. There are also
@@ -595,21 +595,20 @@ UPDATE table_name SET jsonb_field[1]['a'] = '1';
In particular, the way to write a double quote within an embedded string
literal is \", and to write a backslash itself, you
must write \\. Other special backslash sequences
- include those recognized in JSON strings:
+ include those recognized in JavaScript strings:
\b,
\f,
\n,
\r,
\t,
\v
- for various ASCII control characters, and
- \uNNNN for a Unicode
- character identified by its 4-hex-digit code point. The backslash
- syntax also includes two cases not allowed by JSON:
+ for various ASCII control characters,
\xNN for a character code
- written with only two hex digits, and
- \u{N...} for a character
- code written with 1 to 6 hex digits.
+ written with only two hex digits,
+ \uNNNN for a Unicode
+ character identified by its 4-hex-digit code point, and
+ \u{N...} for a Unicode
+ character code point written with 1 to 6 hex digits.
A path expression consists of a sequence of path elements,
which can be any of the following:
@@ -727,4 +726,4 @@ UPDATE table_name SET jsonb_field[1]['a'] = '1';
For this purpose, the term “value” includes array elements,
though JSON terminology sometimes considers array elements distinct
from values within objects.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/datatype-money.html b/doc/src/sgml/html/datatype-money.html
index 7b78270..f4d53fa 100644
--- a/doc/src/sgml/html/datatype-money.html
+++ b/doc/src/sgml/html/datatype-money.html
@@ -1,5 +1,5 @@
-8.2. Monetary Types
The money type stores a currency amount with a fixed
fractional precision; see Table 8.3. The fractional precision is
determined by the database's lc_monetary setting.
@@ -41,4 +41,4 @@ SELECT '52093.89'::money::numeric::float8;
When a money value is divided by another money
value, the result is double precision (i.e., a pure number,
not money); the currency units cancel each other out in the division.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/datatype-net-types.html b/doc/src/sgml/html/datatype-net-types.html
index 5392173..40142a0 100644
--- a/doc/src/sgml/html/datatype-net-types.html
+++ b/doc/src/sgml/html/datatype-net-types.html
@@ -1,5 +1,5 @@
-8.9. Network Address Types
PostgreSQL offers data types to store IPv4, IPv6, and MAC
addresses, as shown in Table 8.21. It
is better to use these types instead of plain text types to store
@@ -129,4 +129,4 @@ SELECT macaddr8_set7bit('08:00:2b:01:02:03');
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/datatype-numeric.html b/doc/src/sgml/html/datatype-numeric.html
index b9bf037..38dbe1f 100644
--- a/doc/src/sgml/html/datatype-numeric.html
+++ b/doc/src/sgml/html/datatype-numeric.html
@@ -1,5 +1,5 @@
-8.1. Numeric Types
Numeric types consist of two-, four-, and eight-byte integers,
four- and eight-byte floating-point numbers, and selectable-precision
decimals. Table 8.2 lists the
@@ -367,4 +367,4 @@ ALTER SEQUENCE tablename_
Object identifiers (OIDs) are used internally by
PostgreSQL as primary keys for various
system tables.
@@ -163,4 +163,4 @@ WHERE ...
physical location of the row within its table.
(The system columns are further explained in Section 5.5.)
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/datatype-pg-lsn.html b/doc/src/sgml/html/datatype-pg-lsn.html
index ab31591..83cbbd8 100644
--- a/doc/src/sgml/html/datatype-pg-lsn.html
+++ b/doc/src/sgml/html/datatype-pg-lsn.html
@@ -1,5 +1,5 @@
-8.20. pg_lsn Type
The pg_lsn data type can be used to store LSN (Log Sequence
Number) data which is a pointer to a location in the WAL. This type is a
representation of XLogRecPtr and an internal system type of
@@ -19,4 +19,4 @@
the calculated LSN should be in the range of pg_lsn type,
i.e., between 0/0 and
FFFFFFFF/FFFFFFFF.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/datatype-pseudo.html b/doc/src/sgml/html/datatype-pseudo.html
index 43be0c8..0d2aee9 100644
--- a/doc/src/sgml/html/datatype-pseudo.html
+++ b/doc/src/sgml/html/datatype-pseudo.html
@@ -1,5 +1,5 @@
-8.21. Pseudo-Types
The PostgreSQL type system contains a
number of special-purpose entries that are collectively called
pseudo-types. A pseudo-type cannot be used as a
@@ -56,4 +56,4 @@
follow this coding rule: do not create any function that is
declared to return internal unless it has at least one
internal argument.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/datatype-textsearch.html b/doc/src/sgml/html/datatype-textsearch.html
index 521ca4a..1b2cfd0 100644
--- a/doc/src/sgml/html/datatype-textsearch.html
+++ b/doc/src/sgml/html/datatype-textsearch.html
@@ -1,5 +1,5 @@
-8.11. Text Search Types
PostgreSQL provides two data types that
are designed to support full text search, which is the activity of
searching through a collection of natural-language documents
@@ -193,4 +193,4 @@ SELECT to_tsvector( 'postgraduate' ), to_tsquery( 'postgres:*' );
'postgradu':1 | 'postgr':*
which will match the stemmed form of postgraduate.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/datatype-uuid.html b/doc/src/sgml/html/datatype-uuid.html
index 34c23be..f155f4e 100644
--- a/doc/src/sgml/html/datatype-uuid.html
+++ b/doc/src/sgml/html/datatype-uuid.html
@@ -1,7 +1,7 @@
-8.12. UUID Type
The data type uuid stores Universally Unique Identifiers
- (UUID) as defined by RFC 4122,
+ (UUID) as defined by RFC 4122,
ISO/IEC 9834-8:2005, and related standards.
(Some systems refer to this data type as a globally unique identifier, or
GUID, instead.) This
@@ -36,4 +36,4 @@ a0ee-bc99-9c0b-4ef8-bb6d-6bb9-bd38-0a11
See Section 9.14 for how to generate a UUID in
PostgreSQL.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/datatype-xml.html b/doc/src/sgml/html/datatype-xml.html
index 8d33bc2..b42b7a3 100644
--- a/doc/src/sgml/html/datatype-xml.html
+++ b/doc/src/sgml/html/datatype-xml.html
@@ -1,5 +1,5 @@
-8.13. XML Type
The xml data type can be used to store XML data. Its
advantage over storing XML data in a text field is that it
checks the input values for well-formedness, and there are support
@@ -148,4 +148,4 @@ SET xmloption TO { DOCUMENT | CONTENT };
up full-document searches of XML data. The necessary
preprocessing support is, however, not yet available in the PostgreSQL
distribution.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/datatype.html b/doc/src/sgml/html/datatype.html
index 0cd966d..c0961c2 100644
--- a/doc/src/sgml/html/datatype.html
+++ b/doc/src/sgml/html/datatype.html
@@ -1,5 +1,5 @@
-Chapter 8. Data Types
PostgreSQL has a rich set of native data
types available to users. Users can add new types to
PostgreSQL using the CREATE TYPE command.
@@ -33,4 +33,4 @@
Some of the input and output functions are not invertible, i.e.,
the result of an output function might lose accuracy when compared to
the original input.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/datetime-appendix.html b/doc/src/sgml/html/datetime-appendix.html
index c2cfe11..faf0109 100644
--- a/doc/src/sgml/html/datetime-appendix.html
+++ b/doc/src/sgml/html/datetime-appendix.html
@@ -1,5 +1,5 @@
-Appendix B. Date/Time Support
PostgreSQL uses an internal heuristic
parser for all date/time input support. Dates and times are input as
strings, and are broken up into distinct fields with a preliminary
@@ -12,4 +12,4 @@
This appendix includes information on the content of these
lookup tables and describes the steps used by the parser to decode
dates and times.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/datetime-config-files.html b/doc/src/sgml/html/datetime-config-files.html
index 2b670c9..fb3d46e 100644
--- a/doc/src/sgml/html/datetime-config-files.html
+++ b/doc/src/sgml/html/datetime-config-files.html
@@ -1,5 +1,5 @@
-B.4. Date/Time Configuration Files
Since timezone abbreviations are not well standardized,
PostgreSQL provides a means to customize
the set of abbreviations accepted by the server. The
@@ -95,4 +95,4 @@
If you modify files in .../share/timezonesets/,
it is up to you to make backups — a normal database dump
will not include this directory.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/datetime-input-rules.html b/doc/src/sgml/html/datetime-input-rules.html
index 1cc9c93..978a43c 100644
--- a/doc/src/sgml/html/datetime-input-rules.html
+++ b/doc/src/sgml/html/datetime-input-rules.html
@@ -1,5 +1,5 @@
-B.1. Date/Time Input Interpretation
Date/time input strings are decoded using the following procedure.
Break the input string into tokens and categorize each token as
@@ -71,4 +71,4 @@
Gregorian years AD 1–99 can be entered by using 4 digits with leading
zeros (e.g., 0099 is AD 99).
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/datetime-invalid-input.html b/doc/src/sgml/html/datetime-invalid-input.html
index fb438fa..110b171 100644
--- a/doc/src/sgml/html/datetime-invalid-input.html
+++ b/doc/src/sgml/html/datetime-invalid-input.html
@@ -1,5 +1,5 @@
-B.2. Handling of Invalid or Ambiguous Timestamps
Ordinarily, if a date/time string is syntactically valid but contains
out-of-range field values, an error will be thrown. For example, input
specifying the 31st of February will be rejected.
@@ -59,4 +59,4 @@
abbreviation that corresponds to a fixed UTC offset. The rule just
given applies only when it is necessary to infer a UTC offset for a time
zone in which the offset varies.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/datetime-julian-dates.html b/doc/src/sgml/html/datetime-julian-dates.html
index b9710f3..8351da4 100644
--- a/doc/src/sgml/html/datetime-julian-dates.html
+++ b/doc/src/sgml/html/datetime-julian-dates.html
@@ -1,5 +1,5 @@
-B.7. Julian Dates
The Julian Date system is a method for
numbering days. It is
unrelated to the Julian calendar, though it is confusingly
@@ -45,4 +45,4 @@
2459389
(1 row)
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/datetime-keywords.html b/doc/src/sgml/html/datetime-keywords.html
index 11bc78a..8781c25 100644
--- a/doc/src/sgml/html/datetime-keywords.html
+++ b/doc/src/sgml/html/datetime-keywords.html
@@ -1,5 +1,5 @@
-B.3. Date/Time Key Words
Table B.1 shows the tokens that are
recognized as names of months.
Table B.1. Month Names
Month
Abbreviations
January
Jan
February
Feb
March
Mar
April
Apr
May
June
Jun
July
Jul
August
Aug
September
Sep, Sept
October
Oct
November
Nov
December
Dec
@@ -8,4 +8,4 @@
Table B.2. Day of the Week Names
Day
Abbreviations
Sunday
Sun
Monday
Mon
Tuesday
Tue, Tues
Wednesday
Wed, Weds
Thursday
Thu, Thur, Thurs
Friday
Fri
Saturday
Sat
Table B.3 shows the tokens that serve
various modifier purposes.
-
Table B.3. Date/Time Field Modifiers
Identifier
Description
AM
Time is before 12:00
AT
Ignored
JULIAN, JD, J
Next field is Julian Date
ON
Ignored
PM
Time is on or after 12:00
T
Next field is time
\ No newline at end of file
+
Table B.3. Date/Time Field Modifiers
Identifier
Description
AM
Time is before 12:00
AT
Ignored
JULIAN, JD, J
Next field is Julian Date
ON
Ignored
PM
Time is on or after 12:00
T
Next field is time
\ No newline at end of file
diff --git a/doc/src/sgml/html/datetime-posix-timezone-specs.html b/doc/src/sgml/html/datetime-posix-timezone-specs.html
index 77792c1..46b3440 100644
--- a/doc/src/sgml/html/datetime-posix-timezone-specs.html
+++ b/doc/src/sgml/html/datetime-posix-timezone-specs.html
@@ -1,5 +1,5 @@
-B.5. POSIX Time Zone Specifications
PostgreSQL can accept time zone specifications
that are written according to the POSIX standard's rules
for the TZ environment
@@ -132,4 +132,4 @@
zone abbreviation(s). For example, SET TIMEZONE TO
FOOBAR0 will work, leaving the system effectively using a
rather peculiar abbreviation for UTC.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/datetime-units-history.html b/doc/src/sgml/html/datetime-units-history.html
index d42e3ed..79c9863 100644
--- a/doc/src/sgml/html/datetime-units-history.html
+++ b/doc/src/sgml/html/datetime-units-history.html
@@ -1,5 +1,5 @@
-B.6. History of Units
The SQL standard states that “Within the definition of a
‘datetime literal’, the ‘datetime
values’ are constrained by the natural rules for dates and
@@ -84,4 +84,4 @@ $ cal 9 1752
The People's Republic of China uses the Gregorian calendar
for civil purposes. The Chinese calendar is used for determining
festivals.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/dblink.html b/doc/src/sgml/html/dblink.html
index 28e3a3a..ce41074 100644
--- a/doc/src/sgml/html/dblink.html
+++ b/doc/src/sgml/html/dblink.html
@@ -1,5 +1,5 @@
-F.12. dblink
dblink_get_pkey — returns the positions and field names of a relation's
primary key fields
dblink_build_sql_insert —
builds an INSERT statement using a local tuple, replacing the
@@ -15,4 +15,4 @@
See also postgres_fdw, which provides roughly the same
functionality using a more modern and standards-compliant infrastructure.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ddl-alter.html b/doc/src/sgml/html/ddl-alter.html
index b5bd6fc..79115e5 100644
--- a/doc/src/sgml/html/ddl-alter.html
+++ b/doc/src/sgml/html/ddl-alter.html
@@ -1,5 +1,5 @@
-5.6. Modifying Tables
When you create a table and you realize that you made a mistake, or
the requirements of the application change, you can drop the
table and create it again. But this is not a convenient option if
@@ -153,4 +153,4 @@ ALTER TABLE products RENAME COLUMN product_no TO product_number;
ALTER TABLE products RENAME TO items;
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ddl-basics.html b/doc/src/sgml/html/ddl-basics.html
index 272487d..8391b69 100644
--- a/doc/src/sgml/html/ddl-basics.html
+++ b/doc/src/sgml/html/ddl-basics.html
@@ -1,5 +1,5 @@
-5.1. Table Basics
A table in a relational database is much like a table on paper: It
consists of rows and columns. The number and order of the columns
is fixed, and each column has a name. The number of rows is
@@ -98,4 +98,4 @@ DROP TABLE products;
security, or convenience. If you are eager to fill your tables with
data now you can skip ahead to Chapter 6 and read the
rest of this chapter later.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ddl-constraints.html b/doc/src/sgml/html/ddl-constraints.html
index 80315b2..3a6e23a 100644
--- a/doc/src/sgml/html/ddl-constraints.html
+++ b/doc/src/sgml/html/ddl-constraints.html
@@ -1,5 +1,5 @@
-5.4. Constraints
Data types are a way to limit the kind of data that can be stored
in a table. For many applications, however, the constraint they
provide is too coarse. For example, a column containing a product
@@ -604,4 +604,4 @@ CREATE TABLE circles (
Adding an exclusion constraint will automatically create an index
of the type specified in the constraint declaration.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ddl-default.html b/doc/src/sgml/html/ddl-default.html
index 1ee15e6..f2bc2cd 100644
--- a/doc/src/sgml/html/ddl-default.html
+++ b/doc/src/sgml/html/ddl-default.html
@@ -1,5 +1,5 @@
-5.2. Default Values
A column can be assigned a default value. When a new row is
created and no values are specified for some of the columns, those
columns will be filled with their respective default values. A
@@ -46,4 +46,4 @@ CREATE TABLE products (
);
The SERIAL shorthand is discussed further in Section 8.1.4.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ddl-depend.html b/doc/src/sgml/html/ddl-depend.html
index f529e15..8fa3063 100644
--- a/doc/src/sgml/html/ddl-depend.html
+++ b/doc/src/sgml/html/ddl-depend.html
@@ -1,5 +1,5 @@
-5.14. Dependency Tracking
When you create complex database structures involving many tables
with foreign key constraints, views, triggers, functions, etc. you
implicitly create a net of dependencies between the objects.
@@ -96,4 +96,4 @@ END;
then the function's dependency on the my_colors
table will be known and enforced by DROP.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ddl-foreign-data.html b/doc/src/sgml/html/ddl-foreign-data.html
index 764476c..b3f9226 100644
--- a/doc/src/sgml/html/ddl-foreign-data.html
+++ b/doc/src/sgml/html/ddl-foreign-data.html
@@ -1,5 +1,5 @@
-5.12. Foreign Data
PostgreSQL implements portions of the SQL/MED
specification, allowing you to access data that resides outside
PostgreSQL using regular SQL queries. Such data is referred to as
@@ -38,4 +38,4 @@
CREATE USER MAPPING,
CREATE FOREIGN TABLE, and
IMPORT FOREIGN SCHEMA.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ddl-generated-columns.html b/doc/src/sgml/html/ddl-generated-columns.html
index f621792..117860a 100644
--- a/doc/src/sgml/html/ddl-generated-columns.html
+++ b/doc/src/sgml/html/ddl-generated-columns.html
@@ -1,5 +1,5 @@
-5.3. Generated Columns
A generated column is a special column that is always computed from other
columns. Thus, it is for columns what a view is for tables. There are two
kinds of generated columns: stored and virtual. A stored generated column
@@ -82,4 +82,4 @@ CREATE TABLE people (
generated columns. But conversely, it is not allowed to access
generated columns in BEFORE triggers.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ddl-inherit.html b/doc/src/sgml/html/ddl-inherit.html
index beeeb0f..99fa367 100644
--- a/doc/src/sgml/html/ddl-inherit.html
+++ b/doc/src/sgml/html/ddl-inherit.html
@@ -1,5 +1,5 @@
-5.10. Inheritance
PostgreSQL implements table inheritance,
which can be a useful tool for database designers. (SQL:1999 and
later define a type inheritance feature, which differs in many
@@ -286,4 +286,4 @@ VALUES ('Albany', NULL, NULL, 'NY');
implemented for declarative partitioning.
Considerable care is needed in deciding whether partitioning with legacy
inheritance is useful for your application.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ddl-others.html b/doc/src/sgml/html/ddl-others.html
index b1566be..d927971 100644
--- a/doc/src/sgml/html/ddl-others.html
+++ b/doc/src/sgml/html/ddl-others.html
@@ -1,5 +1,5 @@
-5.13. Other Database Objects
Tables are the central objects in a relational database structure,
because they hold your data. But they are not the only objects
that exist in a database. Many other kinds of objects can be
@@ -17,4 +17,4 @@
Detailed information on
these topics appears in Part V.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ddl-partitioning.html b/doc/src/sgml/html/ddl-partitioning.html
index 7b3d0fd..3fdda8c 100644
--- a/doc/src/sgml/html/ddl-partitioning.html
+++ b/doc/src/sgml/html/ddl-partitioning.html
@@ -1,5 +1,5 @@
-5.11. Table Partitioning
PostgreSQL supports basic table
partitioning. This section describes why and how to implement
partitioning as part of your database design.
@@ -991,4 +991,4 @@ EXPLAIN SELECT count(*) FROM measurement WHERE logdate >= DATE '2008-01-01';
painfully slow. Simulations of the intended workload are often beneficial
for optimizing the partitioning strategy. Never just assume that more
partitions are better than fewer partitions, nor vice-versa.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ddl-priv.html b/doc/src/sgml/html/ddl-priv.html
index 05bd49f..5dd919c 100644
--- a/doc/src/sgml/html/ddl-priv.html
+++ b/doc/src/sgml/html/ddl-priv.html
@@ -1,5 +1,5 @@
-5.7. Privileges
When an object is created, it is assigned an owner. The
owner is normally the role that executed the creation statement.
For most kinds of objects, the initial state is that only the owner
@@ -311,4 +311,4 @@ GRANT SELECT (col1), UPDATE (col1) ON mytable TO miriam_rw;
Notice that the owner's implicit grant options are not marked in the
access privileges display. A * will appear only when
grant options have been explicitly granted to someone.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ddl-rowsecurity.html b/doc/src/sgml/html/ddl-rowsecurity.html
index f119529..77d5283 100644
--- a/doc/src/sgml/html/ddl-rowsecurity.html
+++ b/doc/src/sgml/html/ddl-rowsecurity.html
@@ -1,5 +1,5 @@
-5.8. Row Security Policies
In addition to the SQL-standard privilege
system available through GRANT,
tables can have row security policies that restrict,
@@ -379,4 +379,4 @@ SELECT * FROM information WHERE group_id = 2 FOR UPDATE;
\ No newline at end of file
diff --git a/doc/src/sgml/html/ddl-schemas.html b/doc/src/sgml/html/ddl-schemas.html
index 2a29b0d..9e4148a 100644
--- a/doc/src/sgml/html/ddl-schemas.html
+++ b/doc/src/sgml/html/ddl-schemas.html
@@ -1,5 +1,5 @@
-5.9. Schemas
A PostgreSQL database cluster contains
one or more named databases. Roles and a few other object types are
shared across the entire cluster. A client connection to the server
@@ -326,4 +326,4 @@ REVOKE CREATE ON SCHEMA public FROM PUBLIC;
limited) cross-database access. If you need to work with those
systems, then maximum portability would be achieved by not using
schemas at all.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ddl-system-columns.html b/doc/src/sgml/html/ddl-system-columns.html
index 67bf8bb..c0a8298 100644
--- a/doc/src/sgml/html/ddl-system-columns.html
+++ b/doc/src/sgml/html/ddl-system-columns.html
@@ -1,5 +1,5 @@
-5.5. System Columns
Every table has several system columns that are
implicitly defined by the system. Therefore, these names cannot be
used as names of user-defined columns. (Note that these
@@ -55,4 +55,4 @@
SQL commands, not the number of rows processed.
Also, only commands that actually modify the database contents will
consume a command identifier.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ddl.html b/doc/src/sgml/html/ddl.html
index 894714a..c64361d 100644
--- a/doc/src/sgml/html/ddl.html
+++ b/doc/src/sgml/html/ddl.html
@@ -1,5 +1,5 @@
-Chapter 5. Data Definition
This chapter covers how one creates the database structures that
will hold one's data. In a relational database, the raw data is
stored in tables, so the majority of this chapter is devoted to
@@ -10,4 +10,4 @@
we will briefly look at other features that affect the data storage,
such as inheritance, table partitioning, views, functions, and
triggers.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/default-roles.html b/doc/src/sgml/html/default-roles.html
index 2ac8ef0..89ab653 100644
--- a/doc/src/sgml/html/default-roles.html
+++ b/doc/src/sgml/html/default-roles.html
@@ -1,9 +1,9 @@
-O.2. Default Roles Renamed to Predefined Roles
PostgreSQL 13 and below used the term “Default Roles”. However, as these
roles are not able to actually be changed and are installed as part of the
system at initialization time, the more appropriate term to use is “Predefined Roles”.
See Section 22.5 for current documentation regarding
- Predefined Roles, and the release notes for
+ Predefined Roles, and the release notes for
PostgreSQL 14 for details on this change.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/dict-int.html b/doc/src/sgml/html/dict-int.html
index 2fccb86..ed0d36d 100644
--- a/doc/src/sgml/html/dict-int.html
+++ b/doc/src/sgml/html/dict-int.html
@@ -1,5 +1,5 @@
-F.13. dict_int
dict_int is an example of an add-on dictionary template
for full-text search. The motivation for this example dictionary is to
control the indexing of integers (signed and unsigned), allowing such
@@ -59,4 +59,4 @@ ALTER TEXT SEARCH CONFIGURATION english
ALTER MAPPING FOR int, uint WITH intdict;
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/dict-xsyn.html b/doc/src/sgml/html/dict-xsyn.html
index 96d8cad..dfc9243 100644
--- a/doc/src/sgml/html/dict-xsyn.html
+++ b/doc/src/sgml/html/dict-xsyn.html
@@ -1,5 +1,5 @@
-F.14. dict_xsyn
dict_xsyn (Extended Synonym Dictionary) is an example of an
add-on dictionary template for full-text search. This dictionary type
replaces words with groups of their synonyms, and so makes it possible to
@@ -94,4 +94,4 @@ ALTER TEXT SEARCH CONFIGURATION english
ALTER MAPPING FOR word, asciiword WITH xsyn, english_stem;
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/different-replication-solutions.html b/doc/src/sgml/html/different-replication-solutions.html
index d4eb03d..e7ca696 100644
--- a/doc/src/sgml/html/different-replication-solutions.html
+++ b/doc/src/sgml/html/different-replication-solutions.html
@@ -1,5 +1,5 @@
-27.1. Comparison of Different Solutions
Shared disk failover avoids synchronization overhead by having only one
copy of the database. It uses a single disk array that is shared by
multiple servers. If the main database server fails, the standby server
@@ -134,4 +134,4 @@
taken PostgreSQL and created commercial
closed-source solutions with unique failover, replication, and load
balancing capabilities. These are not discussed here.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/disk-full.html b/doc/src/sgml/html/disk-full.html
index 514f81f..642a3f7 100644
--- a/doc/src/sgml/html/disk-full.html
+++ b/doc/src/sgml/html/disk-full.html
@@ -1,5 +1,5 @@
-29.2. Disk Full Failure
The most important disk monitoring task of a database administrator
is to make sure the disk doesn't become full. A filled data disk will
not result in data corruption, but it might prevent useful activity
@@ -17,4 +17,4 @@
will naturally be subject to whatever quota is placed on the user
the server runs as. Exceeding the quota will have the same bad
effects as running out of disk space entirely.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/disk-usage.html b/doc/src/sgml/html/disk-usage.html
index 9f58475..11f7832 100644
--- a/doc/src/sgml/html/disk-usage.html
+++ b/doc/src/sgml/html/disk-usage.html
@@ -1,5 +1,5 @@
-29.1. Determining Disk Usage
Each table has a primary heap disk file where most of the data is
stored. If the table has any columns with potentially-wide values,
there also might be a TOAST file associated with the table,
@@ -80,4 +80,4 @@ ORDER BY relpages DESC;
bigtable | 3290
customer | 3144
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/diskusage.html b/doc/src/sgml/html/diskusage.html
index a790fb7..070a182 100644
--- a/doc/src/sgml/html/diskusage.html
+++ b/doc/src/sgml/html/diskusage.html
@@ -1,5 +1,5 @@
-Chapter 29. Monitoring Disk Usage
This chapter discusses how to monitor the disk usage of a
PostgreSQL database system.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/dml-delete.html b/doc/src/sgml/html/dml-delete.html
index 48a6038..48f58df 100644
--- a/doc/src/sgml/html/dml-delete.html
+++ b/doc/src/sgml/html/dml-delete.html
@@ -1,5 +1,5 @@
-6.3. Deleting Data
So far we have explained how to add data to tables and how to
change data. What remains is to discuss how to remove data that is
no longer needed. Just as adding data is only possible in whole
@@ -25,4 +25,4 @@ DELETE FROM products WHERE price = 10;
DELETE FROM products;
then all rows in the table will be deleted! Caveat programmer.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/dml-insert.html b/doc/src/sgml/html/dml-insert.html
index e578794..e5f22de 100644
--- a/doc/src/sgml/html/dml-insert.html
+++ b/doc/src/sgml/html/dml-insert.html
@@ -1,5 +1,5 @@
-6.1. Inserting Data
When a table is created, it contains no data. The first thing to
do before a database can be of much use is to insert data. Data is
inserted one row at a time. You can also insert more than one row
@@ -78,4 +78,4 @@ INSERT INTO products (product_no, name, price)
command, but is more efficient. Refer
to Section 14.4 for more information on improving
bulk loading performance.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/dml-returning.html b/doc/src/sgml/html/dml-returning.html
index 3ff5d5a..24409ca 100644
--- a/doc/src/sgml/html/dml-returning.html
+++ b/doc/src/sgml/html/dml-returning.html
@@ -1,5 +1,5 @@
-6.4. Returning Data from Modified Rows
Sometimes it is useful to obtain data from modified rows while they are
being manipulated. The INSERT, UPDATE,
and DELETE commands all have an
@@ -50,4 +50,4 @@ DELETE FROM products
the data available to RETURNING is the row as modified by
the triggers. Thus, inspecting columns computed by triggers is another
common use-case for RETURNING.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/dml-update.html b/doc/src/sgml/html/dml-update.html
index c08a771..62643cb 100644
--- a/doc/src/sgml/html/dml-update.html
+++ b/doc/src/sgml/html/dml-update.html
@@ -1,5 +1,5 @@
-6.2. Updating Data
The modification of data that is already in the database is
referred to as updating. You can update individual rows, all the
rows in a table, or a subset of all rows. Each column can be
@@ -58,4 +58,4 @@ UPDATE products SET price = price * 1.10;
UPDATE mytable SET a = 5, b = 3, c = 1 WHERE a > 0;
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/dml.html b/doc/src/sgml/html/dml.html
index 0341892..ca7aa80 100644
--- a/doc/src/sgml/html/dml.html
+++ b/doc/src/sgml/html/dml.html
@@ -1,9 +1,9 @@
-Chapter 6. Data Manipulation
The previous chapter discussed how to create tables and other
structures to hold your data. Now it is time to fill the tables
with data. This chapter covers how to insert, update, and delete
table data. The chapter
after this will finally explain how to extract your long-lost data
from the database.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/docguide-authoring.html b/doc/src/sgml/html/docguide-authoring.html
index dcf94c6..65601d0 100644
--- a/doc/src/sgml/html/docguide-authoring.html
+++ b/doc/src/sgml/html/docguide-authoring.html
@@ -1,5 +1,5 @@
-J.4. Documentation Authoring
The documentation sources are most conveniently modified with an editor
that has a mode for editing XML, and even more so if it has some awareness
of XML schema languages so that it can know about
@@ -20,4 +20,4 @@
src/tools/editors/emacs.samples contains
recommended settings for this mode.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/docguide-build.html b/doc/src/sgml/html/docguide-build.html
index ffb8bee..1f1c5cd 100644
--- a/doc/src/sgml/html/docguide-build.html
+++ b/doc/src/sgml/html/docguide-build.html
@@ -1,5 +1,5 @@
-J.3. Building the Documentation
Once you have everything set up, change to the directory
doc/src/sgml and run one of the commands
described in the following subsections to build the
@@ -88,4 +88,4 @@ ADDITIONAL_FLAGS='-Xmx1500m'
doc/src/sgml$ make check
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/docguide-docbook.html b/doc/src/sgml/html/docguide-docbook.html
index 7d92851..151a975 100644
--- a/doc/src/sgml/html/docguide-docbook.html
+++ b/doc/src/sgml/html/docguide-docbook.html
@@ -1,5 +1,5 @@
-J.1. DocBook
The documentation sources are written in
DocBook, which is a markup language
defined in XML. In what
@@ -20,4 +20,4 @@
FreeBSD Documentation Project also uses DocBook and has some good
information, including a number of style guidelines that might be
worth considering.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/docguide-style.html b/doc/src/sgml/html/docguide-style.html
index 5257714..7b592b1 100644
--- a/doc/src/sgml/html/docguide-style.html
+++ b/doc/src/sgml/html/docguide-style.html
@@ -1,5 +1,5 @@
-J.5. Style Guide
Reference pages should follow a standard layout. This allows
users to find the desired information more quickly, and it also
encourages writers to document all relevant aspects of a command.
@@ -86,4 +86,4 @@
database system it is compatible. The See Also section of SQL
commands should list SQL commands before cross-references to
programs.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/docguide-toolsets.html b/doc/src/sgml/html/docguide-toolsets.html
index 6facf81..28b727b 100644
--- a/doc/src/sgml/html/docguide-toolsets.html
+++ b/doc/src/sgml/html/docguide-toolsets.html
@@ -1,5 +1,5 @@
-J.2. Tool Sets
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/docguide.html b/doc/src/sgml/html/docguide.html
index 727d474..e691d01 100644
--- a/doc/src/sgml/html/docguide.html
+++ b/doc/src/sgml/html/docguide.html
@@ -1,5 +1,5 @@
-Appendix J. Documentation
PostgreSQL has four primary documentation
formats:
@@ -21,4 +21,4 @@
standard distribution and are installed by default. PDF
format documentation is available separately for
download.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/domains.html b/doc/src/sgml/html/domains.html
index fa56076..e61674d 100644
--- a/doc/src/sgml/html/domains.html
+++ b/doc/src/sgml/html/domains.html
@@ -1,5 +1,5 @@
-8.18. Domain Types
A domain is a user-defined data type that is
based on another underlying type. Optionally,
it can have constraints that restrict its valid values to a subset of
@@ -31,4 +31,4 @@ INSERT INTO mytable VALUES(-1); -- fails
domain's constraints will be checked.
\ No newline at end of file
diff --git a/doc/src/sgml/html/dynamic-trace.html b/doc/src/sgml/html/dynamic-trace.html
index 9f1b1c7..4196a9c 100644
--- a/doc/src/sgml/html/dynamic-trace.html
+++ b/doc/src/sgml/html/dynamic-trace.html
@@ -1,5 +1,5 @@
-28.5. Dynamic Tracing
PostgreSQL provides facilities to support
dynamic tracing of the database server. This allows an external
utility to be called at specific points in the code and thereby trace
@@ -298,4 +298,4 @@ if (TRACE_POSTGRESQL_TRANSACTION_START_ENABLED())
Each trace macro has a corresponding ENABLED macro.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/earthdistance.html b/doc/src/sgml/html/earthdistance.html
index 55206f0..92b4afb 100644
--- a/doc/src/sgml/html/earthdistance.html
+++ b/doc/src/sgml/html/earthdistance.html
@@ -1,5 +1,5 @@
-F.15. earthdistance
The earthdistance module provides two different approaches to
calculating great circle distances on the surface of the Earth. The one
described first depends on the cube module.
@@ -155,4 +155,4 @@
you need to be careful about the edge conditions near the poles
and near +/- 180 degrees of longitude. The cube-based
representation avoids these discontinuities.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-commands.html b/doc/src/sgml/html/ecpg-commands.html
index 82ace84..a18f8aa 100644
--- a/doc/src/sgml/html/ecpg-commands.html
+++ b/doc/src/sgml/html/ecpg-commands.html
@@ -1,5 +1,5 @@
-36.3. Running SQL Commands
Any SQL command can be run from within an embedded SQL application.
Below are some examples of how to do that.
36.3.1. Executing SQL Statements
@@ -160,4 +160,4 @@ EXEC SQL DEALLOCATE PREPARE name;
see PREPARE. Also
see Section 36.5 for more details about using
placeholders and input parameters.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-concept.html b/doc/src/sgml/html/ecpg-concept.html
index 04e5164..588ddd1 100644
--- a/doc/src/sgml/html/ecpg-concept.html
+++ b/doc/src/sgml/html/ecpg-concept.html
@@ -1,5 +1,5 @@
-36.1. The Concept
An embedded SQL program consists of code written in an ordinary
programming language, in this case C, mixed with SQL commands in
specially marked sections. To build the program, the source code (*.pgc)
@@ -49,4 +49,4 @@ EXEC SQL ...;
Of course, the C part of the program follows C quoting rules.
The following sections explain all the embedded SQL statements.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-connect.html b/doc/src/sgml/html/ecpg-connect.html
index 3728bd8..f5f3eb0 100644
--- a/doc/src/sgml/html/ecpg-connect.html
+++ b/doc/src/sgml/html/ecpg-connect.html
@@ -1,5 +1,5 @@
-36.2. Managing Database Connections
This section describes how to open, close, and switch database
connections.
36.2.1. Connecting to the Database Server
@@ -244,4 +244,4 @@ EXEC SQL DISCONNECT [connec
It is good style that an application always explicitly disconnect
from every connection it opened.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-cpp.html b/doc/src/sgml/html/ecpg-cpp.html
index 242bd59..7a46019 100644
--- a/doc/src/sgml/html/ecpg-cpp.html
+++ b/doc/src/sgml/html/ecpg-cpp.html
@@ -1,5 +1,5 @@
-36.13. C++ Applications
ECPG has some limited support for C++ applications. This section
describes some caveats.
@@ -225,4 +225,4 @@ c++ -c test_cpp.cpp -o test_cpp.o
c++ test_cpp.o test_mod.o -lecpg -o test_cpp
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-descriptors.html b/doc/src/sgml/html/ecpg-descriptors.html
index f0a452b..23b05e8 100644
--- a/doc/src/sgml/html/ecpg-descriptors.html
+++ b/doc/src/sgml/html/ecpg-descriptors.html
@@ -1,5 +1,5 @@
-36.7. Using Descriptor Areas
An SQL descriptor area is a more sophisticated method for processing
the result of a SELECT, FETCH or
a DESCRIBE statement. An SQL descriptor area groups
@@ -707,4 +707,4 @@ tup_fetched = 3253694 (type: 9)
tup_inserted = 0 (type: 9)
tup_updated = 0 (type: 9)
tup_deleted = 0 (type: 9)
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-develop.html b/doc/src/sgml/html/ecpg-develop.html
index 7d0aa69..ee8fecc 100644
--- a/doc/src/sgml/html/ecpg-develop.html
+++ b/doc/src/sgml/html/ecpg-develop.html
@@ -1,5 +1,5 @@
-36.17. Internals
This section explains how ECPG works
internally. This information can occasionally be useful to help
users understand how to use ECPG.
@@ -121,4 +121,4 @@ ECPGdo(__LINE__, NULL, "SELECT res FROM mytable WHERE index = ? ",
(The indentation here is added for readability and not
something the preprocessor does.)
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-dynamic.html b/doc/src/sgml/html/ecpg-dynamic.html
index 9ce0c74..4ca263f 100644
--- a/doc/src/sgml/html/ecpg-dynamic.html
+++ b/doc/src/sgml/html/ecpg-dynamic.html
@@ -1,5 +1,5 @@
-36.5. Dynamic SQL
In many cases, the particular SQL statements that an application
has to execute are known at the time the application is written.
In some cases, however, the SQL statements are composed at run time
@@ -100,4 +100,4 @@ EXEC SQL CLOSE cursor1;
EXEC SQL COMMIT;
EXEC SQL DISCONNECT ALL;
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-errors.html b/doc/src/sgml/html/ecpg-errors.html
index 02caf51..0589152 100644
--- a/doc/src/sgml/html/ecpg-errors.html
+++ b/doc/src/sgml/html/ecpg-errors.html
@@ -1,5 +1,5 @@
-36.8. Error Handling
This section describes how you can handle exceptional conditions
and warnings in an embedded SQL program. There are two
nonexclusive facilities for this.
@@ -438,4 +438,4 @@ while (1)
-605 (ECPG_WARNING_PORTAL_EXISTS)
An existing cursor name was specified. (SQLSTATE 42P03)
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-informix-compat.html b/doc/src/sgml/html/ecpg-informix-compat.html
index a6cc793..7f6ca79 100644
--- a/doc/src/sgml/html/ecpg-informix-compat.html
+++ b/doc/src/sgml/html/ecpg-informix-compat.html
@@ -1,5 +1,5 @@
-36.15. Informix Compatibility Mode
ecpg can be run in a so-called Informix compatibility mode. If
this mode is active, it tries to behave as if it were the Informix
precompiler for Informix E/SQL. Generally spoken this will allow you to use
@@ -388,7 +388,7 @@ int dectodbl(decimal *np, double *dblp);
On success, 0 is returned and a negative value if the conversion
failed.
dectoint
- Convert a variable to type decimal to an integer.
+ Convert a variable of type decimal to an integer.
int dectoint(decimal *np, int *ip);
@@ -405,7 +405,7 @@ int dectoint(decimal *np, int *ip);
32767, while the limits in the ECPG implementation depend on the
architecture (INT_MIN .. INT_MAX).
dectolong
- Convert a variable to type decimal to a long integer.
+ Convert a variable of type decimal to a long integer.
int dectolong(decimal *np, long *lngp);
@@ -889,4 +889,4 @@ risnull(CINTTYPE, (char *) &i);
characters it cannot parse. Internally it is defined as -1264 (the
Informix definition).
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-library.html b/doc/src/sgml/html/ecpg-library.html
index 66a9a05..79a243d 100644
--- a/doc/src/sgml/html/ecpg-library.html
+++ b/doc/src/sgml/html/ecpg-library.html
@@ -1,5 +1,5 @@
-36.11. Library Functions
The libecpg library primarily contains
“hidden” functions that are used to implement the
functionality expressed by the embedded SQL commands. But there
@@ -43,4 +43,4 @@
returns true if you are connected to a database and false if not.
connection_name can be NULL
if a single connection is being used.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-lo.html b/doc/src/sgml/html/ecpg-lo.html
index 4cf471b..bc0c8dc 100644
--- a/doc/src/sgml/html/ecpg-lo.html
+++ b/doc/src/sgml/html/ecpg-lo.html
@@ -1,5 +1,5 @@
-36.12. Large Objects
Large objects are not directly supported by ECPG, but ECPG
application can manipulate large objects through the libpq large
object functions, obtaining the necessary PGconn
@@ -97,4 +97,4 @@ main(void)
EXEC SQL DISCONNECT ALL;
return 0;
}
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-oracle-compat.html b/doc/src/sgml/html/ecpg-oracle-compat.html
index b4bc14a..a3bcbba 100644
--- a/doc/src/sgml/html/ecpg-oracle-compat.html
+++ b/doc/src/sgml/html/ecpg-oracle-compat.html
@@ -1,5 +1,5 @@
-36.16. Oracle Compatibility Mode
ecpg can be run in a so-called Oracle
compatibility mode. If this mode is active, it tries to
behave as if it were Oracle Pro*C.
@@ -16,4 +16,4 @@
Set the null indicator to -1 when character
arrays receive empty character string types
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-pgtypes.html b/doc/src/sgml/html/ecpg-pgtypes.html
index abeded5..1d51c3d 100644
--- a/doc/src/sgml/html/ecpg-pgtypes.html
+++ b/doc/src/sgml/html/ecpg-pgtypes.html
@@ -1,5 +1,5 @@
-36.6. pgtypes Library
The pgtypes library maps PostgreSQL database
types to C equivalents that can be used in C programs. It also offers
functions to do basic calculations with those types within C, i.e., without
@@ -564,7 +564,7 @@ int PGTYPEStimestamp_fmt_asc(timestamp *ts, char *output, int str_len, char *fmt
%z - is replaced by the time zone offset from
UTC; a leading plus sign stands for east of UTC, a minus sign for
west of UTC, hours and minutes follow with two digits each and no
- delimiter between them (common form for RFC 822 date headers).
+ delimiter between them (common form for RFC 822 date headers).
%+ - is replaced by national representation of
the date and time.
@@ -762,4 +762,4 @@ void PGTYPESdecimal_free(decimal *var);
errno != 0 after each call to
PGTYPEStimestamp_from_asc.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-preproc.html b/doc/src/sgml/html/ecpg-preproc.html
index d46411d..dd43db6 100644
--- a/doc/src/sgml/html/ecpg-preproc.html
+++ b/doc/src/sgml/html/ecpg-preproc.html
@@ -1,5 +1,5 @@
-36.9. Preprocessor Directives
Several preprocessor directives are available that modify how
the ecpg preprocessor parses and processes a
file.
@@ -77,6 +77,12 @@ EXEC SQL UPDATE Tbl SET col = MYNUMBER;
#define for a constant that you are going to use in an
embedded SQL query because in this case the embedded SQL precompiler is not
able to see this declaration.
+
+ If multiple input files are named on the ecpg
+ preprocessor's command line, the effects of EXEC SQL
+ DEFINE and EXEC SQL UNDEF do not carry
+ across files: each file starts with only the symbols defined
+ by -D switches on the command line.
36.9.3. ifdef, ifndef, elif, else, and endif Directives
You can use the following directives to compile code sections conditionally:
@@ -126,4 +132,4 @@ EXEC SQL else;
EXEC SQL SET TIMEZONE TO 'GMT';
EXEC SQL endif;
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-process.html b/doc/src/sgml/html/ecpg-process.html
index 81c376d..ae7e405 100644
--- a/doc/src/sgml/html/ecpg-process.html
+++ b/doc/src/sgml/html/ecpg-process.html
@@ -1,5 +1,5 @@
-36.10. Processing Embedded SQL Programs
Now that you have an idea how to form embedded SQL C programs, you
probably want to know how to compile them. Before compiling you
run the file through the embedded SQL
@@ -65,4 +65,4 @@ ECPG = ecpg
The ecpg library is thread-safe by
default. However, you might need to use some threading
command-line options to compile your client code.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-sql-allocate-descriptor.html b/doc/src/sgml/html/ecpg-sql-allocate-descriptor.html
index f6d1b23..1306468 100644
--- a/doc/src/sgml/html/ecpg-sql-allocate-descriptor.html
+++ b/doc/src/sgml/html/ecpg-sql-allocate-descriptor.html
@@ -1,5 +1,5 @@
-ALLOCATE DESCRIPTOR
WHENEVER — specify the action to be taken when an SQL statement causes a specific class condition to be raised
This section describes all SQL commands that are specific to
embedded SQL. Also refer to the SQL commands listed
in SQL Commands, which can also be used in
embedded SQL, unless stated otherwise.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-sql-connect.html b/doc/src/sgml/html/ecpg-sql-connect.html
index 99efc30..12cec00 100644
--- a/doc/src/sgml/html/ecpg-sql-connect.html
+++ b/doc/src/sgml/html/ecpg-sql-connect.html
@@ -1,5 +1,5 @@
-CONNECT
CONNECT TO connection_target [ AS connection_name ] [ USER connection_user ]
CONNECT TO DEFAULT
CONNECT connection_user
@@ -106,4 +106,4 @@ EXEC SQL END DECLARE SECTION;
CONNECT is specified in the SQL standard, but
the format of the connection parameters is
implementation-specific.
-
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-sql-deallocate-descriptor.html b/doc/src/sgml/html/ecpg-sql-deallocate-descriptor.html
index 8a2db13..2ea4b2e 100644
--- a/doc/src/sgml/html/ecpg-sql-deallocate-descriptor.html
+++ b/doc/src/sgml/html/ecpg-sql-deallocate-descriptor.html
@@ -1,5 +1,5 @@
-DEALLOCATE DESCRIPTOR
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-sql-declare-statement.html b/doc/src/sgml/html/ecpg-sql-declare-statement.html
index f3a29f3..b4e475f 100644
--- a/doc/src/sgml/html/ecpg-sql-declare-statement.html
+++ b/doc/src/sgml/html/ecpg-sql-declare-statement.html
@@ -1,5 +1,5 @@
-DECLARE STATEMENT
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-sql-declare.html b/doc/src/sgml/html/ecpg-sql-declare.html
index b2e2080..5e05c8c 100644
--- a/doc/src/sgml/html/ecpg-sql-declare.html
+++ b/doc/src/sgml/html/ecpg-sql-declare.html
@@ -1,5 +1,5 @@
-DECLARE
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-sql-describe.html b/doc/src/sgml/html/ecpg-sql-describe.html
index f784d9d..340fed9 100644
--- a/doc/src/sgml/html/ecpg-sql-describe.html
+++ b/doc/src/sgml/html/ecpg-sql-describe.html
@@ -1,5 +1,5 @@
-DESCRIBE
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-sql-disconnect.html b/doc/src/sgml/html/ecpg-sql-disconnect.html
index b51aa77..aab33e3 100644
--- a/doc/src/sgml/html/ecpg-sql-disconnect.html
+++ b/doc/src/sgml/html/ecpg-sql-disconnect.html
@@ -1,5 +1,5 @@
-DISCONNECT
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-sql-execute-immediate.html b/doc/src/sgml/html/ecpg-sql-execute-immediate.html
index 3aa521a..5c7b181 100644
--- a/doc/src/sgml/html/ecpg-sql-execute-immediate.html
+++ b/doc/src/sgml/html/ecpg-sql-execute-immediate.html
@@ -1,5 +1,5 @@
-EXECUTE IMMEDIATE
EXECUTE IMMEDIATE is specified in the SQL standard.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-sql-get-descriptor.html b/doc/src/sgml/html/ecpg-sql-get-descriptor.html
index ec402e9..f54a62e 100644
--- a/doc/src/sgml/html/ecpg-sql-get-descriptor.html
+++ b/doc/src/sgml/html/ecpg-sql-get-descriptor.html
@@ -1,5 +1,5 @@
-GET DESCRIPTOR
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-sql-open.html b/doc/src/sgml/html/ecpg-sql-open.html
index 5cf0669..a893649 100644
--- a/doc/src/sgml/html/ecpg-sql-open.html
+++ b/doc/src/sgml/html/ecpg-sql-open.html
@@ -1,5 +1,5 @@
-OPEN
OPEN cursor_name
OPEN cursor_name USING value [, ... ]
OPEN cursor_name USING SQL DESCRIPTOR descriptor_name
@@ -28,4 +28,4 @@ EXEC SQL OPEN c1 USING SQL DESCRIPTOR mydesc;
EXEC SQL OPEN :curname1;
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-sql-prepare.html b/doc/src/sgml/html/ecpg-sql-prepare.html
index 9f4dba9..ce31d24 100644
--- a/doc/src/sgml/html/ecpg-sql-prepare.html
+++ b/doc/src/sgml/html/ecpg-sql-prepare.html
@@ -1,5 +1,5 @@
-PREPARE
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-sql-set-autocommit.html b/doc/src/sgml/html/ecpg-sql-set-autocommit.html
index 1eb449c..2798171 100644
--- a/doc/src/sgml/html/ecpg-sql-set-autocommit.html
+++ b/doc/src/sgml/html/ecpg-sql-set-autocommit.html
@@ -1,5 +1,5 @@
-SET AUTOCOMMIT
SET AUTOCOMMIT — set the autocommit behavior of the current session
Synopsis
SET AUTOCOMMIT { = | TO } { ON | OFF }
Description
SET AUTOCOMMIT sets the autocommit behavior of
@@ -10,4 +10,4 @@ SET AUTOCOMMIT { = | TO } { ON | OFF }
where each individual statement is committed implicitly.
Compatibility
SET AUTOCOMMIT is an extension of PostgreSQL ECPG.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-sql-set-connection.html b/doc/src/sgml/html/ecpg-sql-set-connection.html
index d0e4746..d58c7a5 100644
--- a/doc/src/sgml/html/ecpg-sql-set-connection.html
+++ b/doc/src/sgml/html/ecpg-sql-set-connection.html
@@ -1,5 +1,5 @@
-SET CONNECTION
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-sql-set-descriptor.html b/doc/src/sgml/html/ecpg-sql-set-descriptor.html
index 44b06b9..37b493c 100644
--- a/doc/src/sgml/html/ecpg-sql-set-descriptor.html
+++ b/doc/src/sgml/html/ecpg-sql-set-descriptor.html
@@ -1,5 +1,5 @@
-SET DESCRIPTOR
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-sql-type.html b/doc/src/sgml/html/ecpg-sql-type.html
index b10af95..7da593c 100644
--- a/doc/src/sgml/html/ecpg-sql-type.html
+++ b/doc/src/sgml/html/ecpg-sql-type.html
@@ -1,5 +1,5 @@
-TYPE
The TYPE command defines a new C type. It is
@@ -85,4 +85,4 @@ t_ind.i_ind = 0
Compatibility
The TYPE command is a PostgreSQL extension.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-sql-var.html b/doc/src/sgml/html/ecpg-sql-var.html
index c43580e..5656465 100644
--- a/doc/src/sgml/html/ecpg-sql-var.html
+++ b/doc/src/sgml/html/ecpg-sql-var.html
@@ -1,5 +1,5 @@
-VAR
The VAR command assigns a new C data type
@@ -16,4 +16,4 @@ exec sql end declare section;
EXEC SQL VAR a IS int;
Compatibility
The VAR command is a PostgreSQL extension.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-sql-whenever.html b/doc/src/sgml/html/ecpg-sql-whenever.html
index bccda8a..9bd4e9a 100644
--- a/doc/src/sgml/html/ecpg-sql-whenever.html
+++ b/doc/src/sgml/html/ecpg-sql-whenever.html
@@ -1,5 +1,5 @@
-WHENEVER
WHENEVER — specify the action to be taken when an SQL statement causes a specific class condition to be raised
Synopsis
WHENEVER { NOT FOUND | SQLERROR | SQLWARNING } action
Description
Define a behavior which is called on the special cases (Rows not
@@ -54,4 +54,4 @@ main(void)
Compatibility
WHENEVER is specified in the SQL standard, but
most of the actions are PostgreSQL extensions.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg-variables.html b/doc/src/sgml/html/ecpg-variables.html
index a0e86d3..4ac2e14 100644
--- a/doc/src/sgml/html/ecpg-variables.html
+++ b/doc/src/sgml/html/ecpg-variables.html
@@ -1,5 +1,5 @@
-36.4. Using Host Variables
In Section 36.3 you saw how you can execute SQL
statements from an embedded SQL program. Some of those statements
only used fixed values and did not provide a way to insert
@@ -878,4 +878,4 @@ EXEC SQL SELECT b INTO :val :val_ind FROM test1;
input and output) for character string types as empty string and
for integer types as the lowest possible value for type (for
example, INT_MIN for int).
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/ecpg.html b/doc/src/sgml/html/ecpg.html
index aa8e833..9cf5778 100644
--- a/doc/src/sgml/html/ecpg.html
+++ b/doc/src/sgml/html/ecpg.html
@@ -1,5 +1,5 @@
-Chapter 36. ECPG — Embedded SQL in C
This chapter describes the embedded SQL package
for PostgreSQL. It was written by
Linus Tolke (<linus@epact.se>) and Michael Meskes
@@ -10,4 +10,4 @@
This documentation is quite incomplete. But since this
interface is standardized, additional information can be found in
many resources about SQL.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/encryption-options.html b/doc/src/sgml/html/encryption-options.html
index d6d9b2f..3c3f774 100644
--- a/doc/src/sgml/html/encryption-options.html
+++ b/doc/src/sgml/html/encryption-options.html
@@ -1,5 +1,5 @@
-19.8. Encryption Options
PostgreSQL offers encryption at several
levels, and provides flexibility in protecting data from disclosure
due to database server theft, unscrupulous administrators, and
@@ -81,4 +81,4 @@
never appears on the database server. Data is encrypted on the
client before being sent to the server, and database results have
to be decrypted on the client before being used.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/errcodes-appendix.html b/doc/src/sgml/html/errcodes-appendix.html
index 0b15510..082d558 100644
--- a/doc/src/sgml/html/errcodes-appendix.html
+++ b/doc/src/sgml/html/errcodes-appendix.html
@@ -1,5 +1,5 @@
-Appendix A. PostgreSQL Error Codes
All messages emitted by the PostgreSQL
server are assigned five-character error codes that follow the SQL
standard's conventions for “SQLSTATE” codes. Applications
@@ -20,7 +20,7 @@
what to do from the error class.
Table A.1 lists all the error codes defined in
- PostgreSQL 15.6. (Some are not actually
+ PostgreSQL 15.7. (Some are not actually
used at present, but are defined by the SQL standard.)
The error classes are also shown. For each error class there is a
“standard” error code having the last three characters
@@ -42,4 +42,4 @@
As of PostgreSQL 9.3, complete coverage for this feature
exists only for errors in SQLSTATE class 23 (integrity constraint
violation), but this is likely to be expanded in future.
-
Table A.1. PostgreSQL Error Codes
Error Code
Condition Name
Class 00 — Successful Completion
00000
successful_completion
Class 01 — Warning
01000
warning
0100C
dynamic_result_sets_returned
01008
implicit_zero_bit_padding
01003
null_value_eliminated_in_set_function
01007
privilege_not_granted
01006
privilege_not_revoked
01004
string_data_right_truncation
01P01
deprecated_feature
Class 02 — No Data (this is also a warning class per the SQL standard)
Class 2B — Dependent Privilege Descriptors Still Exist
2B000
dependent_privilege_descriptors_still_exist
2BP01
dependent_objects_still_exist
Class 2D — Invalid Transaction Termination
2D000
invalid_transaction_termination
Class 2F — SQL Routine Exception
2F000
sql_routine_exception
2F005
function_executed_no_return_statement
2F002
modifying_sql_data_not_permitted
2F003
prohibited_sql_statement_attempted
2F004
reading_sql_data_not_permitted
Class 34 — Invalid Cursor Name
34000
invalid_cursor_name
Class 38 — External Routine Exception
38000
external_routine_exception
38001
containing_sql_not_permitted
38002
modifying_sql_data_not_permitted
38003
prohibited_sql_statement_attempted
38004
reading_sql_data_not_permitted
Class 39 — External Routine Invocation Exception
39000
external_routine_invocation_exception
39001
invalid_sqlstate_returned
39004
null_value_not_allowed
39P01
trigger_protocol_violated
39P02
srf_protocol_violated
39P03
event_trigger_protocol_violated
Class 3B — Savepoint Exception
3B000
savepoint_exception
3B001
invalid_savepoint_specification
Class 3D — Invalid Catalog Name
3D000
invalid_catalog_name
Class 3F — Invalid Schema Name
3F000
invalid_schema_name
Class 40 — Transaction Rollback
40000
transaction_rollback
40002
transaction_integrity_constraint_violation
40001
serialization_failure
40003
statement_completion_unknown
40P01
deadlock_detected
Class 42 — Syntax Error or Access Rule Violation
42000
syntax_error_or_access_rule_violation
42601
syntax_error
42501
insufficient_privilege
42846
cannot_coerce
42803
grouping_error
42P20
windowing_error
42P19
invalid_recursion
42830
invalid_foreign_key
42602
invalid_name
42622
name_too_long
42939
reserved_name
42804
datatype_mismatch
42P18
indeterminate_datatype
42P21
collation_mismatch
42P22
indeterminate_collation
42809
wrong_object_type
428C9
generated_always
42703
undefined_column
42883
undefined_function
42P01
undefined_table
42P02
undefined_parameter
42704
undefined_object
42701
duplicate_column
42P03
duplicate_cursor
42P04
duplicate_database
42723
duplicate_function
42P05
duplicate_prepared_statement
42P06
duplicate_schema
42P07
duplicate_table
42712
duplicate_alias
42710
duplicate_object
42702
ambiguous_column
42725
ambiguous_function
42P08
ambiguous_parameter
42P09
ambiguous_alias
42P10
invalid_column_reference
42611
invalid_column_definition
42P11
invalid_cursor_definition
42P12
invalid_database_definition
42P13
invalid_function_definition
42P14
invalid_prepared_statement_definition
42P15
invalid_schema_definition
42P16
invalid_table_definition
42P17
invalid_object_definition
Class 44 — WITH CHECK OPTION Violation
44000
with_check_option_violation
Class 53 — Insufficient Resources
53000
insufficient_resources
53100
disk_full
53200
out_of_memory
53300
too_many_connections
53400
configuration_limit_exceeded
Class 54 — Program Limit Exceeded
54000
program_limit_exceeded
54001
statement_too_complex
54011
too_many_columns
54023
too_many_arguments
Class 55 — Object Not In Prerequisite State
55000
object_not_in_prerequisite_state
55006
object_in_use
55P02
cant_change_runtime_param
55P03
lock_not_available
55P04
unsafe_new_enum_value_usage
Class 57 — Operator Intervention
57000
operator_intervention
57014
query_canceled
57P01
admin_shutdown
57P02
crash_shutdown
57P03
cannot_connect_now
57P04
database_dropped
57P05
idle_session_timeout
Class 58 — System Error (errors external to PostgreSQL itself)
58000
system_error
58030
io_error
58P01
undefined_file
58P02
duplicate_file
Class 72 — Snapshot Failure
72000
snapshot_too_old
Class F0 — Configuration File Error
F0000
config_file_error
F0001
lock_file_exists
Class HV — Foreign Data Wrapper Error (SQL/MED)
HV000
fdw_error
HV005
fdw_column_name_not_found
HV002
fdw_dynamic_parameter_value_needed
HV010
fdw_function_sequence_error
HV021
fdw_inconsistent_descriptor_information
HV024
fdw_invalid_attribute_value
HV007
fdw_invalid_column_name
HV008
fdw_invalid_column_number
HV004
fdw_invalid_data_type
HV006
fdw_invalid_data_type_descriptors
HV091
fdw_invalid_descriptor_field_identifier
HV00B
fdw_invalid_handle
HV00C
fdw_invalid_option_index
HV00D
fdw_invalid_option_name
HV090
fdw_invalid_string_length_or_buffer_length
HV00A
fdw_invalid_string_format
HV009
fdw_invalid_use_of_null_pointer
HV014
fdw_too_many_handles
HV001
fdw_out_of_memory
HV00P
fdw_no_schemas
HV00J
fdw_option_name_not_found
HV00K
fdw_reply_handle
HV00Q
fdw_schema_not_found
HV00R
fdw_table_not_found
HV00L
fdw_unable_to_create_execution
HV00M
fdw_unable_to_create_reply
HV00N
fdw_unable_to_establish_connection
Class P0 — PL/pgSQL Error
P0000
plpgsql_error
P0001
raise_exception
P0002
no_data_found
P0003
too_many_rows
P0004
assert_failure
Class XX — Internal Error
XX000
internal_error
XX001
data_corrupted
XX002
index_corrupted
\ No newline at end of file
diff --git a/doc/src/sgml/html/error-message-reporting.html b/doc/src/sgml/html/error-message-reporting.html
index b0e42dc..612044c 100644
--- a/doc/src/sgml/html/error-message-reporting.html
+++ b/doc/src/sgml/html/error-message-reporting.html
@@ -1,5 +1,5 @@
-56.2. Reporting Errors Within the Server
Error, warning, and log messages generated within the server code
should be created using ereport, or its older cousin
elog. The use of this function is complex enough to
@@ -247,4 +247,4 @@ ereport(level, errmsg_internal("format string", ...));
routines will not affect it. That would not be true if you were to
write strerror(errno) explicitly in errmsg's
parameter list; accordingly, do not do so.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/error-style-guide.html b/doc/src/sgml/html/error-style-guide.html
index 03bf135..e5cd23a 100644
--- a/doc/src/sgml/html/error-style-guide.html
+++ b/doc/src/sgml/html/error-style-guide.html
@@ -1,5 +1,5 @@
-56.3. Error Message Style Guide
This style guide is offered in the hope of maintaining a consistent,
user-friendly style throughout all the messages generated by
PostgreSQL.
@@ -247,4 +247,4 @@ BETTER: unrecognized node type: 42
Keep in mind that error message texts need to be translated into other
languages. Follow the guidelines in Section 57.2.2
to avoid making life difficult for translators.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/event-log-registration.html b/doc/src/sgml/html/event-log-registration.html
index a1d2194..6d73266 100644
--- a/doc/src/sgml/html/event-log-registration.html
+++ b/doc/src/sgml/html/event-log-registration.html
@@ -1,5 +1,5 @@
-19.12. Registering Event Log on Windows
To register a Windowsevent log library with the operating system,
issue this command:
@@ -25,4 +25,4 @@
To enable event logging in the database server, modify
log_destination to include
eventlog in postgresql.conf.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/event-trigger-definition.html b/doc/src/sgml/html/event-trigger-definition.html
index 157311e..27d8c80 100644
--- a/doc/src/sgml/html/event-trigger-definition.html
+++ b/doc/src/sgml/html/event-trigger-definition.html
@@ -1,5 +1,5 @@
-40.1. Overview of Event Trigger Behavior
An event trigger fires whenever the event with which it is associated
occurs in the database in which it is defined. Currently, the only
supported events are
@@ -75,4 +75,4 @@
trigger can be fired only for particular commands which the user wishes
to intercept. A common use of such triggers is to restrict the range of
DDL operations which users may perform.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/event-trigger-example.html b/doc/src/sgml/html/event-trigger-example.html
index a0be26e..6bfbc7e 100644
--- a/doc/src/sgml/html/event-trigger-example.html
+++ b/doc/src/sgml/html/event-trigger-example.html
@@ -1,5 +1,5 @@
-40.4. A Complete Event Trigger Example
Here is a very simple example of an event trigger function written in C.
(Examples of triggers written in procedural languages can be found in
the documentation of the procedural languages.)
@@ -75,4 +75,4 @@ COMMIT;
(Recall that DDL commands on event triggers themselves are not affected by
event triggers.)
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/event-trigger-interface.html b/doc/src/sgml/html/event-trigger-interface.html
index e047c2b..7bfe3fc 100644
--- a/doc/src/sgml/html/event-trigger-interface.html
+++ b/doc/src/sgml/html/event-trigger-interface.html
@@ -1,5 +1,5 @@
-40.3. Writing Event Trigger Functions in C
This section describes the low-level details of the interface to an
event trigger function. This information is only needed when writing
event trigger functions in C. If you are using a higher-level language
@@ -65,4 +65,4 @@ typedef struct EventTriggerData
An event trigger function must return a NULL pointer
(not an SQL null value, that is, do not
set isNull true).
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/event-trigger-matrix.html b/doc/src/sgml/html/event-trigger-matrix.html
index 909298d..25b9520 100644
--- a/doc/src/sgml/html/event-trigger-matrix.html
+++ b/doc/src/sgml/html/event-trigger-matrix.html
@@ -1,5 +1,5 @@
-40.2. Event Trigger Firing Matrix
Table 40.1 lists all commands
for which event triggers are supported.
-
Table 40.1. Event Trigger Support by Command Tag
Command Tag
ddl_command_start
ddl_command_end
sql_drop
table_rewrite
Notes
ALTER AGGREGATE
X
X
-
-
ALTER COLLATION
X
X
-
-
ALTER CONVERSION
X
X
-
-
ALTER DOMAIN
X
X
-
-
ALTER DEFAULT PRIVILEGES
X
X
-
-
ALTER EXTENSION
X
X
-
-
ALTER FOREIGN DATA WRAPPER
X
X
-
-
ALTER FOREIGN TABLE
X
X
X
-
ALTER FUNCTION
X
X
-
-
ALTER LANGUAGE
X
X
-
-
ALTER LARGE OBJECT
X
X
-
-
ALTER MATERIALIZED VIEW
X
X
-
X
ALTER OPERATOR
X
X
-
-
ALTER OPERATOR CLASS
X
X
-
-
ALTER OPERATOR FAMILY
X
X
-
-
ALTER POLICY
X
X
-
-
ALTER PROCEDURE
X
X
-
-
ALTER PUBLICATION
X
X
-
-
ALTER ROUTINE
X
X
-
-
ALTER SCHEMA
X
X
-
-
ALTER SEQUENCE
X
X
-
-
ALTER SERVER
X
X
-
-
ALTER STATISTICS
X
X
-
-
ALTER SUBSCRIPTION
X
X
-
-
ALTER TABLE
X
X
X
X
ALTER TEXT SEARCH CONFIGURATION
X
X
-
-
ALTER TEXT SEARCH DICTIONARY
X
X
-
-
ALTER TEXT SEARCH PARSER
X
X
-
-
ALTER TEXT SEARCH TEMPLATE
X
X
-
-
ALTER TRIGGER
X
X
-
-
ALTER TYPE
X
X
-
X
ALTER USER MAPPING
X
X
-
-
ALTER VIEW
X
X
-
-
COMMENT
X
X
-
-
Only for local objects
CREATE ACCESS METHOD
X
X
-
-
CREATE AGGREGATE
X
X
-
-
CREATE CAST
X
X
-
-
CREATE COLLATION
X
X
-
-
CREATE CONVERSION
X
X
-
-
CREATE DOMAIN
X
X
-
-
CREATE EXTENSION
X
X
-
-
CREATE FOREIGN DATA WRAPPER
X
X
-
-
CREATE FOREIGN TABLE
X
X
-
-
CREATE FUNCTION
X
X
-
-
CREATE INDEX
X
X
-
-
CREATE LANGUAGE
X
X
-
-
CREATE MATERIALIZED VIEW
X
X
-
-
CREATE OPERATOR
X
X
-
-
CREATE OPERATOR CLASS
X
X
-
-
CREATE OPERATOR FAMILY
X
X
-
-
CREATE POLICY
X
X
-
-
CREATE PROCEDURE
X
X
-
-
CREATE PUBLICATION
X
X
-
-
CREATE RULE
X
X
-
-
CREATE SCHEMA
X
X
-
-
CREATE SEQUENCE
X
X
-
-
CREATE SERVER
X
X
-
-
CREATE STATISTICS
X
X
-
-
CREATE SUBSCRIPTION
X
X
-
-
CREATE TABLE
X
X
-
-
CREATE TABLE AS
X
X
-
-
CREATE TEXT SEARCH CONFIGURATION
X
X
-
-
CREATE TEXT SEARCH DICTIONARY
X
X
-
-
CREATE TEXT SEARCH PARSER
X
X
-
-
CREATE TEXT SEARCH TEMPLATE
X
X
-
-
CREATE TRIGGER
X
X
-
-
CREATE TYPE
X
X
-
-
CREATE USER MAPPING
X
X
-
-
CREATE VIEW
X
X
-
-
DROP ACCESS METHOD
X
X
X
-
DROP AGGREGATE
X
X
X
-
DROP CAST
X
X
X
-
DROP COLLATION
X
X
X
-
DROP CONVERSION
X
X
X
-
DROP DOMAIN
X
X
X
-
DROP EXTENSION
X
X
X
-
DROP FOREIGN DATA WRAPPER
X
X
X
-
DROP FOREIGN TABLE
X
X
X
-
DROP FUNCTION
X
X
X
-
DROP INDEX
X
X
X
-
DROP LANGUAGE
X
X
X
-
DROP MATERIALIZED VIEW
X
X
X
-
DROP OPERATOR
X
X
X
-
DROP OPERATOR CLASS
X
X
X
-
DROP OPERATOR FAMILY
X
X
X
-
DROP OWNED
X
X
X
-
DROP POLICY
X
X
X
-
DROP PROCEDURE
X
X
X
-
DROP PUBLICATION
X
X
X
-
DROP ROUTINE
X
X
X
-
DROP RULE
X
X
X
-
DROP SCHEMA
X
X
X
-
DROP SEQUENCE
X
X
X
-
DROP SERVER
X
X
X
-
DROP STATISTICS
X
X
X
-
DROP SUBSCRIPTION
X
X
X
-
DROP TABLE
X
X
X
-
DROP TEXT SEARCH CONFIGURATION
X
X
X
-
DROP TEXT SEARCH DICTIONARY
X
X
X
-
DROP TEXT SEARCH PARSER
X
X
X
-
DROP TEXT SEARCH TEMPLATE
X
X
X
-
DROP TRIGGER
X
X
X
-
DROP TYPE
X
X
X
-
DROP USER MAPPING
X
X
X
-
DROP VIEW
X
X
X
-
GRANT
X
X
-
-
Only for local objects
IMPORT FOREIGN SCHEMA
X
X
-
-
REFRESH MATERIALIZED VIEW
X
X
-
-
REVOKE
X
X
-
-
Only for local objects
SECURITY LABEL
X
X
-
-
Only for local objects
SELECT INTO
X
X
-
-
\ No newline at end of file
+
Table 40.1. Event Trigger Support by Command Tag
Command Tag
ddl_command_start
ddl_command_end
sql_drop
table_rewrite
Notes
ALTER AGGREGATE
X
X
-
-
ALTER COLLATION
X
X
-
-
ALTER CONVERSION
X
X
-
-
ALTER DOMAIN
X
X
-
-
ALTER DEFAULT PRIVILEGES
X
X
-
-
ALTER EXTENSION
X
X
-
-
ALTER FOREIGN DATA WRAPPER
X
X
-
-
ALTER FOREIGN TABLE
X
X
X
-
ALTER FUNCTION
X
X
-
-
ALTER LANGUAGE
X
X
-
-
ALTER LARGE OBJECT
X
X
-
-
ALTER MATERIALIZED VIEW
X
X
-
X
ALTER OPERATOR
X
X
-
-
ALTER OPERATOR CLASS
X
X
-
-
ALTER OPERATOR FAMILY
X
X
-
-
ALTER POLICY
X
X
-
-
ALTER PROCEDURE
X
X
-
-
ALTER PUBLICATION
X
X
-
-
ALTER ROUTINE
X
X
-
-
ALTER SCHEMA
X
X
-
-
ALTER SEQUENCE
X
X
-
-
ALTER SERVER
X
X
-
-
ALTER STATISTICS
X
X
-
-
ALTER SUBSCRIPTION
X
X
-
-
ALTER TABLE
X
X
X
X
ALTER TEXT SEARCH CONFIGURATION
X
X
-
-
ALTER TEXT SEARCH DICTIONARY
X
X
-
-
ALTER TEXT SEARCH PARSER
X
X
-
-
ALTER TEXT SEARCH TEMPLATE
X
X
-
-
ALTER TRIGGER
X
X
-
-
ALTER TYPE
X
X
-
X
ALTER USER MAPPING
X
X
-
-
ALTER VIEW
X
X
-
-
COMMENT
X
X
-
-
Only for local objects
CREATE ACCESS METHOD
X
X
-
-
CREATE AGGREGATE
X
X
-
-
CREATE CAST
X
X
-
-
CREATE COLLATION
X
X
-
-
CREATE CONVERSION
X
X
-
-
CREATE DOMAIN
X
X
-
-
CREATE EXTENSION
X
X
-
-
CREATE FOREIGN DATA WRAPPER
X
X
-
-
CREATE FOREIGN TABLE
X
X
-
-
CREATE FUNCTION
X
X
-
-
CREATE INDEX
X
X
-
-
CREATE LANGUAGE
X
X
-
-
CREATE MATERIALIZED VIEW
X
X
-
-
CREATE OPERATOR
X
X
-
-
CREATE OPERATOR CLASS
X
X
-
-
CREATE OPERATOR FAMILY
X
X
-
-
CREATE POLICY
X
X
-
-
CREATE PROCEDURE
X
X
-
-
CREATE PUBLICATION
X
X
-
-
CREATE RULE
X
X
-
-
CREATE SCHEMA
X
X
-
-
CREATE SEQUENCE
X
X
-
-
CREATE SERVER
X
X
-
-
CREATE STATISTICS
X
X
-
-
CREATE SUBSCRIPTION
X
X
-
-
CREATE TABLE
X
X
-
-
CREATE TABLE AS
X
X
-
-
CREATE TEXT SEARCH CONFIGURATION
X
X
-
-
CREATE TEXT SEARCH DICTIONARY
X
X
-
-
CREATE TEXT SEARCH PARSER
X
X
-
-
CREATE TEXT SEARCH TEMPLATE
X
X
-
-
CREATE TRIGGER
X
X
-
-
CREATE TYPE
X
X
-
-
CREATE USER MAPPING
X
X
-
-
CREATE VIEW
X
X
-
-
DROP ACCESS METHOD
X
X
X
-
DROP AGGREGATE
X
X
X
-
DROP CAST
X
X
X
-
DROP COLLATION
X
X
X
-
DROP CONVERSION
X
X
X
-
DROP DOMAIN
X
X
X
-
DROP EXTENSION
X
X
X
-
DROP FOREIGN DATA WRAPPER
X
X
X
-
DROP FOREIGN TABLE
X
X
X
-
DROP FUNCTION
X
X
X
-
DROP INDEX
X
X
X
-
DROP LANGUAGE
X
X
X
-
DROP MATERIALIZED VIEW
X
X
X
-
DROP OPERATOR
X
X
X
-
DROP OPERATOR CLASS
X
X
X
-
DROP OPERATOR FAMILY
X
X
X
-
DROP OWNED
X
X
X
-
DROP POLICY
X
X
X
-
DROP PROCEDURE
X
X
X
-
DROP PUBLICATION
X
X
X
-
DROP ROUTINE
X
X
X
-
DROP RULE
X
X
X
-
DROP SCHEMA
X
X
X
-
DROP SEQUENCE
X
X
X
-
DROP SERVER
X
X
X
-
DROP STATISTICS
X
X
X
-
DROP SUBSCRIPTION
X
X
X
-
DROP TABLE
X
X
X
-
DROP TEXT SEARCH CONFIGURATION
X
X
X
-
DROP TEXT SEARCH DICTIONARY
X
X
X
-
DROP TEXT SEARCH PARSER
X
X
X
-
DROP TEXT SEARCH TEMPLATE
X
X
X
-
DROP TRIGGER
X
X
X
-
DROP TYPE
X
X
X
-
DROP USER MAPPING
X
X
X
-
DROP VIEW
X
X
X
-
GRANT
X
X
-
-
Only for local objects
IMPORT FOREIGN SCHEMA
X
X
-
-
REFRESH MATERIALIZED VIEW
X
X
-
-
REVOKE
X
X
-
-
Only for local objects
SECURITY LABEL
X
X
-
-
Only for local objects
SELECT INTO
X
X
-
-
\ No newline at end of file
diff --git a/doc/src/sgml/html/event-trigger-table-rewrite-example.html b/doc/src/sgml/html/event-trigger-table-rewrite-example.html
index 7786a58..e25cbaa 100644
--- a/doc/src/sgml/html/event-trigger-table-rewrite-example.html
+++ b/doc/src/sgml/html/event-trigger-table-rewrite-example.html
@@ -1,5 +1,5 @@
-40.5. A Table Rewrite Event Trigger Example
To supplement the trigger mechanism discussed in Chapter 39,
PostgreSQL also provides event triggers. Unlike regular
triggers, which are attached to a single table and capture only DML events,
@@ -9,4 +9,4 @@
Like regular triggers, event triggers can be written in any procedural
language that includes event trigger support, or in C, but not in plain
SQL.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/executor.html b/doc/src/sgml/html/executor.html
index 32ec2f2..84e28b4 100644
--- a/doc/src/sgml/html/executor.html
+++ b/doc/src/sgml/html/executor.html
@@ -1,5 +1,5 @@
-52.6. Executor
The executor takes the plan created by the
planner/optimizer and recursively processes it to extract the required set
of rows. This is essentially a demand-pull pipeline mechanism.
@@ -75,4 +75,4 @@
trivial plan tree consisting of a single Result
node, which computes just one result row, feeding that up
to ModifyTable to perform the insertion.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/explicit-joins.html b/doc/src/sgml/html/explicit-joins.html
index cd98a58..6582558 100644
--- a/doc/src/sgml/html/explicit-joins.html
+++ b/doc/src/sgml/html/explicit-joins.html
@@ -1,5 +1,5 @@
-14.3. Controlling the Planner with Explicit JOIN Clauses
14.3. Controlling the Planner with Explicit JOIN Clauses
14.3. Controlling the Planner with Explicit JOIN Clauses
It is possible
to control the query planner to some extent by using the explicit JOIN
syntax. To see why this matters, we first need some background.
@@ -141,4 +141,4 @@ SELECT * FROM x, y, a, b, c WHERE something AND somethingelse;
to control join order with explicit joins). But you might set them
differently if you are trying to fine-tune the trade-off between planning
time and run time.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/explicit-locking.html b/doc/src/sgml/html/explicit-locking.html
index 728395b..4ee53e2 100644
--- a/doc/src/sgml/html/explicit-locking.html
+++ b/doc/src/sgml/html/explicit-locking.html
@@ -1,5 +1,5 @@
-13.3. Explicit Locking
PostgreSQL provides various lock modes
to control concurrent access to data in tables. These modes can
be used for application-controlled locking in situations where
@@ -393,4 +393,4 @@ SELECT pg_advisory_lock(q.id) FROM
The functions provided to manipulate advisory locks are described in
Section 9.27.10.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/extend-extensions.html b/doc/src/sgml/html/extend-extensions.html
index 6a33771..9feea38 100644
--- a/doc/src/sgml/html/extend-extensions.html
+++ b/doc/src/sgml/html/extend-extensions.html
@@ -1,5 +1,5 @@
-38.17. Packaging Related Objects into an Extension
38.17. Packaging Related Objects into an Extension
A useful extension to PostgreSQL typically includes
multiple SQL objects; for example, a new data type will require new
functions, new operators, and probably new index operator classes.
@@ -623,4 +623,4 @@ include $(PGXS)
Once the files are installed, use the
CREATE EXTENSION command to load the objects into
any particular database.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/extend-how.html b/doc/src/sgml/html/extend-how.html
index 6097327..17d97d7 100644
--- a/doc/src/sgml/html/extend-how.html
+++ b/doc/src/sgml/html/extend-how.html
@@ -1,5 +1,5 @@
-38.1. How Extensibility Works
PostgreSQL is extensible because its operation is
catalog-driven. If you are familiar with standard
relational database systems, you know that they store information
@@ -30,4 +30,4 @@
fly” makes PostgreSQL uniquely
suited for rapid prototyping of new applications and storage
structures.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/extend-pgxs.html b/doc/src/sgml/html/extend-pgxs.html
index ef591c2..2b1d44c 100644
--- a/doc/src/sgml/html/extend-pgxs.html
+++ b/doc/src/sgml/html/extend-pgxs.html
@@ -1,5 +1,5 @@
-38.18. Extension Building Infrastructure
If you are thinking about distributing your
PostgreSQL extension modules, setting up a
portable build system for them can be fairly difficult. Therefore
@@ -227,4 +227,4 @@ make VPATH=/path/to/extension/source/tree install
output_iso/results/ directory (for tests in
ISOLATION), then copy them to
expected/ if they match what you expect from the test.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/extend-type-system.html b/doc/src/sgml/html/extend-type-system.html
index ba0bac5..e5e7b9d 100644
--- a/doc/src/sgml/html/extend-type-system.html
+++ b/doc/src/sgml/html/extend-type-system.html
@@ -1,5 +1,5 @@
-38.2. The PostgreSQL Type System
PostgreSQL data types can be divided into base
types, container types, domains, and pseudo-types.
38.2.1. Base Types
@@ -219,4 +219,4 @@ RETURNS anycompatible AS ...
the same as if you had written the appropriate number of
anynonarray or anycompatiblenonarray
parameters.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/extend.html b/doc/src/sgml/html/extend.html
index 352f787..774ceaa 100644
--- a/doc/src/sgml/html/extend.html
+++ b/doc/src/sgml/html/extend.html
@@ -1,5 +1,5 @@
-Chapter 38. Extending SQL
In the sections that follow, we will discuss how you
can extend the PostgreSQL
SQL query language by adding:
@@ -17,4 +17,4 @@
packages of related objects (starting in Section 38.17)
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/external-admin-tools.html b/doc/src/sgml/html/external-admin-tools.html
index 72bfaab..974f6c4 100644
--- a/doc/src/sgml/html/external-admin-tools.html
+++ b/doc/src/sgml/html/external-admin-tools.html
@@ -1,7 +1,7 @@
-H.2. Administration Tools
There are several administration tools available for
PostgreSQL. The most popular is
pgAdmin,
and there are several commercially available ones as well.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/external-extensions.html b/doc/src/sgml/html/external-extensions.html
index ef86722..9e5b2bf 100644
--- a/doc/src/sgml/html/external-extensions.html
+++ b/doc/src/sgml/html/external-extensions.html
@@ -1,5 +1,5 @@
-H.4. Extensions
PostgreSQL is designed to be easily extensible. For
this reason, extensions loaded into the database can function
just like features that are built in. The
@@ -11,4 +11,4 @@
externally. For example, Slony-I is a popular
primary/standby replication solution that is developed independently
from the core project.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/external-interfaces.html b/doc/src/sgml/html/external-interfaces.html
index 04cf5e7..06dbf3b 100644
--- a/doc/src/sgml/html/external-interfaces.html
+++ b/doc/src/sgml/html/external-interfaces.html
@@ -1,5 +1,5 @@
-H.1. Client Interfaces
\ No newline at end of file
diff --git a/doc/src/sgml/html/external-pl.html b/doc/src/sgml/html/external-pl.html
index 3baf39a..23b5b29 100644
--- a/doc/src/sgml/html/external-pl.html
+++ b/doc/src/sgml/html/external-pl.html
@@ -1,5 +1,5 @@
-H.3. Procedural Languages
PostgreSQL includes several procedural
languages with the base distribution: PL/pgSQL, PL/Tcl,
PL/Perl, and PL/Python.
@@ -15,4 +15,4 @@
and documentation.
\ No newline at end of file
diff --git a/doc/src/sgml/html/external-projects.html b/doc/src/sgml/html/external-projects.html
index 5bd461e..e0c13f8 100644
--- a/doc/src/sgml/html/external-projects.html
+++ b/doc/src/sgml/html/external-projects.html
@@ -1,7 +1,7 @@
-Appendix H. External Projects
PostgreSQL is a complex software project,
and managing the project is difficult. We have found that many
enhancements to PostgreSQL can be more
efficiently developed separately from the core project.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/fdw-callbacks.html b/doc/src/sgml/html/fdw-callbacks.html
index 940f2f0..7687746 100644
--- a/doc/src/sgml/html/fdw-callbacks.html
+++ b/doc/src/sgml/html/fdw-callbacks.html
@@ -1,5 +1,5 @@
-59.2. Foreign Data Wrapper Callback Routines
The FDW handler function returns a palloc'd FdwRoutine
struct containing pointers to the callback functions described below.
The scan-related functions are required, the rest are optional.
@@ -1254,4 +1254,4 @@ ReparameterizeForeignPathByChild(PlannerInfo *root, List *fdw_private,
callback may use reparameterize_path_by_child,
adjust_appendrel_attrs or
adjust_appendrel_attrs_multilevel as required.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/fdw-functions.html b/doc/src/sgml/html/fdw-functions.html
index 25e6ce3..244d167 100644
--- a/doc/src/sgml/html/fdw-functions.html
+++ b/doc/src/sgml/html/fdw-functions.html
@@ -1,5 +1,5 @@
-59.1. Foreign Data Wrapper Functions
The FDW author needs to implement a handler function, and optionally
a validator function. Both functions must be written in a compiled
language such as C, using the version-1 interface.
@@ -30,4 +30,4 @@
AttributeRelationId
ForeignDataWrapperRelationId
ForeignServerRelationId
ForeignTableRelationId
UserMappingRelationId
If no validator function is supplied, options are not checked at object
creation time or object alteration time.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/fdw-helpers.html b/doc/src/sgml/html/fdw-helpers.html
index 8efa389..d9f41d8 100644
--- a/doc/src/sgml/html/fdw-helpers.html
+++ b/doc/src/sgml/html/fdw-helpers.html
@@ -1,5 +1,5 @@
-59.3. Foreign Data Wrapper Helper Functions
Several helper functions are exported from the core server so that
authors of foreign data wrappers can get easy access to attributes of
FDW-related objects, such as FDW options.
@@ -111,4 +111,4 @@ GetForeignServerByName(const char *name, bool missing_ok);
This function returns a ForeignServer object
for the foreign server with the given name. If the server is not found,
return NULL if missing_ok is true, otherwise raise an error.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/fdw-planning.html b/doc/src/sgml/html/fdw-planning.html
index 019c475..66caebe 100644
--- a/doc/src/sgml/html/fdw-planning.html
+++ b/doc/src/sgml/html/fdw-planning.html
@@ -1,5 +1,5 @@
-59.4. Foreign Data Wrapper Query Planning
The FDW callback functions GetForeignRelSize,
GetForeignPaths, GetForeignPlan,
PlanForeignModify, GetForeignJoinPaths,
@@ -188,4 +188,4 @@
exclusion constraints on remote tables are not locally known. This
in turn implies that ON CONFLICT DO UPDATE is not supported,
since the specification is mandatory there.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/fdw-row-locking.html b/doc/src/sgml/html/fdw-row-locking.html
index 9cf237f..3e05c87 100644
--- a/doc/src/sgml/html/fdw-row-locking.html
+++ b/doc/src/sgml/html/fdw-row-locking.html
@@ -1,5 +1,5 @@
-59.5. Row Locking in Foreign Data Wrappers
If an FDW's underlying storage mechanism has a concept of locking
individual rows to prevent concurrent updates of those rows, it is
usually worthwhile for the FDW to perform row-level locking with as
@@ -90,4 +90,4 @@
in src/include/nodes/plannodes.h, and the comments for
ExecRowMark in src/include/nodes/execnodes.h for
additional information.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/fdwhandler.html b/doc/src/sgml/html/fdwhandler.html
index 4a1c33b..921ea43 100644
--- a/doc/src/sgml/html/fdwhandler.html
+++ b/doc/src/sgml/html/fdwhandler.html
@@ -1,5 +1,5 @@
-Chapter 59. Writing a Foreign Data Wrapper
All operations on a foreign table are handled through its foreign data
wrapper, which consists of a set of functions that the core server
calls. The foreign data wrapper is responsible for fetching
@@ -18,4 +18,4 @@
However, PostgreSQL does not implement that API, because the effort to
accommodate it into PostgreSQL would be large, and the standard API hasn't
gained wide adoption anyway.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/features-sql-standard.html b/doc/src/sgml/html/features-sql-standard.html
index c66611a..7db204e 100644
--- a/doc/src/sgml/html/features-sql-standard.html
+++ b/doc/src/sgml/html/features-sql-standard.html
@@ -1,4 +1,4 @@
-D.1. Supported Features
trims trailing spaces from CHARACTER values before counting
E021-05
Core
OCTET_LENGTH function
E021-06
Core
SUBSTRING function
E021-07
Core
Character concatenation
E021-08
Core
UPPER and LOWER functions
E021-09
Core
TRIM function
E021-10
Core
Implicit casting among the character string types
E021-11
Core
POSITION function
E021-12
Core
Character comparison
E031
Core
Identifiers
E031-01
Core
Delimited identifiers
E031-02
Core
Lower case identifiers
E031-03
Core
Trailing underscore
E051
Core
Basic query specification
E051-01
Core
SELECT DISTINCT
E051-02
Core
GROUP BY clause
E051-04
Core
GROUP BY can contain columns not in <select list>
E051-05
Core
Select list items can be renamed
E051-06
Core
HAVING clause
E051-07
Core
Qualified * in select list
E051-08
Core
Correlation names in the FROM clause
E051-09
Core
Rename columns in the FROM clause
E061
Core
Basic predicates and search conditions
E061-01
Core
Comparison predicate
E061-02
Core
BETWEEN predicate
E061-03
Core
IN predicate with list of values
E061-04
Core
LIKE predicate
E061-05
Core
LIKE predicate ESCAPE clause
E061-06
Core
NULL predicate
E061-07
Core
Quantified comparison predicate
E061-08
Core
EXISTS predicate
E061-09
Core
Subqueries in comparison predicate
E061-11
Core
Subqueries in IN predicate
E061-12
Core
Subqueries in quantified comparison predicate
E061-13
Core
Correlated subqueries
E061-14
Core
Search condition
E071
Core
Basic query expressions
E071-01
Core
UNION DISTINCT table operator
E071-02
Core
UNION ALL table operator
E071-03
Core
EXCEPT DISTINCT table operator
E071-05
Core
Columns combined via table operators need not have exactly the same data type
E071-06
Core
Table operators in subqueries
E081
Core
Basic Privileges
E081-01
Core
SELECT privilege
E081-02
Core
DELETE privilege
E081-03
Core
INSERT privilege at the table level
E081-04
Core
UPDATE privilege at the table level
E081-05
Core
UPDATE privilege at the column level
E081-06
Core
REFERENCES privilege at the table level
E081-07
Core
REFERENCES privilege at the column level
E081-08
Core
WITH GRANT OPTION
E081-09
Core
USAGE privilege
E081-10
Core
EXECUTE privilege
E091
Core
Set functions
E091-01
Core
AVG
E091-02
Core
COUNT
E091-03
Core
MAX
E091-04
Core
MIN
E091-05
Core
SUM
E091-06
Core
ALL quantifier
E091-07
Core
DISTINCT quantifier
E101
Core
Basic data manipulation
E101-01
Core
INSERT statement
E101-03
Core
Searched UPDATE statement
E101-04
Core
Searched DELETE statement
E111
Core
Single row SELECT statement
E121
Core
Basic cursor support
E121-01
Core
DECLARE CURSOR
E121-02
Core
ORDER BY columns need not be in select list
E121-03
Core
Value expressions in ORDER BY clause
E121-04
Core
OPEN statement
E121-06
Core
Positioned UPDATE statement
E121-07
Core
Positioned DELETE statement
E121-08
Core
CLOSE statement
E121-10
Core
FETCH statement implicit NEXT
E121-17
Core
WITH HOLD cursors
E131
Core
Null value support (nulls in lieu of values)
E141
Core
Basic integrity constraints
E141-01
Core
NOT NULL constraints
E141-02
Core
UNIQUE constraints of NOT NULL columns
E141-03
Core
PRIMARY KEY constraints
E141-04
Core
Basic FOREIGN KEY constraint with the NO ACTION default for both referential delete action and referential update action
E141-06
Core
CHECK constraints
E141-07
Core
Column defaults
E141-08
Core
NOT NULL inferred on PRIMARY KEY
E141-10
Core
Names in a foreign key can be specified in any order
E151
Core
Transaction support
E151-01
Core
COMMIT statement
E151-02
Core
ROLLBACK statement
E152
Core
Basic SET TRANSACTION statement
E152-01
Core
SET TRANSACTION statement: ISOLATION LEVEL SERIALIZABLE clause
E152-02
Core
SET TRANSACTION statement: READ ONLY and READ WRITE clauses
E153
Core
Updatable queries with subqueries
E161
Core
SQL comments using leading double minus
E171
Core
SQLSTATE support
E182
Core
Host language binding
F021
Core
Basic information schema
F021-01
Core
COLUMNS view
F021-02
Core
TABLES view
F021-03
Core
VIEWS view
F021-04
Core
TABLE_CONSTRAINTS view
F021-05
Core
REFERENTIAL_CONSTRAINTS view
F021-06
Core
CHECK_CONSTRAINTS view
F031
Core
Basic schema manipulation
F031-01
Core
CREATE TABLE statement to create persistent base tables
F031-02
Core
CREATE VIEW statement
F031-03
Core
GRANT statement
F031-04
Core
ALTER TABLE statement: ADD COLUMN clause
F031-13
Core
DROP TABLE statement: RESTRICT clause
F031-16
Core
DROP VIEW statement: RESTRICT clause
F031-19
Core
REVOKE statement: RESTRICT clause
F032
CASCADE drop behavior
F033
ALTER TABLE statement: DROP COLUMN clause
F034
Extended REVOKE statement
F034-01
REVOKE statement performed by other than the owner of a schema object
F034-02
REVOKE statement: GRANT OPTION FOR clause
F034-03
REVOKE statement to revoke a privilege that the grantee has WITH GRANT OPTION
F041
Core
Basic joined table
F041-01
Core
Inner join (but not necessarily the INNER keyword)
F041-02
Core
INNER keyword
F041-03
Core
LEFT OUTER JOIN
F041-04
Core
RIGHT OUTER JOIN
F041-05
Core
Outer joins can be nested
F041-07
Core
The inner table in a left or right outer join can also be used in an inner join
F041-08
Core
All comparison operators are supported (rather than just =)
F051
Core
Basic date and time
F051-01
Core
DATE data type (including support of DATE literal)
F051-02
Core
TIME data type (including support of TIME literal) with fractional seconds precision of at least 0
F051-03
Core
TIMESTAMP data type (including support of TIMESTAMP literal) with fractional seconds precision of at least 0 and 6
F051-04
Core
Comparison predicate on DATE, TIME, and TIMESTAMP data types
F051-05
Core
Explicit CAST between datetime types and character string types
F051-06
Core
CURRENT_DATE
F051-07
Core
LOCALTIME
F051-08
Core
LOCALTIMESTAMP
F052
Intervals and datetime arithmetic
F053
OVERLAPS predicate
F081
Core
UNION and EXCEPT in views
F111
Isolation levels other than SERIALIZABLE
F111-01
READ UNCOMMITTED isolation level
F111-02
READ COMMITTED isolation level
F111-03
REPEATABLE READ isolation level
F131
Core
Grouped operations
F131-01
Core
WHERE, GROUP BY, and HAVING clauses supported in queries with grouped views
F131-02
Core
Multiple tables supported in queries with grouped views
F131-03
Core
Set functions supported in queries with grouped views
F131-04
Core
Subqueries with GROUP BY and HAVING clauses and grouped views
F131-05
Core
Single row SELECT with GROUP BY and HAVING clauses and grouped views
F171
Multiple schemas per user
F181
Core
Multiple module support
F191
Referential delete actions
F200
TRUNCATE TABLE statement
F201
Core
CAST function
F202
TRUNCATE TABLE: identity column restart option
F221
Core
Explicit defaults
F222
INSERT statement: DEFAULT VALUES clause
F231
Privilege tables
F231-01
TABLE_PRIVILEGES view
F231-02
COLUMN_PRIVILEGES view
F231-03
USAGE_PRIVILEGES view
F251
Domain support
F261
Core
CASE expression
F261-01
Core
Simple CASE
F261-02
Core
Searched CASE
F261-03
Core
NULLIF
F261-04
Core
COALESCE
F262
Extended CASE expression
F271
Compound character literals
F281
LIKE enhancements
F292
UNIQUE null treatment
SQL:202x draft
F302
INTERSECT table operator
F302-01
INTERSECT DISTINCT table operator
F302-02
INTERSECT ALL table operator
F304
EXCEPT ALL table operator
F311
Core
Schema definition statement
F311-01
Core
CREATE SCHEMA
F311-02
Core
CREATE TABLE for persistent base tables
F311-03
Core
CREATE VIEW
F311-04
Core
CREATE VIEW: WITH CHECK OPTION
F311-05
Core
GRANT statement
F312
MERGE statement
F313
Enhanced MERGE statement
F314
MERGE statement with DELETE branch
F321
User authorization
F341
Usage tables
F361
Subprogram support
F381
Extended schema manipulation
F381-01
ALTER TABLE statement: ALTER COLUMN clause
F381-02
ALTER TABLE statement: ADD CONSTRAINT clause
F381-03
ALTER TABLE statement: DROP CONSTRAINT clause
F382
Alter column data type
F383
Set column not null clause
F384
Drop identity property clause
F385
Drop column generation expression clause
F386
Set identity column generation clause
F391
Long identifiers
F392
Unicode escapes in identifiers
F393
Unicode escapes in literals
F394
Optional normal form specification
F401
Extended joined table
F401-01
NATURAL JOIN
F401-02
FULL OUTER JOIN
F401-04
CROSS JOIN
F402
Named column joins for LOBs, arrays, and multisets
F404
Range variable for common column names
F411
Time zone specification
differences regarding literal interpretation
F421
National character
F431
Read-only scrollable cursors
F431-01
FETCH with explicit NEXT
F431-02
FETCH FIRST
F431-03
FETCH LAST
F431-04
FETCH PRIOR
F431-05
FETCH ABSOLUTE
F431-06
FETCH RELATIVE
F441
Extended set function support
F442
Mixed column references in set functions
F471
Core
Scalar subquery values
F481
Core
Expanded NULL predicate
F491
Constraint management
F501
Core
Features and conformance views
F501-01
Core
SQL_FEATURES view
F501-02
Core
SQL_SIZING view
F502
Enhanced documentation tables
F531
Temporary tables
F555
Enhanced seconds precision
F561
Full value expressions
F571
Truth value tests
F591
Derived tables
F611
Indicator data types
F641
Row and table constructors
F651
Catalog name qualifiers
F661
Simple tables
F672
Retrospective check constraints
F690
Collation support
but no character set support
F692
Extended collation support
F701
Referential update actions
F711
ALTER domain
F731
INSERT column privileges
F751
View CHECK enhancements
F761
Session management
F762
CURRENT_CATALOG
F763
CURRENT_SCHEMA
F771
Connection management
F781
Self-referencing operations
F791
Insensitive cursors
F801
Full set function
F850
Top-level <order by clause> in <query expression>
F851
<order by clause> in subqueries
F852
Top-level <order by clause> in views
F855
Nested <order by clause> in <query expression>
F856
Nested <fetch first clause> in <query expression>
F857
Top-level <fetch first clause> in <query expression>
F858
<fetch first clause> in subqueries
F859
Top-level <fetch first clause> in views
F860
<fetch first row count> in <fetch first clause>
F861
Top-level <result offset clause> in <query expression>
F862
<result offset clause> in subqueries
F863
Nested <result offset clause> in <query expression>
F864
Top-level <result offset clause> in views
F865
<offset row count> in <result offset clause>
F867
FETCH FIRST clause: WITH TIES option
S071
SQL paths in function and type name resolution
S091-01
Arrays of built-in data types
S091-03
Array expressions
S092
Arrays of user-defined types
S095
Array constructors by query
S096
Optional array bounds
S098
ARRAY_AGG
S111
ONLY in query expressions
S201
SQL-invoked routines on arrays
S201-01
Array parameters
S201-02
Array as result type of functions
S211
User-defined cast functions
S301
Enhanced UNNEST
S404
TRIM_ARRAY
T031
BOOLEAN data type
T071
BIGINT data type
T121
WITH (excluding RECURSIVE) in query expression
T122
WITH (excluding RECURSIVE) in subquery
T131
Recursive query
T132
Recursive query in subquery
T133
Enhanced cycle mark values
SQL:202x draft
T141
SIMILAR predicate
T151
DISTINCT predicate
T152
DISTINCT predicate with negation
T171
LIKE clause in table definition
T172
AS subquery clause in table definition
T173
Extended LIKE clause in table definition
T174
Identity columns
T177
Sequence generator support: simple restart option
T178
Identity columns: simple restart option
T191
Referential action RESTRICT
T201
Comparable data types for referential constraints
T211-01
Triggers activated on UPDATE, INSERT, or DELETE of one base table
T211-02
BEFORE triggers
T211-03
AFTER triggers
T211-04
FOR EACH ROW triggers
T211-05
Ability to specify a search condition that must be true before the trigger is invoked
T211-07
TRIGGER privilege
T212
Enhanced trigger capability
T213
INSTEAD OF triggers
T241
START TRANSACTION statement
T261
Chained transactions
T271
Savepoints
T281
SELECT privilege with column granularity
T285
Enhanced derived column names
T312
OVERLAY function
T321-01
Core
User-defined functions with no overloading
T321-02
Core
User-defined stored procedures with no overloading
T321-03
Core
Function invocation
T321-04
Core
CALL statement
T321-05
Core
RETURN statement
T321-06
Core
ROUTINES view
T321-07
Core
PARAMETERS view
T323
Explicit security for external routines
T325
Qualified SQL parameter references
T331
Basic roles
T332
Extended roles
T341
Overloading of SQL-invoked functions and procedures
T351
Bracketed SQL comments (/*...*/ comments)
T431
Extended grouping capabilities
T432
Nested and concatenated GROUPING SETS
T433
Multiargument GROUPING function
T434
GROUP BY DISTINCT
T441
ABS and MOD functions
T461
Symmetric BETWEEN predicate
T491
LATERAL derived table
T501
Enhanced EXISTS predicate
T521
Named arguments in CALL statement
T523
Default values for INOUT parameters of SQL-invoked procedures
T524
Named arguments in routine invocations other than a CALL statement
T525
Default values for parameters of SQL-invoked functions
T551
Optional key words for default syntax
T581
Regular expression substring function
T591
UNIQUE constraints of possibly null columns
T611
Elementary OLAP operations
T612
Advanced OLAP operations
T613
Sampling
T614
NTILE function
T615
LEAD and LAG functions
T617
FIRST_VALUE and LAST_VALUE function
T620
WINDOW clause: GROUPS option
T621
Enhanced numeric functions
T622
Trigonometric functions
T623
General logarithm functions
T624
Common logarithm functions
T631
Core
IN predicate with one list element
T651
SQL-schema statements in SQL routines
T653
SQL-schema statements in external routines
T655
Cyclically dependent routines
T831
SQL/JSON path language: strict mode
T832
SQL/JSON path language: item method
T833
SQL/JSON path language: multiple subscripts
T834
SQL/JSON path language: wildcard member accessor
T835
SQL/JSON path language: filter expressions
T836
SQL/JSON path language: starts with predicate
T837
SQL/JSON path language: regex_like predicate
X010
XML type
X011
Arrays of XML type
X014
Attributes of XML type
X016
Persistent XML values
X020
XMLConcat
X031
XMLElement
X032
XMLForest
X034
XMLAgg
X035
XMLAgg: ORDER BY option
X036
XMLComment
X037
XMLPI
X040
Basic table mapping
X041
Basic table mapping: nulls absent
X042
Basic table mapping: null as nil
X043
Basic table mapping: table as forest
X044
Basic table mapping: table as element
X045
Basic table mapping: with target namespace
X046
Basic table mapping: data mapping
X047
Basic table mapping: metadata mapping
X048
Basic table mapping: base64 encoding of binary strings
X049
Basic table mapping: hex encoding of binary strings
X050
Advanced table mapping
X051
Advanced table mapping: nulls absent
X052
Advanced table mapping: null as nil
X053
Advanced table mapping: table as forest
X054
Advanced table mapping: table as element
X055
Advanced table mapping: with target namespace
X056
Advanced table mapping: data mapping
X057
Advanced table mapping: metadata mapping
X058
Advanced table mapping: base64 encoding of binary strings
X059
Advanced table mapping: hex encoding of binary strings
X060
XMLParse: character string input and CONTENT option
X061
XMLParse: character string input and DOCUMENT option
X070
XMLSerialize: character string serialization and CONTENT option
X071
XMLSerialize: character string serialization and DOCUMENT option
X072
XMLSerialize: character string serialization
X090
XML document predicate
X120
XML parameters in SQL routines
X121
XML parameters in external routines
X221
XML passing mechanism BY VALUE
X301
XMLTable: derived column list option
X302
XMLTable: ordinality column option
X303
XMLTable: column default option
X304
XMLTable: passing a context item
must be XML DOCUMENT
X400
Name and identifier mapping
X410
Alter column data type: XML type
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/features.html b/doc/src/sgml/html/features.html
index fa08f62..9500638 100644
--- a/doc/src/sgml/html/features.html
+++ b/doc/src/sgml/html/features.html
@@ -1,5 +1,5 @@
-Appendix D. SQL Conformance
This section attempts to outline to what extent
PostgreSQL conforms to the current SQL
standard. The following information is not a full statement of
@@ -70,4 +70,4 @@
Feature codes containing a hyphen are subfeatures. Therefore, if a
particular subfeature is not supported, the main feature is listed
as unsupported even if some other subfeatures are supported.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/file-fdw.html b/doc/src/sgml/html/file-fdw.html
index 61fdd76..72a023c 100644
--- a/doc/src/sgml/html/file-fdw.html
+++ b/doc/src/sgml/html/file-fdw.html
@@ -1,5 +1,5 @@
-F.16. file_fdw
The file_fdw module provides the foreign-data wrapper
file_fdw, which can be used to access data
files in the server's file system, or to execute programs on the server
@@ -142,4 +142,4 @@ OPTIONS ( filename 'log/pglog.csv', format 'csv' );
That's it — now you can query your log directly. In production, of
course, you would need to define some way to deal with log rotation.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-admin.html b/doc/src/sgml/html/functions-admin.html
index c1e0715..5169eb1 100644
--- a/doc/src/sgml/html/functions-admin.html
+++ b/doc/src/sgml/html/functions-admin.html
@@ -1,5 +1,5 @@
-9.27. System Administration Functions
@@ -1645,4 +1645,4 @@ SELECT convert_from(pg_read_binary_file('file_in_utf8.txt'), 'UTF8');
This will either obtain the lock immediately and
return true, or return false
without waiting if the lock cannot be acquired immediately.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-aggregate.html b/doc/src/sgml/html/functions-aggregate.html
index 1723136..93637d9 100644
--- a/doc/src/sgml/html/functions-aggregate.html
+++ b/doc/src/sgml/html/functions-aggregate.html
@@ -1,5 +1,5 @@
-9.21. Aggregate Functions
Aggregate functions compute a single result
from a set of input values. The built-in general-purpose aggregate
functions are listed in Table 9.58
@@ -726,4 +726,4 @@ SELECT count(*) FROM sometable;
neither make nor model was grouped
by in the last row (which therefore is an aggregate over all the input
rows).
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-array.html b/doc/src/sgml/html/functions-array.html
index ec1cc4f..a5c50cb 100644
--- a/doc/src/sgml/html/functions-array.html
+++ b/doc/src/sgml/html/functions-array.html
@@ -1,5 +1,5 @@
-9.19. Array Functions and Operators
Table 9.52 shows the specialized operators
available for array types.
In addition to those, the usual comparison operators shown in Table 9.1 are available for
@@ -382,4 +382,4 @@
See also Section 9.21 about the aggregate
function array_agg for use with arrays.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-binarystring.html b/doc/src/sgml/html/functions-binarystring.html
index ba0b67f..f4e997a 100644
--- a/doc/src/sgml/html/functions-binarystring.html
+++ b/doc/src/sgml/html/functions-binarystring.html
@@ -1,5 +1,5 @@
-9.5. Binary String Functions and Operators
This section describes functions and operators for examining and
manipulating binary strings, that is values of type bytea.
Many of these are equivalent, in purpose and syntax, to the
@@ -470,7 +470,7 @@
base64
The base64 format is that
- of RFC
+ of RFC
2045 Section 6.8. As per the RFC, encoded lines are
broken at 76 characters. However instead of the MIME CRLF
end-of-line marker, only a newline is used for end-of-line.
@@ -507,4 +507,4 @@
See also the aggregate function string_agg in
Section 9.21 and the large object functions
in Section 35.4.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-bitstring.html b/doc/src/sgml/html/functions-bitstring.html
index 265b296..8a32325 100644
--- a/doc/src/sgml/html/functions-bitstring.html
+++ b/doc/src/sgml/html/functions-bitstring.html
@@ -1,5 +1,5 @@
-9.6. Bit String Functions and Operators
This section describes functions and operators for examining and
manipulating bit strings, that is values of the types
bit and bit varying. (While only
@@ -232,4 +232,4 @@ cast(-44 as bit(12)) “bit” means casting to
bit(1), and so will deliver only the least significant
bit of the integer.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-comparison.html b/doc/src/sgml/html/functions-comparison.html
index 6c9e82b..34beddd 100644
--- a/doc/src/sgml/html/functions-comparison.html
+++ b/doc/src/sgml/html/functions-comparison.html
@@ -1,5 +1,5 @@
-9.2. Comparison Functions and Operators
The usual comparison operators are available, as shown in Table 9.1.
Table 9.1. Comparison Operators
Operator
Description
datatype<datatype
@@ -397,4 +397,4 @@
num_nulls(1, NULL, 2)
→ 1
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-comparisons.html b/doc/src/sgml/html/functions-comparisons.html
index 1e08113..0655af1 100644
--- a/doc/src/sgml/html/functions-comparisons.html
+++ b/doc/src/sgml/html/functions-comparisons.html
@@ -1,5 +1,5 @@
-9.24. Row and Array Comparisons
This section describes several specialized constructs for making
multiple comparisons between groups of values. These forms are
syntactically related to the subquery forms of the previous section,
@@ -212,4 +212,4 @@ AND
for materialized views and might be useful for other specialized
purposes such as replication and B-Tree deduplication (see Section 67.4.3). They are not intended to be
generally useful for writing queries, though.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-conditional.html b/doc/src/sgml/html/functions-conditional.html
index 8db014d..1737259 100644
--- a/doc/src/sgml/html/functions-conditional.html
+++ b/doc/src/sgml/html/functions-conditional.html
@@ -1,5 +1,5 @@
-9.18. Conditional Expressions
This section describes the SQL-compliant conditional expressions
available in PostgreSQL.
Tip
@@ -184,4 +184,4 @@ SELECT NULLIF(value, '(none)') ...
the SQL standard, but are a common extension. Some other databases
make them return NULL if any argument is NULL, rather than only when
all are NULL.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-datetime.html b/doc/src/sgml/html/functions-datetime.html
index 9523015..aaa1c4e 100644
--- a/doc/src/sgml/html/functions-datetime.html
+++ b/doc/src/sgml/html/functions-datetime.html
@@ -1,5 +1,5 @@
-9.9. Date/Time Functions and Operators
Table 9.33 shows the available
functions for date/time value processing, with details appearing in
the following subsections. Table 9.32 illustrates the behaviors of
@@ -183,7 +183,7 @@
Subtract timestamps (converting 24-hour intervals into days,
- similarly to justify_hours())
+ similarly to justify_hours())
- Adjust interval so 30-day time periods are represented as months
+ Adjust interval, converting 30-day time periods to months
- justify_days(interval '35 days')
- → 1 mon 5 days
+ justify_days(interval '1 year 65 days')
+ → 1 year 2 mons 5 days
-
+ justify_hours ( interval )
→ interval
- Adjust interval so 24-hour time periods are represented as days
+ Adjust interval, converting 24-hour time periods to days
- justify_hours(interval '27 hours')
- → 1 day 03:00:00
+ justify_hours(interval '50 hours 10 minutes')
+ → 2 days 02:10:00
justify_interval ( interval )
@@ -758,38 +758,40 @@ EXTRACT(field FROM extract function retrieves subfields
such as year or hour from date/time values.
source must be a value expression of
- type timestamp, time, or interval.
- (Expressions of type date are
- cast to timestamp and can therefore be used as
- well.) field is an identifier or
+ type timestamp, date, time,
+ or interval. (Timestamps and times can be with or
+ without time zone.)
+ field is an identifier or
string that selects what field to extract from the source value.
+ Not all fields are valid for every input data type; for example, fields
+ smaller than a day cannot be extracted from a date, while
+ fields of a day or more cannot be extracted from a time.
The extract function returns values of type
numeric.
+
The following are valid field names:
century
- The century
+ The century; for interval values, the year field
+ divided by 100
SELECT EXTRACT(CENTURY FROM TIMESTAMP '2000-12-16 12:21:13');
Result: 20
SELECT EXTRACT(CENTURY FROM TIMESTAMP '2001-02-16 20:38:40');
Result: 21
-
- The first century starts at 0001-01-01 00:00:00 AD, although
- they did not know it at the time. This definition applies to all
- Gregorian calendar countries. There is no century number 0,
- you go from -1 century to 1 century.
-
- If you disagree with this, please write your complaint to:
- Pope, Cathedral Saint-Peter of Roma, Vatican.
-
day
- For timestamp values, the day (of the month) field
- (1–31) ; for interval values, the number of days
+SELECT EXTRACT(CENTURY FROM DATE '0001-01-01 AD');
+Result: 1
+SELECT EXTRACT(CENTURY FROM DATE '0001-12-31 BC');
+Result: -1
+SELECT EXTRACT(CENTURY FROM INTERVAL '2001 years');
+Result: 20
+
day
+ The day of the month (1–31); for interval
+ values, the number of days
SELECT EXTRACT(DAY FROM TIMESTAMP '2001-02-16 20:38:40');
Result: 16
-
SELECT EXTRACT(DAY FROM INTERVAL '40 days 1 minute');
Result: 40
decade
@@ -824,10 +826,8 @@ SELECT EXTRACT(DOY FROM TIMESTAMP '2001-02-16 20:38:40');
SELECT EXTRACT(EPOCH FROM TIMESTAMP WITH TIME ZONE '2001-02-16 20:38:40.12-08');
Result: 982384720.120000
-
SELECT EXTRACT(EPOCH FROM TIMESTAMP '2001-02-16 20:38:40.12');
Result: 982355920.120000
-
SELECT EXTRACT(EPOCH FROM INTERVAL '5 days 3 hours');
Result: 442800.000000
@@ -843,7 +843,8 @@ SELECT to_timestamp(982384720.12);
assume that the original value had been given in UTC, which might
not be the case.
hour
- The hour field (0–23)
+ The hour field (0–23 in timestamps, unrestricted in
+ intervals)
SELECT EXTRACT(HOUR FROM TIMESTAMP '2001-02-16 20:38:40');
Result: 20
@@ -858,7 +859,7 @@ SELECT EXTRACT(ISODOW FROM TIMESTAMP '2001-02-18 20:38:40');
matches the ISO 8601 day of the week numbering.
isoyear
The ISO 8601 week-numbering year that the date
- falls in (not applicable to intervals)
+ falls in
SELECT EXTRACT(ISOYEAR FROM DATE '2006-01-01');
Result: 2005
@@ -870,11 +871,9 @@ SELECT EXTRACT(ISOYEAR FROM DATE '2006-01-02');
January or late December the ISO year may be
different from the Gregorian year. See the week
field for more information.
-
- This field is not available in PostgreSQL releases prior to 8.3.
julian
The Julian Date corresponding to the
- date or timestamp (not applicable to intervals). Timestamps
+ date or timestamp. Timestamps
that are not local midnight result in a fractional value. See
Section B.7 for more information.
@@ -889,10 +888,13 @@ SELECT EXTRACT(JULIAN FROM TIMESTAMP '2006-01-01 12:00');
SELECT EXTRACT(MICROSECONDS FROM TIME '17:12:28.5');
Result: 28500000
millennium
- The millennium
+ The millennium; for interval values, the year field
+ divided by 1000
SELECT EXTRACT(MILLENNIUM FROM TIMESTAMP '2001-02-16 20:38:40');
Result: 3
+SELECT EXTRACT(MILLENNIUM FROM INTERVAL '2001 years');
+Result: 2
Years in the 1900s are in the second millennium.
The third millennium started January 1, 2001.
@@ -908,16 +910,14 @@ SELECT EXTRACT(MILLISECONDS FROM TIME '17:12:28.5');
SELECT EXTRACT(MINUTE FROM TIMESTAMP '2001-02-16 20:38:40');
Result: 38
month
- For timestamp values, the number of the month
- within the year (1–12) ; for interval values,
- the number of months, modulo 12 (0–11)
+ The number of the month within the year (1–12);
+ for interval values, the number of months modulo 12
+ (0–11)
SELECT EXTRACT(MONTH FROM TIMESTAMP '2001-02-16 20:38:40');
Result: 2
-
SELECT EXTRACT(MONTH FROM INTERVAL '2 years 3 months');
Result: 3
-
SELECT EXTRACT(MONTH FROM INTERVAL '2 years 13 months');
Result: 1
quarter
@@ -930,7 +930,6 @@ SELECT EXTRACT(QUARTER FROM TIMESTAMP '2001-02-16 20:38:40');
SELECT EXTRACT(SECOND FROM TIMESTAMP '2001-02-16 20:38:40');
Result: 40.000000
-
SELECT EXTRACT(SECOND FROM TIME '17:12:28.5');
Result: 28.500000
timezone
@@ -967,6 +966,18 @@ SELECT EXTRACT(WEEK FROM TIMESTAMP '2001-02-16 20:38:40');
SELECT EXTRACT(YEAR FROM TIMESTAMP '2001-02-16 20:38:40');
Result: 2001
+
+ When processing an interval value,
+ the extract function produces field values that
+ match the interpretation used by the interval output function. This
+ can produce surprising results if one starts with a non-normalized
+ interval representation, for example:
+
SELECT TIMESTAMP '2001-02-16 20:38:40' AT TIME ZONE 'America/Denver';
Result: 2001-02-16 19:38:40-08
-
SELECT TIMESTAMP WITH TIME ZONE '2001-02-16 20:38:40-05' AT TIME ZONE 'America/Denver';
Result: 2001-02-16 18:38:40
-
SELECT TIMESTAMP '2001-02-16 20:38:40' AT TIME ZONE 'Asia/Tokyo' AT TIME ZONE 'America/Chicago';
Result: 2001-02-16 05:38:40
@@ -1313,4 +1312,4 @@ SELECT pg_sleep_until('tomorrow 03:00');
when calling pg_sleep or its variants. Otherwise
other sessions might have to wait for your sleeping process, slowing down
the entire system.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-enum.html b/doc/src/sgml/html/functions-enum.html
index 7f4e134..cb930fe 100644
--- a/doc/src/sgml/html/functions-enum.html
+++ b/doc/src/sgml/html/functions-enum.html
@@ -1,5 +1,5 @@
-9.10. Enum Support Functions
For enum types (described in Section 8.7),
there are several functions that allow cleaner programming without
hard-coding particular values of an enum type.
@@ -81,4 +81,4 @@ CREATE TYPE rainbow AS ENUM ('red', 'orange', 'yellow', 'green', 'blue', 'purple
the type can be passed, with the same result. It is more common to
apply these functions to a table column or function argument than to
a hardwired type name as used in the examples.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-event-triggers.html b/doc/src/sgml/html/functions-event-triggers.html
index d5e41a6..5719030 100644
--- a/doc/src/sgml/html/functions-event-triggers.html
+++ b/doc/src/sgml/html/functions-event-triggers.html
@@ -1,5 +1,5 @@
-9.29. Event Trigger Functions
PostgreSQL provides these helper functions
to retrieve information from event triggers.
@@ -130,4 +130,4 @@ CREATE EVENT TRIGGER test_table_rewrite_oid
ON table_rewrite
EXECUTE FUNCTION test_event_trigger_table_rewrite_oid();
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-formatting.html b/doc/src/sgml/html/functions-formatting.html
index a509eee..37c2442 100644
--- a/doc/src/sgml/html/functions-formatting.html
+++ b/doc/src/sgml/html/functions-formatting.html
@@ -1,5 +1,5 @@
-9.8. Data Type Formatting Functions
The PostgreSQL formatting functions
provide a powerful set of tools for converting various data types
(date/time, integer, floating point, numeric) to formatted strings
@@ -245,11 +245,11 @@
use some non-digit character or template after YYYY,
otherwise the year is always interpreted as 4 digits. For example
(with the year 20000):
- to_date('200001131', 'YYYYMMDD') will be
+ to_date('200001130', 'YYYYMMDD') will be
interpreted as a 4-digit year; instead use a non-digit
separator after the year, like
- to_date('20000-1131', 'YYYY-MMDD') or
- to_date('20000Nov31', 'YYYYMonDD').
+ to_date('20000-1130', 'YYYY-MMDD') or
+ to_date('20000Nov30', 'YYYYMonDD').
In to_timestamp and to_date,
the CC (century) field is accepted but ignored
@@ -407,4 +407,4 @@
Table 9.30. Template Pattern Modifiers for Numeric Formatting
Modifier
Description
Example
FM prefix
fill mode (suppress trailing zeroes and padding blanks)
FM99.99
TH suffix
upper case ordinal number suffix
999TH
th suffix
lower case ordinal number suffix
999th
Table 9.31 shows some
examples of the use of the to_char function.
-
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-geometry.html b/doc/src/sgml/html/functions-geometry.html
index 756d40b..66e4b35 100644
--- a/doc/src/sgml/html/functions-geometry.html
+++ b/doc/src/sgml/html/functions-geometry.html
@@ -1,5 +1,5 @@
-9.11. Geometric Functions and Operators
The geometric types point, box,
lseg, line, path,
polygon, and circle have a large set of
@@ -883,4 +883,4 @@
UPDATE t SET p[1] = ... changes the Y coordinate.
In the same way, a value of type box or lseg can be treated
as an array of two point values.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-info.html b/doc/src/sgml/html/functions-info.html
index 6f16acd..5a2052c 100644
--- a/doc/src/sgml/html/functions-info.html
+++ b/doc/src/sgml/html/functions-info.html
@@ -1,5 +1,5 @@
-9.26. System Information Functions and Operators
Table 9.66 shows several
functions that extract session and system information.
@@ -1771,4 +1771,4 @@ SELECT collation for ('foo' COLLATE "de_DE");
Returns information about recovery state, as shown in
Table 9.86.
-
Table 9.83. pg_control_checkpoint Output Columns
Column Name
Data Type
checkpoint_lsn
pg_lsn
redo_lsn
pg_lsn
redo_wal_file
text
timeline_id
integer
prev_timeline_id
integer
full_page_writes
boolean
next_xid
text
next_oid
oid
next_multixact_id
xid
next_multi_offset
xid
oldest_xid
xid
oldest_xid_dbid
oid
oldest_active_xid
xid
oldest_multi_xid
xid
oldest_multi_dbid
oid
oldest_commit_ts_xid
xid
newest_commit_ts_xid
xid
checkpoint_time
timestamp with time zone
Table 9.84. pg_control_system Output Columns
Column Name
Data Type
pg_control_version
integer
catalog_version_no
integer
system_identifier
bigint
pg_control_last_modified
timestamp with time zone
Table 9.85. pg_control_init Output Columns
Column Name
Data Type
max_data_alignment
integer
database_block_size
integer
blocks_per_segment
integer
wal_block_size
integer
bytes_per_wal_segment
integer
max_identifier_length
integer
max_index_columns
integer
max_toast_chunk_size
integer
large_object_chunk_size
integer
float8_pass_by_value
boolean
data_page_checksum_version
integer
Table 9.86. pg_control_recovery Output Columns
Column Name
Data Type
min_recovery_end_lsn
pg_lsn
min_recovery_end_timeline
integer
backup_start_lsn
pg_lsn
backup_end_lsn
pg_lsn
end_of_backup_record_required
boolean
\ No newline at end of file
+
Table 9.83. pg_control_checkpoint Output Columns
Column Name
Data Type
checkpoint_lsn
pg_lsn
redo_lsn
pg_lsn
redo_wal_file
text
timeline_id
integer
prev_timeline_id
integer
full_page_writes
boolean
next_xid
text
next_oid
oid
next_multixact_id
xid
next_multi_offset
xid
oldest_xid
xid
oldest_xid_dbid
oid
oldest_active_xid
xid
oldest_multi_xid
xid
oldest_multi_dbid
oid
oldest_commit_ts_xid
xid
newest_commit_ts_xid
xid
checkpoint_time
timestamp with time zone
Table 9.84. pg_control_system Output Columns
Column Name
Data Type
pg_control_version
integer
catalog_version_no
integer
system_identifier
bigint
pg_control_last_modified
timestamp with time zone
Table 9.85. pg_control_init Output Columns
Column Name
Data Type
max_data_alignment
integer
database_block_size
integer
blocks_per_segment
integer
wal_block_size
integer
bytes_per_wal_segment
integer
max_identifier_length
integer
max_index_columns
integer
max_toast_chunk_size
integer
large_object_chunk_size
integer
float8_pass_by_value
boolean
data_page_checksum_version
integer
Table 9.86. pg_control_recovery Output Columns
Column Name
Data Type
min_recovery_end_lsn
pg_lsn
min_recovery_end_timeline
integer
backup_start_lsn
pg_lsn
backup_end_lsn
pg_lsn
end_of_backup_record_required
boolean
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-json.html b/doc/src/sgml/html/functions-json.html
index fc43dd4..45104e5 100644
--- a/doc/src/sgml/html/functions-json.html
+++ b/doc/src/sgml/html/functions-json.html
@@ -1,5 +1,5 @@
-9.16. JSON Functions and Operators
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-logical.html b/doc/src/sgml/html/functions-logical.html
index a835ec8..d304355 100644
--- a/doc/src/sgml/html/functions-logical.html
+++ b/doc/src/sgml/html/functions-logical.html
@@ -1,5 +1,5 @@
-9.1. Logical Operators
The usual logical operators are available:
@@ -33,4 +33,4 @@
without affecting the result. (However, it is not guaranteed that
the left operand is evaluated before the right operand. See Section 4.2.14 for more information about the
order of evaluation of subexpressions.)
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-matching.html b/doc/src/sgml/html/functions-matching.html
index 47d57e3..565e92c 100644
--- a/doc/src/sgml/html/functions-matching.html
+++ b/doc/src/sgml/html/functions-matching.html
@@ -1,5 +1,5 @@
-9.7. Pattern Matching
There are three separate approaches to pattern matching provided
by PostgreSQL: the traditional
SQL LIKE operator, the
@@ -1412,4 +1412,4 @@ SELECT regexp_match('abc01234xyz', '(?:(.*?)(\d+)(.*)){1,1}');
backslash.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-math.html b/doc/src/sgml/html/functions-math.html
index 6fb0086..5a4c475 100644
--- a/doc/src/sgml/html/functions-math.html
+++ b/doc/src/sgml/html/functions-math.html
@@ -1,5 +1,5 @@
-9.3. Mathematical Functions and Operators
Mathematical operators are provided for many
PostgreSQL types. For types without
standard mathematical conventions
@@ -998,4 +998,4 @@
atanh(0.5)
→ 0.5493061443340548
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-net.html b/doc/src/sgml/html/functions-net.html
index 3f466ee..4cd7cd5 100644
--- a/doc/src/sgml/html/functions-net.html
+++ b/doc/src/sgml/html/functions-net.html
@@ -1,5 +1,5 @@
-9.12. Network Address Functions and Operators
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-range.html b/doc/src/sgml/html/functions-range.html
index c931d3c..c203e5d 100644
--- a/doc/src/sgml/html/functions-range.html
+++ b/doc/src/sgml/html/functions-range.html
@@ -1,5 +1,5 @@
-9.20. Range/Multirange Functions and Operators
Table 9.54 shows the specialized operators
@@ -704,4 +704,4 @@
The lower_inc, upper_inc,
lower_inf, and upper_inf
functions all return false for an empty range or multirange.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-sequence.html b/doc/src/sgml/html/functions-sequence.html
index a641ed1..2e2f8b8 100644
--- a/doc/src/sgml/html/functions-sequence.html
+++ b/doc/src/sgml/html/functions-sequence.html
@@ -1,5 +1,5 @@
-9.17. Sequence Manipulation Functions
This section describes functions for operating on sequence
objects, also called sequence generators or just sequences.
Sequence objects are special single-row tables created with CREATE SEQUENCE.
@@ -136,4 +136,4 @@ SELECT setval('myseq', 42, false); regclass data type's input
converter will do the work for you. See Section 8.19
for details.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-srf.html b/doc/src/sgml/html/functions-srf.html
index e9994fd..446416c 100644
--- a/doc/src/sgml/html/functions-srf.html
+++ b/doc/src/sgml/html/functions-srf.html
@@ -1,5 +1,5 @@
-9.25. Set Returning Functions
This section describes functions that possibly return more than one row.
The most widely used functions in this class are series generating
functions, as detailed in Table 9.64 and
@@ -215,4 +215,4 @@ SELECT * FROM pg_ls_dir('.') WITH ORDINALITY AS t(ls,n);
pg_subtrans | 19
(19 rows)
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-statistics.html b/doc/src/sgml/html/functions-statistics.html
index 8ca7a84..26629a3 100644
--- a/doc/src/sgml/html/functions-statistics.html
+++ b/doc/src/sgml/html/functions-statistics.html
@@ -1,5 +1,5 @@
-9.30. Statistics Information Functions
PostgreSQL provides a function to inspect complex
statistics defined using the CREATE STATISTICS command.
9.30.1. Inspecting MCV Lists
@@ -21,4 +21,4 @@ SELECT m.* FROM pg_statistic_ext join pg_statistic_ext_data on (oid = stxoid),
Values of the pg_mcv_list type can be obtained only from the
pg_statistic_ext_data.stxdmcv
column.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-string.html b/doc/src/sgml/html/functions-string.html
index 07f40c9..c45ceca 100644
--- a/doc/src/sgml/html/functions-string.html
+++ b/doc/src/sgml/html/functions-string.html
@@ -1,5 +1,5 @@
-9.4. String Functions and Operators
This section describes functions and operators for examining and
manipulating string values. Strings in this context include values
of the types character, character varying,
@@ -1205,4 +1205,4 @@ SELECT format('Testing %3$s, %2$s, %s', 'one', 'two', 'three');
The %I and %L format specifiers are particularly
useful for safely constructing dynamic SQL statements. See
Example 43.1.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-subquery.html b/doc/src/sgml/html/functions-subquery.html
index 25373c3..fc96226 100644
--- a/doc/src/sgml/html/functions-subquery.html
+++ b/doc/src/sgml/html/functions-subquery.html
@@ -1,5 +1,5 @@
-9.23. Subquery Expressions
This section describes the SQL-compliant subquery
expressions available in PostgreSQL.
All of the expression forms documented in this section return
@@ -210,4 +210,4 @@ WHERE EXISTS (SELECT 1 FROM tab2 WHERE col2 = tab1.col2);
See Section 9.24.5 for details about the meaning
of a row constructor comparison.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-textsearch.html b/doc/src/sgml/html/functions-textsearch.html
index b40b9a8..7c27d25 100644
--- a/doc/src/sgml/html/functions-textsearch.html
+++ b/doc/src/sgml/html/functions-textsearch.html
@@ -1,5 +1,5 @@
-9.13. Text Search Functions and Operators
ts_stat('SELECT vector FROM apod')
→ (foo,10,15) ...
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-trigger.html b/doc/src/sgml/html/functions-trigger.html
index 82f9950..77abbf5 100644
--- a/doc/src/sgml/html/functions-trigger.html
+++ b/doc/src/sgml/html/functions-trigger.html
@@ -1,5 +1,5 @@
-9.28. Trigger Functions
While many uses of triggers involve user-written trigger functions,
PostgreSQL provides a few built-in trigger
functions that can be used directly in user-defined triggers. These
@@ -90,4 +90,4 @@ FOR EACH ROW EXECUTE FUNCTION suppress_redundant_updates_trigger();
choose a trigger name that comes after the name of any other trigger
you might have on the table. (Hence the “z” prefix in the
example.)
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-uuid.html b/doc/src/sgml/html/functions-uuid.html
index c6dc609..d5fb9e4 100644
--- a/doc/src/sgml/html/functions-uuid.html
+++ b/doc/src/sgml/html/functions-uuid.html
@@ -1,5 +1,5 @@
-9.14. UUID Functions
PostgreSQL includes one function to generate a UUID:
gen_random_uuid () → uuid
@@ -13,4 +13,4 @@
PostgreSQL also provides the usual comparison
operators shown in Table 9.1 for
UUIDs.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-window.html b/doc/src/sgml/html/functions-window.html
index 74ac321..3a46b8c 100644
--- a/doc/src/sgml/html/functions-window.html
+++ b/doc/src/sgml/html/functions-window.html
@@ -1,5 +1,5 @@
-9.22. Window Functions
Window functions provide the ability to perform
calculations across sets of rows that are related to the current query
row. See Section 3.5 for an introduction to this
@@ -179,4 +179,4 @@
default FROM FIRST behavior is supported. (You can achieve
the result of FROM LAST by reversing the ORDER BY
ordering.)
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions-xml.html b/doc/src/sgml/html/functions-xml.html
index 6780308..aa2d1b4 100644
--- a/doc/src/sgml/html/functions-xml.html
+++ b/doc/src/sgml/html/functions-xml.html
@@ -1,5 +1,5 @@
-9.15. XML Functions
The functions and function-like expressions described in this
section operate on values of type xml. See Section 8.13 for information about the xml
type. The function-like expressions xmlparse
@@ -909,4 +909,4 @@ table2-mapping
will be put into content form with each such disallowed node replaced by
its string value, as defined for the XPath 1.0
string function.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/functions.html b/doc/src/sgml/html/functions.html
index 1f13502..8be5ec2 100644
--- a/doc/src/sgml/html/functions.html
+++ b/doc/src/sgml/html/functions.html
@@ -1,5 +1,5 @@
-Chapter 9. Functions and Operators
PostgreSQL provides a large number of
functions and operators for the built-in data types. This chapter
describes most of them, although additional special-purpose functions
@@ -30,4 +30,4 @@ repeat('Pg', 4) → PgPgPgPg
is present in other SQL database management
systems, and in many cases this functionality is compatible and
consistent between the various implementations.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/fuzzystrmatch.html b/doc/src/sgml/html/fuzzystrmatch.html
index 18e23de..f7418d3 100644
--- a/doc/src/sgml/html/fuzzystrmatch.html
+++ b/doc/src/sgml/html/fuzzystrmatch.html
@@ -1,5 +1,5 @@
-F.17. fuzzystrmatch
\ No newline at end of file
diff --git a/doc/src/sgml/html/generic-wal.html b/doc/src/sgml/html/generic-wal.html
index dbc702e..e0408e8 100644
--- a/doc/src/sgml/html/generic-wal.html
+++ b/doc/src/sgml/html/generic-wal.html
@@ -1,5 +1,5 @@
-Chapter 65. Generic WAL Records
Although all built-in WAL-logged modules have their own types of WAL
records, there is also a generic WAL record type, which describes changes
to pages in a generic way. This is useful for extensions that provide
@@ -99,4 +99,4 @@
comparison. This is not very compact for the case of moving data
within a page, and might be improved in the future.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/geqo-biblio.html b/doc/src/sgml/html/geqo-biblio.html
index 7fa0437..b998487 100644
--- a/doc/src/sgml/html/geqo-biblio.html
+++ b/doc/src/sgml/html/geqo-biblio.html
@@ -1,5 +1,5 @@
-62.4. Further Reading
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/geqo-intro.html b/doc/src/sgml/html/geqo-intro.html
index 3a7b39b..abaed8c 100644
--- a/doc/src/sgml/html/geqo-intro.html
+++ b/doc/src/sgml/html/geqo-intro.html
@@ -1,5 +1,5 @@
-62.1. Query Handling as a Complex Optimization Problem
62.1. Query Handling as a Complex Optimization Problem
62.1. Query Handling as a Complex Optimization Problem
Among all relational operators the most difficult one to process
and optimize is the join. The number of
possible query plans grows exponentially with the
@@ -33,4 +33,4 @@
genetic algorithm to solve the join
ordering problem in a manner that is efficient for queries
involving large numbers of joins.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/geqo-intro2.html b/doc/src/sgml/html/geqo-intro2.html
index bad186c..1dcf51c 100644
--- a/doc/src/sgml/html/geqo-intro2.html
+++ b/doc/src/sgml/html/geqo-intro2.html
@@ -1,5 +1,5 @@
-62.2. Genetic Algorithms
The genetic algorithm (GA) is a heuristic optimization method which
operates through randomized search. The set of possible solutions for the
optimization problem is considered as a
@@ -24,4 +24,4 @@
strongly that a GA is not a pure random search for a solution to a
problem. A GA uses stochastic processes, but the result is distinctly
non-random (better than random).
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/geqo-pg-intro.html b/doc/src/sgml/html/geqo-pg-intro.html
index 1f39468..a4754a4 100644
--- a/doc/src/sgml/html/geqo-pg-intro.html
+++ b/doc/src/sgml/html/geqo-pg-intro.html
@@ -1,5 +1,5 @@
-62.3. Genetic Query Optimization (GEQO) in PostgreSQL
62.3. Genetic Query Optimization (GEQO) in PostgreSQL
The GEQO module approaches the query
optimization problem as though it were the well-known traveling salesman
@@ -104,4 +104,4 @@
of the rest of the tour, but this is certainly not true for query
optimization. Thus it is questionable whether edge recombination
crossover is the most effective mutation procedure.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/geqo.html b/doc/src/sgml/html/geqo.html
index 89aef06..d2665f0 100644
--- a/doc/src/sgml/html/geqo.html
+++ b/doc/src/sgml/html/geqo.html
@@ -1,8 +1,8 @@
-Chapter 62. Genetic Query Optimizer
Written by Martin Utesch (<utesch@aut.tu-freiberg.de>)
for the Institute of Automatic Control at the University of Mining and Technology in Freiberg, Germany.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/gin-builtin-opclasses.html b/doc/src/sgml/html/gin-builtin-opclasses.html
index dfaaf8e..14cb7ea 100644
--- a/doc/src/sgml/html/gin-builtin-opclasses.html
+++ b/doc/src/sgml/html/gin-builtin-opclasses.html
@@ -1,5 +1,5 @@
-70.2. Built-in Operator Classes
The core PostgreSQL distribution
includes the GIN operator classes shown in
Table 70.1.
@@ -10,4 +10,4 @@
is the default. jsonb_path_ops supports fewer operators but
offers better performance for those operators.
See Section 8.14.4 for details.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/gin-examples.html b/doc/src/sgml/html/gin-examples.html
index 5c11957..c604127 100644
--- a/doc/src/sgml/html/gin-examples.html
+++ b/doc/src/sgml/html/gin-examples.html
@@ -1,5 +1,5 @@
-70.7. Examples
The core PostgreSQL distribution
includes the GIN operator classes previously shown in
Table 70.1.
@@ -7,4 +7,4 @@
GIN operator classes:
btree_gin
B-tree equivalent functionality for several data types
hstore
Module for storing (key, value) pairs
intarray
Enhanced support for int[]
pg_trgm
Text similarity using trigram matching
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/gin-extensibility.html b/doc/src/sgml/html/gin-extensibility.html
index deaa381..cc30160 100644
--- a/doc/src/sgml/html/gin-extensibility.html
+++ b/doc/src/sgml/html/gin-extensibility.html
@@ -1,5 +1,5 @@
-70.3. Extensibility
The GIN interface has a high level of abstraction,
requiring the access method implementer only to implement the semantics of
the data type being accessed. The GIN layer itself
@@ -234,4 +234,4 @@
recommended that the SQL declarations of these three support functions use
the opclass's indexed data type for the query argument, even
though the actual type might be something else depending on the operator.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/gin-implementation.html b/doc/src/sgml/html/gin-implementation.html
index d25e2f7..6a984be 100644
--- a/doc/src/sgml/html/gin-implementation.html
+++ b/doc/src/sgml/html/gin-implementation.html
@@ -1,5 +1,5 @@
-70.4. Implementation
Internally, a GIN index contains a B-tree index
constructed over keys, where each key is an element of one or more indexed
items (a member of an array, for example) and where each tuple in a leaf
@@ -61,4 +61,4 @@
index key, less than zero for a non-match that is still within the range
to be searched, or greater than zero if the index key is past the range
that could match.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/gin-intro.html b/doc/src/sgml/html/gin-intro.html
index 2159803..b68cbc8 100644
--- a/doc/src/sgml/html/gin-intro.html
+++ b/doc/src/sgml/html/gin-intro.html
@@ -1,5 +1,5 @@
-70.1. Introduction
GIN stands for Generalized Inverted Index.
GIN is designed for handling cases where the items
to be indexed are composite values, and the queries to be handled by
@@ -37,4 +37,4 @@
maintained by Teodor Sigaev and Oleg Bartunov. There is more
information about GIN on their
website.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/gin-limit.html b/doc/src/sgml/html/gin-limit.html
index 296e2fa..a009222 100644
--- a/doc/src/sgml/html/gin-limit.html
+++ b/doc/src/sgml/html/gin-limit.html
@@ -1,5 +1,5 @@
-70.6. Limitations
GIN assumes that indexable operators are strict. This
means that extractValue will not be called at all on a null
item value (instead, a placeholder index entry is created automatically),
@@ -7,4 +7,4 @@
value either (instead, the query is presumed to be unsatisfiable). Note
however that null key values contained within a non-null composite item
or query value are supported.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/gin-tips.html b/doc/src/sgml/html/gin-tips.html
index b5edd64..8d57cec 100644
--- a/doc/src/sgml/html/gin-tips.html
+++ b/doc/src/sgml/html/gin-tips.html
@@ -1,5 +1,5 @@
-70.5. GIN Tips and Tricks
Insertion into a GIN index can be slow
due to the likelihood of many keys being inserted for each item.
So, for bulk insertions into a table it is advisable to drop the GIN
@@ -55,4 +55,4 @@
From experience, values in the thousands (e.g., 5000 — 20000)
work well.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/gin.html b/doc/src/sgml/html/gin.html
index 03e10f6..d7d0b77 100644
--- a/doc/src/sgml/html/gin.html
+++ b/doc/src/sgml/html/gin.html
@@ -1,2 +1,2 @@
-Chapter 70. GIN Indexes
The core PostgreSQL distribution
includes the GiST operator classes shown in
Table 68.1.
(Some of the optional modules described in Appendix F
provide additional GiST operator classes.)
-
Table 68.1. Built-in GiST Operator Classes
Name
Indexable Operators
Ordering Operators
box_ops
<< (box, box)
<-> (box, point)
&< (box, box)
&& (box, box)
&> (box, box)
>> (box, box)
~= (box, box)
@> (box, box)
<@ (box, box)
&<| (box, box)
<<| (box, box)
|>> (box, box)
|&> (box, box)
~ (box, box)
@ (box, box)
circle_ops
<< (circle, circle)
<-> (circle, point)
&< (circle, circle)
&> (circle, circle)
>> (circle, circle)
<@ (circle, circle)
@> (circle, circle)
~= (circle, circle)
&& (circle, circle)
|>> (circle, circle)
<<| (circle, circle)
&<| (circle, circle)
|&> (circle, circle)
@ (circle, circle)
~ (circle, circle)
inet_ops
<< (inet, inet)
<<= (inet, inet)
>> (inet, inet)
>>= (inet, inet)
= (inet, inet)
<> (inet, inet)
< (inet, inet)
<= (inet, inet)
> (inet, inet)
>= (inet, inet)
&& (inet, inet)
multirange_ops
= (anymultirange, anymultirange)
&& (anymultirange, anymultirange)
&& (anymultirange, anyrange)
@> (anymultirange, anyelement)
@> (anymultirange, anymultirange)
@> (anymultirange, anyrange)
<@ (anymultirange, anymultirange)
<@ (anymultirange, anyrange)
<< (anymultirange, anymultirange)
<< (anymultirange, anyrange)
>> (anymultirange, anymultirange)
>> (anymultirange, anyrange)
&< (anymultirange, anymultirange)
&< (anymultirange, anyrange)
&> (anymultirange, anymultirange)
&> (anymultirange, anyrange)
-|- (anymultirange, anymultirange)
-|- (anymultirange, anyrange)
point_ops
|>> (point, point)
<-> (point, point)
<< (point, point)
>> (point, point)
<<| (point, point)
~= (point, point)
<@ (point, box)
<@ (point, polygon)
<@ (point, circle)
poly_ops
<< (polygon, polygon)
<-> (polygon, point)
&< (polygon, polygon)
&> (polygon, polygon)
>> (polygon, polygon)
<@ (polygon, polygon)
@> (polygon, polygon)
~= (polygon, polygon)
&& (polygon, polygon)
<<| (polygon, polygon)
&<| (polygon, polygon)
|&> (polygon, polygon)
|>> (polygon, polygon)
@ (polygon, polygon)
~ (polygon, polygon)
range_ops
= (anyrange, anyrange)
&& (anyrange, anyrange)
&& (anyrange, anymultirange)
@> (anyrange, anyelement)
@> (anyrange, anyrange)
@> (anyrange, anymultirange)
<@ (anyrange, anyrange)
<@ (anyrange, anymultirange)
<< (anyrange, anyrange)
<< (anyrange, anymultirange)
>> (anyrange, anyrange)
>> (anyrange, anymultirange)
&< (anyrange, anyrange)
&< (anyrange, anymultirange)
&> (anyrange, anyrange)
&> (anyrange, anymultirange)
-|- (anyrange, anyrange)
-|- (anyrange, anymultirange)
tsquery_ops
<@ (tsquery, tsquery)
@> (tsquery, tsquery)
tsvector_ops
@@ (tsvector, tsquery)
+
Table 68.1. Built-in GiST Operator Classes
Name
Indexable Operators
Ordering Operators
box_ops
<< (box, box)
<-> (box, point)
&< (box, box)
&& (box, box)
&> (box, box)
>> (box, box)
~= (box, box)
@> (box, box)
<@ (box, box)
&<| (box, box)
<<| (box, box)
|>> (box, box)
|&> (box, box)
circle_ops
<< (circle, circle)
<-> (circle, point)
&< (circle, circle)
&> (circle, circle)
>> (circle, circle)
<@ (circle, circle)
@> (circle, circle)
~= (circle, circle)
&& (circle, circle)
|>> (circle, circle)
<<| (circle, circle)
&<| (circle, circle)
|&> (circle, circle)
inet_ops
<< (inet, inet)
<<= (inet, inet)
>> (inet, inet)
>>= (inet, inet)
= (inet, inet)
<> (inet, inet)
< (inet, inet)
<= (inet, inet)
> (inet, inet)
>= (inet, inet)
&& (inet, inet)
multirange_ops
= (anymultirange, anymultirange)
&& (anymultirange, anymultirange)
&& (anymultirange, anyrange)
@> (anymultirange, anyelement)
@> (anymultirange, anymultirange)
@> (anymultirange, anyrange)
<@ (anymultirange, anymultirange)
<@ (anymultirange, anyrange)
<< (anymultirange, anymultirange)
<< (anymultirange, anyrange)
>> (anymultirange, anymultirange)
>> (anymultirange, anyrange)
&< (anymultirange, anymultirange)
&< (anymultirange, anyrange)
&> (anymultirange, anymultirange)
&> (anymultirange, anyrange)
-|- (anymultirange, anymultirange)
-|- (anymultirange, anyrange)
point_ops
|>> (point, point)
<-> (point, point)
<< (point, point)
>> (point, point)
<<| (point, point)
~= (point, point)
<@ (point, box)
<@ (point, polygon)
<@ (point, circle)
poly_ops
<< (polygon, polygon)
<-> (polygon, point)
&< (polygon, polygon)
&> (polygon, polygon)
>> (polygon, polygon)
<@ (polygon, polygon)
@> (polygon, polygon)
~= (polygon, polygon)
&& (polygon, polygon)
<<| (polygon, polygon)
&<| (polygon, polygon)
|&> (polygon, polygon)
|>> (polygon, polygon)
range_ops
= (anyrange, anyrange)
&& (anyrange, anyrange)
&& (anyrange, anymultirange)
@> (anyrange, anyelement)
@> (anyrange, anyrange)
@> (anyrange, anymultirange)
<@ (anyrange, anyrange)
<@ (anyrange, anymultirange)
<< (anyrange, anyrange)
<< (anyrange, anymultirange)
>> (anyrange, anyrange)
>> (anyrange, anymultirange)
&< (anyrange, anyrange)
&< (anyrange, anymultirange)
&> (anyrange, anyrange)
&> (anyrange, anymultirange)
-|- (anyrange, anyrange)
-|- (anyrange, anymultirange)
tsquery_ops
<@ (tsquery, tsquery)
@> (tsquery, tsquery)
tsvector_ops
@@ (tsvector, tsquery)
For historical reasons, the inet_ops operator class is
not the default class for types inet and cidr.
To use it, mention the class name in CREATE INDEX,
@@ -13,4 +13,4 @@
CREATE INDEX ON my_table USING GIST (my_inet_column inet_ops);
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/gist-examples.html b/doc/src/sgml/html/gist-examples.html
index 6a7a338..8d20192 100644
--- a/doc/src/sgml/html/gist-examples.html
+++ b/doc/src/sgml/html/gist-examples.html
@@ -1,5 +1,5 @@
-68.5. Examples
The PostgreSQL source distribution includes
several examples of index methods implemented using
GiST. The core system currently provides text search
@@ -10,4 +10,4 @@
operator classes:
btree_gist
B-tree equivalent functionality for several data types
cube
Indexing for multidimensional cubes
hstore
Module for storing (key, value) pairs
intarray
RD-Tree for one-dimensional array of int4 values
ltree
Indexing for tree-like structures
pg_trgm
Text similarity using trigram matching
seg
Indexing for “float ranges”
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/gist-extensibility.html b/doc/src/sgml/html/gist-extensibility.html
index d2b4e52..c07899d 100644
--- a/doc/src/sgml/html/gist-extensibility.html
+++ b/doc/src/sgml/html/gist-extensibility.html
@@ -1,5 +1,5 @@
-68.3. Extensibility
Traditionally, implementing a new index access method meant a lot of
difficult work. It was necessary to understand the inner workings of the
database, such as the lock manager and Write-Ahead Log. The
@@ -810,4 +810,4 @@ my_sortsupport(PG_FUNCTION_ARGS)
index scan, index build, or index tuple insertion). Be careful to pfree
the previous value when replacing a fn_extra value, or the leak
will accumulate for the duration of the operation.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/gist-implementation.html b/doc/src/sgml/html/gist-implementation.html
index c3b1548..f9b69bb 100644
--- a/doc/src/sgml/html/gist-implementation.html
+++ b/doc/src/sgml/html/gist-implementation.html
@@ -1,5 +1,5 @@
-68.4. Implementation
The simplest way to build a GiST index is just to insert all the entries,
one by one. This tends to be slow for large indexes, because if the
index tuples are scattered across the index and the index is large enough
@@ -35,4 +35,4 @@
CREATE INDEX command. The default behavior is good for most cases, but
turning buffering off might speed up the build somewhat if the input data
is ordered.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/gist-intro.html b/doc/src/sgml/html/gist-intro.html
index 1a86c60..e986c33 100644
--- a/doc/src/sgml/html/gist-intro.html
+++ b/doc/src/sgml/html/gist-intro.html
@@ -1,5 +1,5 @@
-68.1. Introduction
GiST stands for Generalized Search Tree. It is a
balanced, tree-structured access method, that acts as a base template in
which to implement arbitrary indexing schemes. B-trees, R-trees and many
@@ -20,4 +20,4 @@
maintained by Teodor Sigaev and Oleg Bartunov, and there is more
information on their
web site.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/gist.html b/doc/src/sgml/html/gist.html
index 6206348..0e63601 100644
--- a/doc/src/sgml/html/gist.html
+++ b/doc/src/sgml/html/gist.html
@@ -1,2 +1,2 @@
-Chapter 68. GiST Indexes
\ No newline at end of file
diff --git a/doc/src/sgml/html/git.html b/doc/src/sgml/html/git.html
index 687849f..3f73203 100644
--- a/doc/src/sgml/html/git.html
+++ b/doc/src/sgml/html/git.html
@@ -1,5 +1,5 @@
-I.1. Getting the Source via Git
With Git you will make a copy of the entire code repository
on your local machine, so you will have access to all history and branches
offline. This is the fastest and most flexible way to develop or test
@@ -39,4 +39,4 @@ git fetch
Git can do a lot more things than just fetch the source. For
more information, consult the Git man pages, or see the
website at https://git-scm.com.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/glossary.html b/doc/src/sgml/html/glossary.html
index d740b71..354ebe1 100644
--- a/doc/src/sgml/html/glossary.html
+++ b/doc/src/sgml/html/glossary.html
@@ -1,5 +1,5 @@
-Appendix M. Glossary
This is a list of terms and their meaning in the context of
PostgreSQL and relational database
systems in general.
@@ -1067,4 +1067,4 @@
It comprises many individual
WAL records written
sequentially to WAL files.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/gssapi-auth.html b/doc/src/sgml/html/gssapi-auth.html
index 1122ada..ef63962 100644
--- a/doc/src/sgml/html/gssapi-auth.html
+++ b/doc/src/sgml/html/gssapi-auth.html
@@ -1,8 +1,8 @@
-21.6. GSSAPI Authentication
GSSAPI is an industry-standard protocol
for secure authentication defined in
- RFC 2743.
+ RFC 2743.
PostgreSQL
supports GSSAPI for authentication,
communications encryption, or both.
@@ -115,4 +115,4 @@
parameter. If that is set to true, client principals are matched to
user map entries case-insensitively. krb_realm, if
set, is also matched case-insensitively.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/gssapi-enc.html b/doc/src/sgml/html/gssapi-enc.html
index fa613f6..93b55c9 100644
--- a/doc/src/sgml/html/gssapi-enc.html
+++ b/doc/src/sgml/html/gssapi-enc.html
@@ -1,5 +1,5 @@
-19.10. Secure TCP/IP Connections with GSSAPI Encryption
19.10. Secure TCP/IP Connections with GSSAPI Encryption
PostgreSQL also has native support for
using GSSAPI to encrypt client/server communications for
increased security. Support requires that a GSSAPI
@@ -28,4 +28,4 @@
behavior, GSSAPI encryption requires no setup beyond
that which is necessary for GSSAPI authentication. (For more information
on configuring that, see Section 21.6.)
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/hash-implementation.html b/doc/src/sgml/html/hash-implementation.html
index 66104bc..83f2b29 100644
--- a/doc/src/sgml/html/hash-implementation.html
+++ b/doc/src/sgml/html/hash-implementation.html
@@ -1,5 +1,5 @@
-72.2. Implementation
There are four kinds of pages in a hash index: the meta page (page zero),
which contains statically allocated control information; primary bucket
pages; overflow pages; and bitmap pages, which keep track of overflow
@@ -33,4 +33,4 @@
src/backend/access/hash/README.
The split algorithm is crash safe and can be restarted if not completed
successfully.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/hash-index.html b/doc/src/sgml/html/hash-index.html
index 349462a..c5dda6b 100644
--- a/doc/src/sgml/html/hash-index.html
+++ b/doc/src/sgml/html/hash-index.html
@@ -1,2 +1,2 @@
-Chapter 72. Hash Indexes
\ No newline at end of file
diff --git a/doc/src/sgml/html/hash-intro.html b/doc/src/sgml/html/hash-intro.html
index f73c5a1..2415791 100644
--- a/doc/src/sgml/html/hash-intro.html
+++ b/doc/src/sgml/html/hash-intro.html
@@ -1,5 +1,5 @@
-72.1. Overview
PostgreSQL
includes an implementation of persistent on-disk hash indexes,
which are fully crash recoverable. Any data type can be indexed by a
@@ -74,4 +74,4 @@
The expansion occurs in the foreground, which could increase execution
time for user inserts. Thus, hash indexes may not be suitable for tables
with rapidly increasing number of rows.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/high-availability.html b/doc/src/sgml/html/high-availability.html
index 4074fb3..cd9624f 100644
--- a/doc/src/sgml/html/high-availability.html
+++ b/doc/src/sgml/html/high-availability.html
@@ -1,5 +1,5 @@
-Chapter 27. High Availability, Load Balancing, and Replication
Chapter 27. High Availability, Load Balancing, and Replication
Database servers can work together to allow a second server to
take over quickly if the primary server fails (high
availability), or to allow several computers to serve the same
@@ -54,4 +54,4 @@
The remainder of this section outlines various failover, replication,
and load balancing solutions.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/history.html b/doc/src/sgml/html/history.html
index 78e9d71..1045fcb 100644
--- a/doc/src/sgml/html/history.html
+++ b/doc/src/sgml/html/history.html
@@ -1,5 +1,5 @@
-2. A Brief History of PostgreSQL
The object-relational database management system now known as
PostgreSQL is derived from the
POSTGRES package written at the
@@ -137,4 +137,4 @@
Details about what has happened in PostgreSQL since
then can be found in Appendix E.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/hot-standby.html b/doc/src/sgml/html/hot-standby.html
index 44443c8..5dba8e0 100644
--- a/doc/src/sgml/html/hot-standby.html
+++ b/doc/src/sgml/html/hot-standby.html
@@ -1,5 +1,5 @@
-27.4. Hot Standby
Hot standby is the term used to describe the ability to connect to
the server and run read-only queries while the server is in archive
recovery or standby mode. This
@@ -572,4 +572,4 @@ HINT: You can then restart the server after making the necessary configuration
hot standby mode will generate an error.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/how-parallel-query-works.html b/doc/src/sgml/html/how-parallel-query-works.html
index 740aa11..18cab3a 100644
--- a/doc/src/sgml/html/how-parallel-query-works.html
+++ b/doc/src/sgml/html/how-parallel-query-works.html
@@ -1,5 +1,5 @@
-15.1. How Parallel Query Works
When the optimizer determines that parallel query is the fastest execution
strategy for a particular query, it will create a query plan that includes
a Gather or Gather Merge
@@ -68,4 +68,4 @@ EXPLAIN SELECT * FROM pgbench_accounts WHERE filler LIKE '%x%';
order-preserving merge. In contrast, Gather reads tuples
from the workers in whatever order is convenient, destroying any sort
order that may have existed.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/hstore.html b/doc/src/sgml/html/hstore.html
index ea788bb..3f707c6 100644
--- a/doc/src/sgml/html/hstore.html
+++ b/doc/src/sgml/html/hstore.html
@@ -1,5 +1,5 @@
-F.18. hstore
This module implements the hstore data type for storing sets of
key/value pairs within a single PostgreSQL value.
This can be useful in various scenarios, such as rows with many attributes
@@ -696,4 +696,4 @@ ALTER TABLE tablename ALTER hstorecol TYPE hstore USING hstorecol || '';
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/index-api.html b/doc/src/sgml/html/index-api.html
index ec365e2..25e00d8 100644
--- a/doc/src/sgml/html/index-api.html
+++ b/doc/src/sgml/html/index-api.html
@@ -1,5 +1,5 @@
-64.1. Basic API Structure for Indexes
Each index access method is described by a row in the
pg_am
system catalog. The pg_am entry
@@ -177,4 +177,4 @@ typedef struct IndexAmRoutine
sensible: it means that there can only be one key column, but there can
also be included column(s). Also, included columns must be allowed to be
null, independently of amoptionalkey.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/index-cost-estimation.html b/doc/src/sgml/html/index-cost-estimation.html
index 197d688..a5f363b 100644
--- a/doc/src/sgml/html/index-cost-estimation.html
+++ b/doc/src/sgml/html/index-cost-estimation.html
@@ -1,5 +1,5 @@
-64.6. Index Cost Estimation Functions
The amcostestimate function is given information describing
a possible index scan, including lists of WHERE and ORDER BY clauses that
have been determined to be usable with the index. It must return estimates
@@ -139,4 +139,4 @@ cost_qual_eval(&index_qual_cost, path->indexquals, root);
Examples of cost estimator functions can be found in
src/backend/utils/adt/selfuncs.c.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/index-functions.html b/doc/src/sgml/html/index-functions.html
index fbbd95e..1f6da1c 100644
--- a/doc/src/sgml/html/index-functions.html
+++ b/doc/src/sgml/html/index-functions.html
@@ -1,5 +1,5 @@
-64.2. Index Access Method Functions
The index construction and maintenance functions that an index access
method must provide in IndexAmRoutine are:
@@ -484,4 +484,4 @@ amparallelrescan (IndexScanDesc scan);
must be restarted. It should reset any shared state set up by
aminitparallelscan such that the scan will be restarted from
the beginning.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/index-locking.html b/doc/src/sgml/html/index-locking.html
index 8bf3ae1..6bce0d3 100644
--- a/doc/src/sgml/html/index-locking.html
+++ b/doc/src/sgml/html/index-locking.html
@@ -1,5 +1,5 @@
-64.4. Index Locking Considerations
Index access methods must handle concurrent updates
of the index by multiple processes.
The core PostgreSQL system obtains
@@ -88,4 +88,4 @@
integrity. When the flag is set, it indicates that the index access
method implements finer-grained predicate locking, which will tend to
reduce the frequency of such transaction cancellations.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/index-scanning.html b/doc/src/sgml/html/index-scanning.html
index 6ba0e2e..e51c4d1 100644
--- a/doc/src/sgml/html/index-scanning.html
+++ b/doc/src/sgml/html/index-scanning.html
@@ -1,5 +1,5 @@
-64.3. Index Scanning
In an index scan, the index access method is responsible for regurgitating
the TIDs of all the tuples it has been told about that match the
scan keys. The access method is not involved in
@@ -120,4 +120,4 @@
Note that it is permitted for an access method to implement only
amgetbitmap and not amgettuple, or vice versa,
if its internal implementation is unsuited to one API or the other.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/index-unique-checks.html b/doc/src/sgml/html/index-unique-checks.html
index 07a62e1..52f0bdf 100644
--- a/doc/src/sgml/html/index-unique-checks.html
+++ b/doc/src/sgml/html/index-unique-checks.html
@@ -1,5 +1,5 @@
-64.5. Index Uniqueness Checks
PostgreSQL enforces SQL uniqueness constraints
using unique indexes, which are indexes that disallow
multiple entries with identical keys. An access method that supports this
@@ -106,4 +106,4 @@
target row is found in the recheck verifies that we are scanning
for the same tuple values as were used in the original insertion.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/index.html b/doc/src/sgml/html/index.html
index 4d7b437..fa1df0e 100644
--- a/doc/src/sgml/html/index.html
+++ b/doc/src/sgml/html/index.html
@@ -1,2 +1,2 @@
-PostgreSQL 15.6 Documentation
\ No newline at end of file
diff --git a/doc/src/sgml/html/indexam.html b/doc/src/sgml/html/indexam.html
index 6a495f8..5112271 100644
--- a/doc/src/sgml/html/indexam.html
+++ b/doc/src/sgml/html/indexam.html
@@ -1,5 +1,5 @@
-Chapter 64. Index Access Method Interface Definition
Chapter 64. Index Access Method Interface Definition
This chapter defines the interface between the core
PostgreSQL system and index access
methods, which manage individual index types. The core system
@@ -32,4 +32,4 @@
statement; but indexes do not deal with those, either.) Index entries for
dead tuples are reclaimed (by vacuuming) when the dead tuples themselves
are reclaimed.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/indexes-bitmap-scans.html b/doc/src/sgml/html/indexes-bitmap-scans.html
index 71986de..6eddb2a 100644
--- a/doc/src/sgml/html/indexes-bitmap-scans.html
+++ b/doc/src/sgml/html/indexes-bitmap-scans.html
@@ -1,5 +1,5 @@
-11.5. Combining Multiple Indexes
A single index scan can only use query clauses that use the index's
columns with operators of its operator class and are joined with
AND. For example, given an index on (a, b)
@@ -58,4 +58,4 @@
common. If one of the types of query is much less common than the
others, you'd probably settle for creating just the two indexes that
best match the common types.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/indexes-collations.html b/doc/src/sgml/html/indexes-collations.html
index 80ab030..6cf0cc6 100644
--- a/doc/src/sgml/html/indexes-collations.html
+++ b/doc/src/sgml/html/indexes-collations.html
@@ -1,5 +1,5 @@
-11.11. Indexes and Collations
An index can support only one collation per index column.
If multiple collations are of interest, multiple indexes may be needed.
@@ -28,4 +28,4 @@ SELECT * FROM test1c WHERE content > constant
CREATE INDEX test1c_content_y_index ON test1c (content COLLATE "y");
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/indexes-examine.html b/doc/src/sgml/html/indexes-examine.html
index 0077928..4b8a7de 100644
--- a/doc/src/sgml/html/indexes-examine.html
+++ b/doc/src/sgml/html/indexes-examine.html
@@ -1,5 +1,5 @@
-11.12. Examining Index Usage
Although indexes in PostgreSQL do not need
maintenance or tuning, it is still important to check
which indexes are actually used by the real-life query workload.
@@ -79,4 +79,4 @@
appropriate, then you might have to resort to forcing index usage
explicitly. You might also want to contact the
PostgreSQL developers to examine the issue.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/indexes-expressional.html b/doc/src/sgml/html/indexes-expressional.html
index f3e3d0a..065e603 100644
--- a/doc/src/sgml/html/indexes-expressional.html
+++ b/doc/src/sgml/html/indexes-expressional.html
@@ -1,5 +1,5 @@
-11.7. Indexes on Expressions
An index column need not be just a column of the underlying table,
but can be a function or scalar expression computed from one or
more columns of the table. This feature is useful to obtain fast
@@ -46,4 +46,4 @@ CREATE INDEX people_names ON people ((first_name || ' ' || last_name));
and so the speed of the search is equivalent to any other simple index
query. Thus, indexes on expressions are useful when retrieval speed
is more important than insertion and update speed.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/indexes-index-only-scans.html b/doc/src/sgml/html/indexes-index-only-scans.html
index 18089c3..0bf95f2 100644
--- a/doc/src/sgml/html/indexes-index-only-scans.html
+++ b/doc/src/sgml/html/indexes-index-only-scans.html
@@ -1,5 +1,5 @@
-11.9. Index-Only Scans and Covering Indexes
All indexes in PostgreSQL
are secondary indexes, meaning that each index is
stored separately from the table's main data area (which is called the
@@ -206,4 +206,4 @@ SELECT target FROM tests WHERE subject = 'some-subject' AND success;
checked in the plan. PostgreSQL versions 9.6
and later will recognize such cases and allow index-only scans to be
generated, but older versions will not.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/indexes-intro.html b/doc/src/sgml/html/indexes-intro.html
index 2dadf9a..c1689f8 100644
--- a/doc/src/sgml/html/indexes-intro.html
+++ b/doc/src/sgml/html/indexes-intro.html
@@ -1,5 +1,5 @@
-11.1. Introduction
CREATE TABLE test1 (
@@ -103,4 +103,4 @@ CREATE INDEX test1_id_index ON test1 (id);
tuples.
Therefore indexes that are seldom or never used in queries
should be removed.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/indexes-multicolumn.html b/doc/src/sgml/html/indexes-multicolumn.html
index 063e0b8..95d71aa 100644
--- a/doc/src/sgml/html/indexes-multicolumn.html
+++ b/doc/src/sgml/html/indexes-multicolumn.html
@@ -1,5 +1,5 @@
-11.3. Multicolumn Indexes
An index can be defined on more than one column of a table. For example, if
you have a table of this form:
@@ -79,4 +79,4 @@ CREATE INDEX test2_mm_idx ON test2 (major, minor);
Section 11.5 and
Section 11.9 for some discussion of the
merits of different index configurations.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/indexes-opclass.html b/doc/src/sgml/html/indexes-opclass.html
index f837067..d315f07 100644
--- a/doc/src/sgml/html/indexes-opclass.html
+++ b/doc/src/sgml/html/indexes-opclass.html
@@ -1,5 +1,5 @@
-11.10. Operator Classes and Operator Families
An index definition can specify an operator
class for each column of an index.
@@ -104,4 +104,4 @@ SELECT am.amname AS index_method,
commands \dAc, \dAf,
and \dAo, which provide slightly more sophisticated
versions of these queries.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/indexes-ordering.html b/doc/src/sgml/html/indexes-ordering.html
index 3ad0c58..49e364e 100644
--- a/doc/src/sgml/html/indexes-ordering.html
+++ b/doc/src/sgml/html/indexes-ordering.html
@@ -1,5 +1,5 @@
-11.4. Indexes and ORDER BY
In addition to simply finding the rows to be returned by a query,
an index may be able to deliver them in a specific sorted order.
This allows a query's ORDER BY specification to be honored
@@ -61,4 +61,4 @@ CREATE INDEX test3_desc_index ON test3 (id DESC NULLS LAST);
speedups for certain queries. Whether it's worth maintaining such an
index depends on how often you use queries that require a special
sort ordering.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/indexes-partial.html b/doc/src/sgml/html/indexes-partial.html
index 9b752b5..1fae4d4 100644
--- a/doc/src/sgml/html/indexes-partial.html
+++ b/doc/src/sgml/html/indexes-partial.html
@@ -1,5 +1,5 @@
-11.8. Partial Indexes
A partial index is an index built over a
subset of a table; the subset is defined by a conditional
expression (called the predicate of the
@@ -209,4 +209,4 @@ CREATE INDEX mytable_cat_data ON mytable (category, data);
far better performance is possible.
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/indexes-types.html b/doc/src/sgml/html/indexes-types.html
index c5c8e25..23c4738 100644
--- a/doc/src/sgml/html/indexes-types.html
+++ b/doc/src/sgml/html/indexes-types.html
@@ -1,5 +1,5 @@
-11.2. Index Types
PostgreSQL provides several index types:
B-tree, Hash, GiST, SP-GiST, GIN, BRIN, and the extension bloom.
Each index type uses a different
@@ -159,4 +159,4 @@ SELECT * FROM places ORDER BY location <-> point '(101,456)' LIMIT 10;
The BRIN operator classes included in the standard distribution are
documented in Table 71.1.
For more information see Chapter 71.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/indexes-unique.html b/doc/src/sgml/html/indexes-unique.html
index e7bc514..7d5734b 100644
--- a/doc/src/sgml/html/indexes-unique.html
+++ b/doc/src/sgml/html/indexes-unique.html
@@ -1,5 +1,5 @@
-11.6. Unique Indexes
Indexes can also be used to enforce uniqueness of a column's value,
or the uniqueness of the combined values of more than one column.
@@ -23,4 +23,4 @@ CREATE UNIQUE INDEX name ON
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/indexes.html b/doc/src/sgml/html/indexes.html
index 423ef9b..232b509 100644
--- a/doc/src/sgml/html/indexes.html
+++ b/doc/src/sgml/html/indexes.html
@@ -1,8 +1,8 @@
-Chapter 11. Indexes
Indexes are a common way to enhance database performance. An index
allows the database server to find and retrieve specific rows much
faster than it could do without an index. But indexes also add
overhead to the database system as a whole, so they should be used
sensibly.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/information-schema.html b/doc/src/sgml/html/information-schema.html
index da50149..c5168ae 100644
--- a/doc/src/sgml/html/information-schema.html
+++ b/doc/src/sgml/html/information-schema.html
@@ -1,5 +1,5 @@
-Chapter 37. The Information Schema
The information schema consists of a set of views that contain
information about the objects defined in the current database. The
information schema is defined in the SQL standard and can therefore
@@ -28,4 +28,4 @@
issues but contain the table name to help distinguish duplicate
rows, e.g., constraint_column_usage,
constraint_table_usage, table_constraints.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-administrable-role-authorizations.html b/doc/src/sgml/html/infoschema-administrable-role-authorizations.html
index ebdf439..617966d 100644
--- a/doc/src/sgml/html/infoschema-administrable-role-authorizations.html
+++ b/doc/src/sgml/html/infoschema-administrable-role-authorizations.html
@@ -1,5 +1,5 @@
-37.4. administrable_role_authorizations
The view administrable_role_authorizations
identifies all roles that the current user has the admin option
for.
@@ -25,4 +25,4 @@
Always YES
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-applicable-roles.html b/doc/src/sgml/html/infoschema-applicable-roles.html
index ee28362..55b46f7 100644
--- a/doc/src/sgml/html/infoschema-applicable-roles.html
+++ b/doc/src/sgml/html/infoschema-applicable-roles.html
@@ -1,5 +1,5 @@
-37.5. applicable_roles
The view applicable_roles identifies all roles
whose privileges the current user can use. This means there is
some chain of role grants from the current user to the role in
@@ -30,4 +30,4 @@
YES if the grantee has the admin option on
the role, NO if not
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-attributes.html b/doc/src/sgml/html/infoschema-attributes.html
index fd6a733..ae17373 100644
--- a/doc/src/sgml/html/infoschema-attributes.html
+++ b/doc/src/sgml/html/infoschema-attributes.html
@@ -1,5 +1,5 @@
-37.6. attributes
The view attributes contains information about
the attributes of composite data types defined in the database.
(Note that the view does not give information about table columns,
@@ -223,4 +223,4 @@
See also under Section 37.17, a similarly
structured view, for further information on some of the columns.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-character-sets.html b/doc/src/sgml/html/infoschema-character-sets.html
index ef3ad3c..41c6f2d 100644
--- a/doc/src/sgml/html/infoschema-character-sets.html
+++ b/doc/src/sgml/html/infoschema-character-sets.html
@@ -1,5 +1,5 @@
-37.7. character_sets
The view character_sets identifies the character
sets available in the current database. Since PostgreSQL does not
support multiple character sets within one database, this view only
@@ -83,4 +83,4 @@
settings of the current database. If there is no such
collation, then this column and the associated schema and
catalog columns are null.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-check-constraint-routine-usage.html b/doc/src/sgml/html/infoschema-check-constraint-routine-usage.html
index ab27fe1..886b67e 100644
--- a/doc/src/sgml/html/infoschema-check-constraint-routine-usage.html
+++ b/doc/src/sgml/html/infoschema-check-constraint-routine-usage.html
@@ -1,5 +1,5 @@
-37.8. check_constraint_routine_usage
The view check_constraint_routine_usage
identifies routines (functions and procedures) that are used by a
check constraint. Only those routines are shown that are owned by
@@ -39,4 +39,4 @@
The “specific name” of the function. See Section 37.45 for more information.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-check-constraints.html b/doc/src/sgml/html/infoschema-check-constraints.html
index 14263be..88ecb02 100644
--- a/doc/src/sgml/html/infoschema-check-constraints.html
+++ b/doc/src/sgml/html/infoschema-check-constraints.html
@@ -1,5 +1,5 @@
-37.9. check_constraints
The view check_constraints contains all check
constraints, either defined on a table or on a domain, that are
owned by a currently enabled role. (The owner of the table or
@@ -29,4 +29,4 @@
The check expression of the check constraint
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-collation-character-set-applicab.html b/doc/src/sgml/html/infoschema-collation-character-set-applicab.html
index af15061..4b771df 100644
--- a/doc/src/sgml/html/infoschema-collation-character-set-applicab.html
+++ b/doc/src/sgml/html/infoschema-collation-character-set-applicab.html
@@ -1,5 +1,5 @@
-37.11. collation_character_set_applicability
The view collation_character_set_applicability
identifies which character set the available collations are
applicable to. In PostgreSQL, there is only one character set per
@@ -41,4 +41,4 @@
Name of the character set
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-collations.html b/doc/src/sgml/html/infoschema-collations.html
index f5256b0..a165d91 100644
--- a/doc/src/sgml/html/infoschema-collations.html
+++ b/doc/src/sgml/html/infoschema-collations.html
@@ -1,5 +1,5 @@
-37.10. collations
The view collations contains the collations
available in the current database.
Table 37.8. collations Columns
@@ -28,4 +28,4 @@
Always NO PAD (The alternative PAD
SPACE is not supported by PostgreSQL.)
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-column-column-usage.html b/doc/src/sgml/html/infoschema-column-column-usage.html
index 62c87f3..15ff89b 100644
--- a/doc/src/sgml/html/infoschema-column-column-usage.html
+++ b/doc/src/sgml/html/infoschema-column-column-usage.html
@@ -1,5 +1,5 @@
-37.12. column_column_usage
The view column_column_usage identifies all generated
columns that depend on another base column in the same table. Only tables
owned by a currently enabled role are included.
@@ -33,4 +33,4 @@
Name of the generated column
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-column-domain-usage.html b/doc/src/sgml/html/infoschema-column-domain-usage.html
index 10badd9..8d9fbe5 100644
--- a/doc/src/sgml/html/infoschema-column-domain-usage.html
+++ b/doc/src/sgml/html/infoschema-column-domain-usage.html
@@ -1,5 +1,5 @@
-37.13. column_domain_usage
The view column_domain_usage identifies all
columns (of a table or a view) that make use of some domain defined
in the current database and owned by a currently enabled role.
@@ -43,4 +43,4 @@
Name of the column
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-column-options.html b/doc/src/sgml/html/infoschema-column-options.html
index 2a07508..cec1a9d 100644
--- a/doc/src/sgml/html/infoschema-column-options.html
+++ b/doc/src/sgml/html/infoschema-column-options.html
@@ -1,5 +1,5 @@
-37.14. column_options
The view column_options contains all the
options defined for foreign table columns in the current database. Only
those foreign table columns are shown that the current user has access to
@@ -39,4 +39,4 @@
Value of the option
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-column-privileges.html b/doc/src/sgml/html/infoschema-column-privileges.html
index ea0738d..1f874d4 100644
--- a/doc/src/sgml/html/infoschema-column-privileges.html
+++ b/doc/src/sgml/html/infoschema-column-privileges.html
@@ -1,5 +1,5 @@
-37.15. column_privileges
The view column_privileges identifies all
privileges granted on columns to a currently enabled role or by a
currently enabled role. There is one row for each combination of
@@ -57,4 +57,4 @@
YES if the privilege is grantable, NO if not
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-column-udt-usage.html b/doc/src/sgml/html/infoschema-column-udt-usage.html
index 879f8c6..9ee2b6e 100644
--- a/doc/src/sgml/html/infoschema-column-udt-usage.html
+++ b/doc/src/sgml/html/infoschema-column-udt-usage.html
@@ -1,5 +1,5 @@
-37.16. column_udt_usage
The view column_udt_usage identifies all columns
that use data types owned by a currently enabled role. Note that in
PostgreSQL, built-in data types behave
@@ -49,4 +49,4 @@
Name of the column
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-columns.html b/doc/src/sgml/html/infoschema-columns.html
index 21a5428..736c641 100644
--- a/doc/src/sgml/html/infoschema-columns.html
+++ b/doc/src/sgml/html/infoschema-columns.html
@@ -1,5 +1,5 @@
-37.17. columns
The view columns contains information about all
table columns (or view columns) in the database. System columns
(ctid, etc.) are not included. Only those columns are
@@ -334,4 +334,4 @@
columns with their associated data types and treat domains as
separate types, you could write coalesce(domain_name,
udt_name), etc.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-constraint-column-usage.html b/doc/src/sgml/html/infoschema-constraint-column-usage.html
index 52b4c5d..6c18d8e 100644
--- a/doc/src/sgml/html/infoschema-constraint-column-usage.html
+++ b/doc/src/sgml/html/infoschema-constraint-column-usage.html
@@ -1,5 +1,5 @@
-37.18. constraint_column_usage
The view constraint_column_usage identifies all
columns in the current database that are used by some constraint.
Only those columns are shown that are contained in a table owned by
@@ -52,4 +52,4 @@
Name of the constraint
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-constraint-table-usage.html b/doc/src/sgml/html/infoschema-constraint-table-usage.html
index 0a97df2..baba47a 100644
--- a/doc/src/sgml/html/infoschema-constraint-table-usage.html
+++ b/doc/src/sgml/html/infoschema-constraint-table-usage.html
@@ -1,5 +1,5 @@
-37.19. constraint_table_usage
The view constraint_table_usage identifies all
tables in the current database that are used by some constraint and
are owned by a currently enabled role. (This is different from the
@@ -47,4 +47,4 @@
Name of the constraint
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-data-type-privileges.html b/doc/src/sgml/html/infoschema-data-type-privileges.html
index dd49680..f6971e2 100644
--- a/doc/src/sgml/html/infoschema-data-type-privileges.html
+++ b/doc/src/sgml/html/infoschema-data-type-privileges.html
@@ -1,5 +1,5 @@
-37.20. data_type_privileges
The view data_type_privileges identifies all
data type descriptors that the current user has access to, by way
of being the owner of the described object or having some privilege
@@ -49,4 +49,4 @@
The identifier of the data type descriptor, which is unique
among the data type descriptors for that same object.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-datatypes.html b/doc/src/sgml/html/infoschema-datatypes.html
index fd5e1ba..0b2fd8b 100644
--- a/doc/src/sgml/html/infoschema-datatypes.html
+++ b/doc/src/sgml/html/infoschema-datatypes.html
@@ -1,5 +1,5 @@
-37.2. Data Types
The columns of the information schema views use special data types
that are defined in the information schema. These are defined as
simple domains over ordinary built-in types. You should not use
@@ -30,4 +30,4 @@
Every column in the information schema has one of these five types.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-domain-constraints.html b/doc/src/sgml/html/infoschema-domain-constraints.html
index 1a70548..8de1139 100644
--- a/doc/src/sgml/html/infoschema-domain-constraints.html
+++ b/doc/src/sgml/html/infoschema-domain-constraints.html
@@ -1,5 +1,5 @@
-37.21. domain_constraints
The view domain_constraints contains all constraints
belonging to domains defined in the current database. Only those domains
are shown that the current user has access to (by way of being the owner or
@@ -49,4 +49,4 @@
YES if the constraint is deferrable and initially deferred, NO if not
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-domain-udt-usage.html b/doc/src/sgml/html/infoschema-domain-udt-usage.html
index eed587e..25f5fe3 100644
--- a/doc/src/sgml/html/infoschema-domain-udt-usage.html
+++ b/doc/src/sgml/html/infoschema-domain-udt-usage.html
@@ -1,5 +1,5 @@
-37.22. domain_udt_usage
The view domain_udt_usage identifies all domains
that are based on data types owned by a currently enabled role.
Note that in PostgreSQL, built-in data
@@ -40,4 +40,4 @@
Name of the domain
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-domains.html b/doc/src/sgml/html/infoschema-domains.html
index 07354c6..3f98b3c 100644
--- a/doc/src/sgml/html/infoschema-domains.html
+++ b/doc/src/sgml/html/infoschema-domains.html
@@ -1,5 +1,5 @@
-37.23. domains
The view domains contains all
domains defined in the
current database. Only those domains are shown that the current user has
@@ -194,4 +194,4 @@
instances of such identifiers. (The specific format of the
identifier is not defined and not guaranteed to remain the same
in future versions.)
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-element-types.html b/doc/src/sgml/html/infoschema-element-types.html
index c8b17c3..184b847 100644
--- a/doc/src/sgml/html/infoschema-element-types.html
+++ b/doc/src/sgml/html/infoschema-element-types.html
@@ -1,5 +1,5 @@
-37.24. element_types
The view element_types contains the data type
descriptors of the elements of arrays. When a table column, composite-type attribute,
domain, function parameter, or function return value is defined to
@@ -191,4 +191,4 @@ ORDER BY c.ordinal_position;
An identifier of the data type descriptor of the element. This
is currently not useful.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-enabled-roles.html b/doc/src/sgml/html/infoschema-enabled-roles.html
index 1d13b01..29fbb98 100644
--- a/doc/src/sgml/html/infoschema-enabled-roles.html
+++ b/doc/src/sgml/html/infoschema-enabled-roles.html
@@ -1,5 +1,5 @@
-37.25. enabled_roles
The view enabled_roles identifies the currently
“enabled roles”. The enabled roles are recursively
defined as the current user together with all roles that have been
@@ -25,4 +25,4 @@
Name of a role
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-foreign-data-wrapper-options.html b/doc/src/sgml/html/infoschema-foreign-data-wrapper-options.html
index b1d0596..b1de409 100644
--- a/doc/src/sgml/html/infoschema-foreign-data-wrapper-options.html
+++ b/doc/src/sgml/html/infoschema-foreign-data-wrapper-options.html
@@ -1,5 +1,5 @@
-37.26. foreign_data_wrapper_options
The view foreign_data_wrapper_options contains
all the options defined for foreign-data wrappers in the current
database. Only those foreign-data wrappers are shown that the
@@ -30,4 +30,4 @@
Value of the option
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-foreign-data-wrappers.html b/doc/src/sgml/html/infoschema-foreign-data-wrappers.html
index 34473d8..e4b2cd8 100644
--- a/doc/src/sgml/html/infoschema-foreign-data-wrappers.html
+++ b/doc/src/sgml/html/infoschema-foreign-data-wrappers.html
@@ -1,5 +1,5 @@
-37.27. foreign_data_wrappers
The view foreign_data_wrappers contains all
foreign-data wrappers defined in the current database. Only those
foreign-data wrappers are shown that the current user has access to
@@ -35,4 +35,4 @@
Language used to implement this foreign-data wrapper
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-foreign-server-options.html b/doc/src/sgml/html/infoschema-foreign-server-options.html
index 4e56271..8d4a267 100644
--- a/doc/src/sgml/html/infoschema-foreign-server-options.html
+++ b/doc/src/sgml/html/infoschema-foreign-server-options.html
@@ -1,5 +1,5 @@
-37.28. foreign_server_options
The view foreign_server_options contains all the
options defined for foreign servers in the current database. Only
those foreign servers are shown that the current user has access to
@@ -29,4 +29,4 @@
Value of the option
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-foreign-servers.html b/doc/src/sgml/html/infoschema-foreign-servers.html
index dd26a06..bdbbb33 100644
--- a/doc/src/sgml/html/infoschema-foreign-servers.html
+++ b/doc/src/sgml/html/infoschema-foreign-servers.html
@@ -1,5 +1,5 @@
-37.29. foreign_servers
The view foreign_servers contains all foreign
servers defined in the current database. Only those foreign
servers are shown that the current user has access to (by way of
@@ -45,4 +45,4 @@
Name of the owner of the foreign server
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-foreign-table-options.html b/doc/src/sgml/html/infoschema-foreign-table-options.html
index 3a8e6b0..ea9427e 100644
--- a/doc/src/sgml/html/infoschema-foreign-table-options.html
+++ b/doc/src/sgml/html/infoschema-foreign-table-options.html
@@ -1,5 +1,5 @@
-37.30. foreign_table_options
The view foreign_table_options contains all the
options defined for foreign tables in the current database. Only
those foreign tables are shown that the current user has access to
@@ -34,4 +34,4 @@
Value of the option
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-foreign-tables.html b/doc/src/sgml/html/infoschema-foreign-tables.html
index 6126087..1d0c2dc 100644
--- a/doc/src/sgml/html/infoschema-foreign-tables.html
+++ b/doc/src/sgml/html/infoschema-foreign-tables.html
@@ -1,5 +1,5 @@
-37.31. foreign_tables
The view foreign_tables contains all foreign
tables defined in the current database. Only those foreign
tables are shown that the current user has access to (by way of
@@ -34,4 +34,4 @@
Name of the foreign server
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-information-schema-catalog-name.html b/doc/src/sgml/html/infoschema-information-schema-catalog-name.html
index e741318..fe08368 100644
--- a/doc/src/sgml/html/infoschema-information-schema-catalog-name.html
+++ b/doc/src/sgml/html/infoschema-information-schema-catalog-name.html
@@ -1,5 +1,5 @@
-37.3. information_schema_catalog_name
information_schema_catalog_name is a table that
always contains one row and one column containing the name of the
current database (current catalog, in SQL terminology).
@@ -13,4 +13,4 @@
Name of the database that contains this information schema
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-key-column-usage.html b/doc/src/sgml/html/infoschema-key-column-usage.html
index 485b6fc..7ef9315 100644
--- a/doc/src/sgml/html/infoschema-key-column-usage.html
+++ b/doc/src/sgml/html/infoschema-key-column-usage.html
@@ -1,5 +1,5 @@
-37.32. key_column_usage
The view key_column_usage identifies all columns
in the current database that are restricted by some unique, primary
key, or foreign key constraint. Check constraints are not included
@@ -62,4 +62,4 @@
For a foreign-key constraint, ordinal position of the referenced
column within its unique constraint (count starts at 1);
otherwise null
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-parameters.html b/doc/src/sgml/html/infoschema-parameters.html
index 1724aca..2a0d9dc 100644
--- a/doc/src/sgml/html/infoschema-parameters.html
+++ b/doc/src/sgml/html/infoschema-parameters.html
@@ -1,5 +1,5 @@
-37.33. parameters
The view parameters contains information about
the parameters (arguments) of all functions in the current database.
Only those functions are shown that the current user has access to
@@ -185,4 +185,4 @@
The default expression of the parameter, or null if none or if the
function is not owned by a currently enabled role.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-referential-constraints.html b/doc/src/sgml/html/infoschema-referential-constraints.html
index 1e0ad61..2c5122e 100644
--- a/doc/src/sgml/html/infoschema-referential-constraints.html
+++ b/doc/src/sgml/html/infoschema-referential-constraints.html
@@ -1,5 +1,5 @@
-37.34. referential_constraints
The view referential_constraints contains all
referential (foreign key) constraints in the current database.
Only those constraints are shown for which the current user has
@@ -67,4 +67,4 @@
CASCADE, SET NULL,
SET DEFAULT, RESTRICT, or
NO ACTION.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-role-column-grants.html b/doc/src/sgml/html/infoschema-role-column-grants.html
index fe86dbb..082a912 100644
--- a/doc/src/sgml/html/infoschema-role-column-grants.html
+++ b/doc/src/sgml/html/infoschema-role-column-grants.html
@@ -1,5 +1,5 @@
-37.35. role_column_grants
The view role_column_grants identifies all
privileges granted on columns where the grantor or grantee is a
currently enabled role. Further information can be found under
@@ -55,4 +55,4 @@
YES if the privilege is grantable, NO if not
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-role-routine-grants.html b/doc/src/sgml/html/infoschema-role-routine-grants.html
index be46900..95b01c7 100644
--- a/doc/src/sgml/html/infoschema-role-routine-grants.html
+++ b/doc/src/sgml/html/infoschema-role-routine-grants.html
@@ -1,5 +1,5 @@
-37.36. role_routine_grants
The view role_routine_grants identifies all
privileges granted on functions where the grantor or grantee is a
currently enabled role. Further information can be found under
@@ -63,4 +63,4 @@
YES if the privilege is grantable, NO if not
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-role-table-grants.html b/doc/src/sgml/html/infoschema-role-table-grants.html
index 3a5089b..11b50c5 100644
--- a/doc/src/sgml/html/infoschema-role-table-grants.html
+++ b/doc/src/sgml/html/infoschema-role-table-grants.html
@@ -1,5 +1,5 @@
-37.37. role_table_grants
The view role_table_grants identifies all
privileges granted on tables or views where the grantor or grantee
is a currently enabled role. Further information can be found
@@ -61,4 +61,4 @@
in the SELECT privilege, so this column
shows YES if the privilege
is SELECT, else NO.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-role-udt-grants.html b/doc/src/sgml/html/infoschema-role-udt-grants.html
index 46ab82e..180ab83 100644
--- a/doc/src/sgml/html/infoschema-role-udt-grants.html
+++ b/doc/src/sgml/html/infoschema-role-udt-grants.html
@@ -1,5 +1,5 @@
-37.38. role_udt_grants
The view role_udt_grants is intended to identify
USAGE privileges granted on user-defined types
where the grantor or grantee is a currently enabled role. Further
@@ -50,4 +50,4 @@
YES if the privilege is grantable, NO if not
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-role-usage-grants.html b/doc/src/sgml/html/infoschema-role-usage-grants.html
index 8af5c68..976bfeb 100644
--- a/doc/src/sgml/html/infoschema-role-usage-grants.html
+++ b/doc/src/sgml/html/infoschema-role-usage-grants.html
@@ -1,5 +1,5 @@
-37.39. role_usage_grants
The view role_usage_grants identifies
USAGE privileges granted on various kinds of
objects where the grantor or grantee is a currently enabled role.
@@ -54,4 +54,4 @@
YES if the privilege is grantable, NO if not
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-routine-column-usage.html b/doc/src/sgml/html/infoschema-routine-column-usage.html
index 795463b..cdb6c5d 100644
--- a/doc/src/sgml/html/infoschema-routine-column-usage.html
+++ b/doc/src/sgml/html/infoschema-routine-column-usage.html
@@ -1,5 +1,5 @@
-37.40. routine_column_usage
The view routine_column_usage identifies all columns
that are used by a function or procedure, either in the SQL body or in
parameter default expressions. (This only works for unquoted SQL bodies,
@@ -61,4 +61,4 @@
Name of the column that is used by the function
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-routine-privileges.html b/doc/src/sgml/html/infoschema-routine-privileges.html
index a325dda..61cd4ba 100644
--- a/doc/src/sgml/html/infoschema-routine-privileges.html
+++ b/doc/src/sgml/html/infoschema-routine-privileges.html
@@ -1,5 +1,5 @@
-37.41. routine_privileges
The view routine_privileges identifies all
privileges granted on functions to a currently enabled role or by a
currently enabled role. There is one row for each combination of function,
@@ -59,4 +59,4 @@
YES if the privilege is grantable, NO if not
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-routine-routine-usage.html b/doc/src/sgml/html/infoschema-routine-routine-usage.html
index 35e62a7..a27a3fe 100644
--- a/doc/src/sgml/html/infoschema-routine-routine-usage.html
+++ b/doc/src/sgml/html/infoschema-routine-routine-usage.html
@@ -1,5 +1,5 @@
-37.42. routine_routine_usage
The view routine_routine_usage identifies all functions
or procedures that are used by another (or the same) function or procedure,
either in the SQL body or in parameter default expressions. (This only
@@ -52,4 +52,4 @@
The “specific name” of the function that is used by the
first function.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-routine-sequence-usage.html b/doc/src/sgml/html/infoschema-routine-sequence-usage.html
index 1a6d952..d2297fb 100644
--- a/doc/src/sgml/html/infoschema-routine-sequence-usage.html
+++ b/doc/src/sgml/html/infoschema-routine-sequence-usage.html
@@ -1,5 +1,5 @@
-37.43. routine_sequence_usage
The view routine_sequence_usage identifies all sequences
that are used by a function or procedure, either in the SQL body or in
parameter default expressions. (This only works for unquoted SQL bodies,
@@ -56,4 +56,4 @@
Name of the sequence that is used by the function
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-routine-table-usage.html b/doc/src/sgml/html/infoschema-routine-table-usage.html
index 970360e..e150bf8 100644
--- a/doc/src/sgml/html/infoschema-routine-table-usage.html
+++ b/doc/src/sgml/html/infoschema-routine-table-usage.html
@@ -1,5 +1,5 @@
-37.44. routine_table_usage
The view routine_table_usage is meant to identify all
tables that are used by a function or procedure. This information is
currently not tracked by PostgreSQL.
@@ -54,4 +54,4 @@
Name of the table that is used by the function
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-routines.html b/doc/src/sgml/html/infoschema-routines.html
index fc2b3d2..5a18e97 100644
--- a/doc/src/sgml/html/infoschema-routines.html
+++ b/doc/src/sgml/html/infoschema-routines.html
@@ -1,5 +1,5 @@
-37.45. routines
The view routines contains all functions and procedures in the
current database. Only those functions and procedures are shown that the current
user has access to (by way of being the owner or having some
@@ -461,4 +461,4 @@
Applies to a feature not available in PostgreSQL
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-schema.html b/doc/src/sgml/html/infoschema-schema.html
index c572991..41edcdd 100644
--- a/doc/src/sgml/html/infoschema-schema.html
+++ b/doc/src/sgml/html/infoschema-schema.html
@@ -1,5 +1,5 @@
-37.1. The Schema
The information schema itself is a schema named
information_schema. This schema automatically
exists in all databases. The owner of this schema is the initial
@@ -13,4 +13,4 @@
schema are generic names that might occur in user applications, you
should be careful if you want to put the information schema in the
path.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-schemata.html b/doc/src/sgml/html/infoschema-schemata.html
index 2858d63..5857df9 100644
--- a/doc/src/sgml/html/infoschema-schemata.html
+++ b/doc/src/sgml/html/infoschema-schemata.html
@@ -1,5 +1,5 @@
-37.46. schemata
The view schemata contains all schemas in the current
database that the current user has access to (by way of being the owner or
having some privilege).
@@ -43,4 +43,4 @@
Applies to a feature not available in PostgreSQL
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-sequences.html b/doc/src/sgml/html/infoschema-sequences.html
index 9b69690..d0bb295 100644
--- a/doc/src/sgml/html/infoschema-sequences.html
+++ b/doc/src/sgml/html/infoschema-sequences.html
@@ -1,5 +1,5 @@
-37.47. sequences
The view sequences contains all sequences
defined in the current database. Only those sequences are shown
that the current user has access to (by way of being the owner or
@@ -84,4 +84,4 @@
Note that in accordance with the SQL standard, the start, minimum,
maximum, and increment values are returned as character strings.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-sql-features.html b/doc/src/sgml/html/infoschema-sql-features.html
index a4d94dd..b57e383 100644
--- a/doc/src/sgml/html/infoschema-sql-features.html
+++ b/doc/src/sgml/html/infoschema-sql-features.html
@@ -1,5 +1,5 @@
-37.48. sql_features
The table sql_features contains information
about which formal features defined in the SQL standard are
supported by PostgreSQL. This is the
@@ -47,4 +47,4 @@
Possibly a comment about the supported status of the feature
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-sql-implementation-info.html b/doc/src/sgml/html/infoschema-sql-implementation-info.html
index 623dc4a..434dc21 100644
--- a/doc/src/sgml/html/infoschema-sql-implementation-info.html
+++ b/doc/src/sgml/html/infoschema-sql-implementation-info.html
@@ -1,5 +1,5 @@
-37.49. sql_implementation_info
The table sql_implementation_info contains
information about various aspects that are left
implementation-defined by the SQL standard. This information is
@@ -42,4 +42,4 @@
Possibly a comment pertaining to the implementation information item
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-sql-parts.html b/doc/src/sgml/html/infoschema-sql-parts.html
index b648e55..f512d20 100644
--- a/doc/src/sgml/html/infoschema-sql-parts.html
+++ b/doc/src/sgml/html/infoschema-sql-parts.html
@@ -1,5 +1,5 @@
-37.50. sql_parts
The table sql_parts contains information about
which of the several parts of the SQL standard are supported by
PostgreSQL.
@@ -36,4 +36,4 @@
Possibly a comment about the supported status of the part
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-sql-sizing.html b/doc/src/sgml/html/infoschema-sql-sizing.html
index f862662..956abce 100644
--- a/doc/src/sgml/html/infoschema-sql-sizing.html
+++ b/doc/src/sgml/html/infoschema-sql-sizing.html
@@ -1,5 +1,5 @@
-37.51. sql_sizing
The table sql_sizing contains information about
various size limits and maximum values in
PostgreSQL. This information is
@@ -35,4 +35,4 @@
Possibly a comment pertaining to the sizing item
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-table-constraints.html b/doc/src/sgml/html/infoschema-table-constraints.html
index dfb87c1..192ac5c 100644
--- a/doc/src/sgml/html/infoschema-table-constraints.html
+++ b/doc/src/sgml/html/infoschema-table-constraints.html
@@ -1,5 +1,5 @@
-37.52. table_constraints
The view table_constraints contains all
constraints belonging to tables that the current user owns or has
some privilege other than SELECT on.
@@ -70,4 +70,4 @@
if the constraint treats nulls as distinct or NO if
it treats nulls as not distinct, otherwise null for other types of
constraints.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-table-privileges.html b/doc/src/sgml/html/infoschema-table-privileges.html
index c1869b0..e0b9cff 100644
--- a/doc/src/sgml/html/infoschema-table-privileges.html
+++ b/doc/src/sgml/html/infoschema-table-privileges.html
@@ -1,5 +1,5 @@
-37.53. table_privileges
The view table_privileges identifies all
privileges granted on tables or views to a currently enabled role
or by a currently enabled role. There is one row for each
@@ -57,4 +57,4 @@
in the SELECT privilege, so this column
shows YES if the privilege
is SELECT, else NO.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-tables.html b/doc/src/sgml/html/infoschema-tables.html
index 088970c..bb50e35 100644
--- a/doc/src/sgml/html/infoschema-tables.html
+++ b/doc/src/sgml/html/infoschema-tables.html
@@ -1,5 +1,5 @@
-37.54. tables
The view tables contains all tables and views
defined in the current database. Only those tables and views are
shown that the current user has access to (by way of being the
@@ -79,4 +79,4 @@
Not yet implemented
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-transforms.html b/doc/src/sgml/html/infoschema-transforms.html
index ed0d401..63ffa88 100644
--- a/doc/src/sgml/html/infoschema-transforms.html
+++ b/doc/src/sgml/html/infoschema-transforms.html
@@ -1,5 +1,5 @@
-37.55. transforms
The view transforms contains information about the
transforms defined in the current database. More precisely, it contains a
row for each function contained in a transform (the “from SQL”
@@ -52,4 +52,4 @@
FROM SQL or TO SQL
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-triggered-update-columns.html b/doc/src/sgml/html/infoschema-triggered-update-columns.html
index 178aea9..945d64b 100644
--- a/doc/src/sgml/html/infoschema-triggered-update-columns.html
+++ b/doc/src/sgml/html/infoschema-triggered-update-columns.html
@@ -1,5 +1,5 @@
-37.56. triggered_update_columns
For triggers in the current database that specify a column list
(like UPDATE OF column1, column2), the
view triggered_update_columns identifies these
@@ -48,4 +48,4 @@
Name of the column that the trigger is defined on
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-triggers.html b/doc/src/sgml/html/infoschema-triggers.html
index 148fedd..397d518 100644
--- a/doc/src/sgml/html/infoschema-triggers.html
+++ b/doc/src/sgml/html/infoschema-triggers.html
@@ -1,5 +1,5 @@
-37.57. triggers
The view triggers contains all triggers defined
in the current database on tables and views that the current user owns
or has some privilege other than SELECT on.
@@ -147,4 +147,4 @@
respectively.
That was how they were named in the SQL:1999 standard.
The new naming conforms to SQL:2003 and later.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-udt-privileges.html b/doc/src/sgml/html/infoschema-udt-privileges.html
index 3df1745..ed5fd63 100644
--- a/doc/src/sgml/html/infoschema-udt-privileges.html
+++ b/doc/src/sgml/html/infoschema-udt-privileges.html
@@ -1,5 +1,5 @@
-37.58. udt_privileges
The view udt_privileges identifies
USAGE privileges granted on user-defined types to a
currently enabled role or by a currently enabled role. There is one row for
@@ -47,4 +47,4 @@
YES if the privilege is grantable, NO if not
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-usage-privileges.html b/doc/src/sgml/html/infoschema-usage-privileges.html
index cf0c9cf..eca3b01 100644
--- a/doc/src/sgml/html/infoschema-usage-privileges.html
+++ b/doc/src/sgml/html/infoschema-usage-privileges.html
@@ -1,5 +1,5 @@
-37.59. usage_privileges
The view usage_privileges identifies
USAGE privileges granted on various kinds of
objects to a currently enabled role or by a currently enabled role.
@@ -63,4 +63,4 @@
YES if the privilege is grantable, NO if not
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-user-defined-types.html b/doc/src/sgml/html/infoschema-user-defined-types.html
index 2b6ea5e..0014772 100644
--- a/doc/src/sgml/html/infoschema-user-defined-types.html
+++ b/doc/src/sgml/html/infoschema-user-defined-types.html
@@ -1,5 +1,5 @@
-37.60. user_defined_types
The view user_defined_types currently contains
all composite types defined in the current database.
Only those types are shown that the current user has access to (by way
@@ -165,4 +165,4 @@
Applies to a feature not available in PostgreSQL
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-user-mapping-options.html b/doc/src/sgml/html/infoschema-user-mapping-options.html
index 09f02df..a161234 100644
--- a/doc/src/sgml/html/infoschema-user-mapping-options.html
+++ b/doc/src/sgml/html/infoschema-user-mapping-options.html
@@ -1,5 +1,5 @@
-37.61. user_mapping_options
The view user_mapping_options contains all the
options defined for user mappings in the current database. Only
those user mappings are shown where the current user has access to
@@ -42,4 +42,4 @@
server owner, or the current user is a superuser. The intent is
to protect password information stored as user mapping
option.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-user-mappings.html b/doc/src/sgml/html/infoschema-user-mappings.html
index 7b8698e..11bd2bf 100644
--- a/doc/src/sgml/html/infoschema-user-mappings.html
+++ b/doc/src/sgml/html/infoschema-user-mappings.html
@@ -1,5 +1,5 @@
-37.62. user_mappings
The view user_mappings contains all user
mappings defined in the current database. Only those user mappings
are shown where the current user has access to the corresponding
@@ -27,4 +27,4 @@
Name of the foreign server used by this mapping
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-view-column-usage.html b/doc/src/sgml/html/infoschema-view-column-usage.html
index 7467765..b8127f3 100644
--- a/doc/src/sgml/html/infoschema-view-column-usage.html
+++ b/doc/src/sgml/html/infoschema-view-column-usage.html
@@ -1,5 +1,5 @@
-37.63. view_column_usage
The view view_column_usage identifies all
columns that are used in the query expression of a view (the
SELECT statement that defines the view). A
@@ -51,4 +51,4 @@
Name of the column that is used by the view
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-view-routine-usage.html b/doc/src/sgml/html/infoschema-view-routine-usage.html
index 5e52ae3..9f94776 100644
--- a/doc/src/sgml/html/infoschema-view-routine-usage.html
+++ b/doc/src/sgml/html/infoschema-view-routine-usage.html
@@ -1,5 +1,5 @@
-37.64. view_routine_usage
The view view_routine_usage identifies all
routines (functions and procedures) that are used in the query
expression of a view (the SELECT statement that
@@ -40,4 +40,4 @@
The “specific name” of the function. See Section 37.45 for more information.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-view-table-usage.html b/doc/src/sgml/html/infoschema-view-table-usage.html
index a2bcb89..3d453b4 100644
--- a/doc/src/sgml/html/infoschema-view-table-usage.html
+++ b/doc/src/sgml/html/infoschema-view-table-usage.html
@@ -1,5 +1,5 @@
-37.65. view_table_usage
The view view_table_usage identifies all tables
that are used in the query expression of a view (the
SELECT statement that defines the view). A
@@ -44,4 +44,4 @@
Name of the table that is used by the view
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/infoschema-views.html b/doc/src/sgml/html/infoschema-views.html
index 6052a95..9ca8e5e 100644
--- a/doc/src/sgml/html/infoschema-views.html
+++ b/doc/src/sgml/html/infoschema-views.html
@@ -1,5 +1,5 @@
-37.66. views
The view views contains all views defined in the
current database. Only those views are shown that the current user
has access to (by way of being the owner or having some privilege).
@@ -67,4 +67,4 @@
YES if the view has an INSTEAD OFINSERT trigger defined on it, NO if not
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/install-binaries.html b/doc/src/sgml/html/install-binaries.html
index 50c3500..b98ec81 100644
--- a/doc/src/sgml/html/install-binaries.html
+++ b/doc/src/sgml/html/install-binaries.html
@@ -1,5 +1,5 @@
-Chapter 16. Installation from Binaries
PostgreSQL is available in the form of binary
packages for most common operating systems today. When available, this is
the recommended way to install PostgreSQL for users of the system. Building
@@ -10,4 +10,4 @@
the download section on the PostgreSQL website at
https://www.postgresql.org/download/ and follow the
instructions for the specific platform.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/install-getsource.html b/doc/src/sgml/html/install-getsource.html
index bcacaad..ece82cc 100644
--- a/doc/src/sgml/html/install-getsource.html
+++ b/doc/src/sgml/html/install-getsource.html
@@ -1,5 +1,5 @@
-17.3. Getting the Source
The PostgreSQL source code for released versions
can be obtained from the download section of our website:
https://www.postgresql.org/ftp/source/.
@@ -17,4 +17,4 @@
Alternatively, you can use the Git version control system; see
Section I.1 for more information.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/install-post.html b/doc/src/sgml/html/install-post.html
index 3f7f0df..8cf21d6 100644
--- a/doc/src/sgml/html/install-post.html
+++ b/doc/src/sgml/html/install-post.html
@@ -1,5 +1,5 @@
-17.5. Post-Installation Setup
On some systems with shared libraries
you need to tell the system how to find the newly installed
shared libraries. The systems on which this is
@@ -100,4 +100,4 @@ export MANPATH
user that plans to use the database sets PGHOST. This
is not required, however; the settings can be communicated via command
line options to most client programs.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/install-procedure.html b/doc/src/sgml/html/install-procedure.html
index c6ca127..96c598e 100644
--- a/doc/src/sgml/html/install-procedure.html
+++ b/doc/src/sgml/html/install-procedure.html
@@ -1,5 +1,5 @@
-17.4. Installation Procedure
The first step of the installation procedure is to configure the
source tree for your system and choose the options you would like.
This is done by running the configure script. For a
@@ -815,4 +815,4 @@ build-postgresql:
makefiles. Which to use is a matter of preference, but a common habit
among developers is to use PROFILE for one-time flag
adjustments, while COPT might be kept set all the time.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/install-requirements.html b/doc/src/sgml/html/install-requirements.html
index 0ccce68..0510e44 100644
--- a/doc/src/sgml/html/install-requirements.html
+++ b/doc/src/sgml/html/install-requirements.html
@@ -1,5 +1,5 @@
-17.2. Requirements
In general, a modern Unix-compatible platform should be able to run
PostgreSQL.
The platforms that had received specific testing at the
@@ -194,4 +194,4 @@
run the regression tests you will temporarily need up to an extra
300 MB. Use the df command to check free disk
space.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/doc/src/sgml/html/install-short.html b/doc/src/sgml/html/install-short.html
index c52018a..92b6b4a 100644
--- a/doc/src/sgml/html/install-short.html
+++ b/doc/src/sgml/html/install-short.html
@@ -1,5 +1,5 @@
-17.1. Short Version
\ No newline at end of file
diff --git a/doc/src/sgml/html/install-windows-full.html b/doc/src/sgml/html/install-windows-full.html
index 70010d3..6f4f4e3 100644
--- a/doc/src/sgml/html/install-windows-full.html
+++ b/doc/src/sgml/html/install-windows-full.html
@@ -1,6 +1,6 @@
18.1. Building with Visual C++ or the Microsoft Windows SDK
18.1. Building with Visual C++ or the
- Microsoft Windows SDK
PostgreSQL can be built using the Visual C++ compiler suite from Microsoft.
These compilers can be either from Visual Studio,
@@ -338,4 +338,4 @@ $ENV{PROVE_TESTS}='t/020*.pl t/010*.pl'
zstd, which will search for a command by that
name in the configured PATH.