\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/admin.html postgresql-10-10.19/doc/src/sgml/html/admin.html
--- postgresql-10-10.17/doc/src/sgml/html/admin.html 2021-05-10 20:58:12.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/admin.html 2021-11-08 22:24:55.000000000 +0000
@@ -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
server, management of users and databases, and maintenance tasks.
@@ -20,4 +20,4 @@
the PostgreSQL database system. Readers are
encouraged to look at Part I and Part II for additional information.
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
of server log files.
@@ -50,4 +50,4 @@
by pg_stat_file()
pg_catalog.pg_logfile_rotate()
integer
Alternate name for pg_rotate_logfile(), but note that it
returns integer 0 or 1 rather than boolean
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/amcheck.html postgresql-10-10.19/doc/src/sgml/html/amcheck.html
--- postgresql-10-10.17/doc/src/sgml/html/amcheck.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/amcheck.html 2021-11-08 22:25:11.000000000 +0000
@@ -1,5 +1,5 @@
-F.2. amcheck
The amcheck module provides functions that allow you to
verify the logical consistency of the structure of indexes. If the
structure appears to be valid, no error is raised.
The functions verify various invariants in the
@@ -165,4 +165,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/app-clusterdb.html postgresql-10-10.19/doc/src/sgml/html/app-clusterdb.html
--- postgresql-10-10.17/doc/src/sgml/html/app-clusterdb.html 2021-05-10 20:58:21.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/app-clusterdb.html 2021-11-08 22:25:04.000000000 +0000
@@ -1,5 +1,5 @@
-clusterdb
createdb creates a new PostgreSQL
database.
@@ -100,4 +100,4 @@
template0 template database, here is the
command-line command and the underlying SQL command:
createuser creates a
new PostgreSQL user (or more precisely, a role).
Only superusers and users with CREATEROLE privilege can create
new users, so createuser must be
@@ -128,4 +128,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.
-
dropdb destroys an existing
PostgreSQL database.
The user who executes this command must be a database
superuser or the owner of the database.
@@ -74,4 +74,4 @@
$ dropdb -p 5000 -h eden -i -e demoDatabase "demo" will be permanently deleted.
Are you sure? (y/n) y
-DROP DATABASE demo;
dropuser removes an existing
PostgreSQL user.
Only superusers and users with the CREATEROLE privilege can
remove PostgreSQL users. (To remove a
@@ -71,4 +71,4 @@
$ dropuser -p 5000 -h eden -i -e joeRole "joe" will be permanently removed.
Are you sure? (y/n) y
-DROP ROLE joe;
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
function calls. The output files can then be processed with any C
@@ -77,4 +77,4 @@
program using the following sequence of commands:
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/appendix-obsolete.html postgresql-10-10.19/doc/src/sgml/html/appendix-obsolete.html
--- postgresql-10-10.17/doc/src/sgml/html/appendix-obsolete.html 2021-05-10 20:58:29.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/appendix-obsolete.html 2021-11-08 22:25:12.000000000 +0000
@@ -1,7 +1,7 @@
-Appendix L. 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 -Nru postgresql-10-10.17/doc/src/sgml/html/app-initdb.html postgresql-10-10.19/doc/src/sgml/html/app-initdb.html
--- postgresql-10-10.17/doc/src/sgml/html/app-initdb.html 2021-05-10 20:58:22.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/app-initdb.html 2021-11-08 22:25:05.000000000 +0000
@@ -1,5 +1,5 @@
-initdb
initdb creates a new
PostgreSQL database cluster. A database
cluster is a collection of databases that are managed by a single
@@ -145,4 +145,4 @@
(see Section 33.14).
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/applevel-consistency.html postgresql-10-10.19/doc/src/sgml/html/applevel-consistency.html
--- postgresql-10-10.17/doc/src/sgml/html/applevel-consistency.html 2021-05-10 20:58:09.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/applevel-consistency.html 2021-11-08 22:24:52.000000000 +0000
@@ -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
restrict itself to the statement's snapshot if a write conflict occurs.
@@ -100,4 +100,4 @@
UPDATE, or DELETE), 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 -Nru postgresql-10-10.17/doc/src/sgml/html/app-pgbasebackup.html postgresql-10-10.19/doc/src/sgml/html/app-pgbasebackup.html
--- postgresql-10-10.17/doc/src/sgml/html/app-pgbasebackup.html 2021-05-10 20:58:21.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/app-pgbasebackup.html 2021-11-08 22:25:04.000000000 +0000
@@ -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 base backups of
a running PostgreSQL database cluster. These
are taken without affecting other clients to the database, and can be used
@@ -304,4 +304,4 @@
/opt/ts is relocated
to ./backup/ts:
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
to PostgreSQL to facilitate finding the required header files
@@ -77,4 +77,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/app-pgcontroldata.html postgresql-10-10.19/doc/src/sgml/html/app-pgcontroldata.html
--- postgresql-10-10.17/doc/src/sgml/html/app-pgcontroldata.html 2021-05-10 20:58:22.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/app-pgcontroldata.html 2021-11-08 22:25:05.000000000 +0000
@@ -1,5 +1,5 @@
-pg_controldata
pg_controldata — display control information of a PostgreSQL database cluster
Synopsis
pg_controldata [option] [[-D] datadir]
Description
pg_controldata prints information initialized during
initdb, such as the catalog version.
It also shows information about write-ahead logging and checkpoint
processing. This information is cluster-wide, and not specific to any one
@@ -13,4 +13,4 @@
supports options -? and --help, which output the
supported arguments.
Environment
PGDATA
Default data directory location
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/app-pg-ctl.html postgresql-10-10.19/doc/src/sgml/html/app-pg-ctl.html
--- postgresql-10-10.17/doc/src/sgml/html/app-pg-ctl.html 2021-05-10 20:58:22.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/app-pg-ctl.html 2021-11-08 22:25:05.000000000 +0000
@@ -1,5 +1,5 @@
-pg_ctl
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
SQL commands that can be used as input to psql to restore the databases. It does this by
@@ -223,4 +223,4 @@
databases.)
See Also
Check pg_dump for details on possible
error conditions.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/app-pgdump.html postgresql-10-10.19/doc/src/sgml/html/app-pgdump.html
--- postgresql-10-10.17/doc/src/sgml/html/app-pgdump.html 2021-05-10 20:58:21.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/app-pgdump.html 2021-11-08 22:25:04.000000000 +0000
@@ -1,5 +1,5 @@
-pg_dump
pg_dump is a utility for backing up a
PostgreSQL database. It makes consistent
@@ -587,4 +587,4 @@
Thus, to dump a single table with a mixed-case name, you need something
like
-
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.
Options
-d dbname --dbname=dbname
Specifies the name of the database to connect to. The
@@ -50,4 +50,4 @@
someremotehost:5432 - no response$echo $?2
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/app-pgreceivewal.html postgresql-10-10.19/doc/src/sgml/html/app-pgreceivewal.html
--- postgresql-10-10.17/doc/src/sgml/html/app-pgreceivewal.html 2021-05-10 20:58:21.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/app-pgreceivewal.html 2021-11-08 22:25:04.000000000 +0000
@@ -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
@@ -34,6 +34,16 @@
must permit the replication connection. The server must also be
configured with max_wal_senders set high enough to
leave at least one session available for the stream.
+
The starting point of the write-ahead log streaming is calculated when
+ pg_receivewal starts:
+
First, scan the directory where the WAL segment files are written and
+ find the newest completed segment file, using as starting point the
+ beginning of the next WAL segment file. This is calculated independently
+ on the compression method used to compress each segment.
+
If a starting point cannot be calculated with the previous method,
+ the latest WAL flush location is used as reported by the server from
+ a IDENTIFY_SYSTEM command.
+
If the connection is lost, or if it cannot be initially established,
with a non-fatal error, pg_receivewal will
retry the connection indefinitely, and reestablish streaming as soon
@@ -139,4 +149,4 @@
Examples
To stream the write-ahead log from the server at
mydbserver and store it in the local directory
/usr/local/pgsql/archive:
-
pg_recvlogical — control PostgreSQL logical decoding streams
Synopsis
pg_recvlogical [option...]
Description
pg_recvlogical controls logical decoding replication
slots and streams data from such replication slots.
It creates a replication-mode connection, so it is subject to the same
constraints as pg_receivewal, plus those for logical
@@ -120,4 +120,4 @@
uses the environment variables supported by libpq
(see Section 33.14).
pg_resetwal — reset the write-ahead log and other control information of a PostgreSQL database cluster
Synopsis
pg_resetwal [-f] [-n] [option...] {[-D] datadir}
Description
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
if these files have become corrupted. It should be used only as a
@@ -94,6 +94,14 @@
data directory, adding one, and then multiplying by 52352 (0xCC80).
The file names are in hexadecimal. There is no simple recipe such as
the ones for other options of appending zeroes.
+
-u xid
Manually set the oldest unfrozen transaction ID.
+
A safe value can be determined by looking for the numerically smallest
+ file name in the directory pg_xact under the data directory
+ and then multiplying by 1048576 (0x100000). Note that the file names are in
+ hexadecimal. It is usually easiest to specify the option value in
+ hexadecimal too. For example, if 0007 is the smallest entry
+ in pg_xact, -u 0x700000 will work (five
+ trailing zeroes provide the proper multiplier).
-xxid
Manually set the next transaction ID.
A safe value can be determined by looking for the numerically largest
file name in the directory pg_xact under the data directory,
@@ -112,4 +120,4 @@
so, make doubly certain that there is no server process still alive.
pg_resetwal works only with servers of the same
major version.
-
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 master server back online
after failover as a standby that follows the new master.
@@ -99,4 +99,4 @@
doesn't apply the WAL, it just creates a backup label file that
makes PostgreSQL start by replaying all WAL from
that checkpoint forward.)
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/app-postgres.html postgresql-10-10.19/doc/src/sgml/html/app-postgres.html
--- postgresql-10-10.17/doc/src/sgml/html/app-postgres.html 2021-05-10 20:58:22.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/app-postgres.html 2021-11-08 22:25:05.000000000 +0000
@@ -1,5 +1,5 @@
-postgres
postgres is the
PostgreSQL database server. In order
for a client application to access a database it connects (over a
network or locally) to a running postgres instance.
@@ -351,4 +351,4 @@
to set a parameter.
psql is a terminal-based front-end to
PostgreSQL. It enables you to type in
@@ -282,7 +282,7 @@
psql is currently connected, followed by
the string =>. For example:
$ psql testdb
-psql (10.17)
+psql (10.19)
Type "help" for help.
testdb=>
vacuumdb — garbage-collect and analyze a PostgreSQL database
Synopsis
vacuumdb [connection-option...] [option...] [ -t | --tabletable
[( column [,...] )]
]
@@ -120,4 +120,4 @@
foo in a database named
xyzzy, and analyze a single column
bar of the table for the optimizer:
-
The local shell command to execute to retrieve an archived segment of
the WAL file series. This parameter is required for archive recovery,
@@ -70,4 +70,4 @@
anyway. An exception is that if the command was terminated by a
signal or an error by the shell (such as command not found), the
database will not proceed with startup.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/arrays.html postgresql-10-10.19/doc/src/sgml/html/arrays.html
--- postgresql-10-10.17/doc/src/sgml/html/arrays.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/arrays.html 2021-11-08 22:24:49.000000000 +0000
@@ -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, or composite type
can be created.
@@ -530,4 +530,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/auth-delay.html postgresql-10-10.19/doc/src/sgml/html/auth-delay.html
--- postgresql-10-10.17/doc/src/sgml/html/auth-delay.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/auth-delay.html 2021-11-08 22:25:11.000000000 +0000
@@ -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
denial-of-service attacks, and may even exacerbate them, since processes
@@ -17,4 +17,4 @@
shared_preload_libraries = 'auth_delay'
auth_delay.milliseconds = '500'
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/auth-methods.html postgresql-10-10.19/doc/src/sgml/html/auth-methods.html
--- postgresql-10-10.17/doc/src/sgml/html/auth-methods.html 2021-05-10 20:58:11.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/auth-methods.html 2021-11-08 22:24:53.000000000 +0000
@@ -1,5 +1,5 @@
-20.3. Authentication Methods
The following subsections describe the authentication methods in more detail.
20.3.1. Trust Authentication
When trust authentication is specified,
PostgreSQL assumes that anyone who can
connect to the server is authorized to access the database with
@@ -514,4 +514,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 -Nru postgresql-10-10.17/doc/src/sgml/html/auth-pg-hba-conf.html postgresql-10-10.19/doc/src/sgml/html/auth-pg-hba-conf.html
--- postgresql-10-10.17/doc/src/sgml/html/auth-pg-hba-conf.html 2021-05-10 20:58:11.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/auth-pg-hba-conf.html 2021-11-08 22:24:53.000000000 +0000
@@ -1,5 +1,5 @@
-20.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
cluster's data directory.
@@ -381,4 +381,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
+local db1,db2,@demodbs all md5
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/auth-username-maps.html postgresql-10-10.19/doc/src/sgml/html/auth-username-maps.html
--- postgresql-10-10.17/doc/src/sgml/html/auth-username-maps.html 2021-05-10 20:58:11.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/auth-username-maps.html 2021-11-08 22:24:53.000000000 +0000
@@ -1,5 +1,5 @@
-20.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.
In this case, a user name map can be applied to map the operating system
@@ -78,4 +78,4 @@
# bob has user name robert on these machines
omicron robert bob
# bryanh can also connect as guest1
-omicron bryanh guest1
\ No newline at end of file
+omicron bryanh guest1
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/auto-explain.html postgresql-10-10.19/doc/src/sgml/html/auto-explain.html
--- postgresql-10-10.17/doc/src/sgml/html/auto-explain.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/auto-explain.html 2021-11-08 22:25:11.000000000 +0000
@@ -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
by hand. This is especially helpful for tracking down un-optimized queries
@@ -120,4 +120,4 @@
Buckets: 1024 Batches: 1 Memory Usage: 4kB
-> Seq Scan on pg_index (cost=0.00..3.02 rows=92 width=4) (actual time=0.008..3.187 rows=92 loops=1)
Filter: indisunique
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/backup-dump.html postgresql-10-10.19/doc/src/sgml/html/backup-dump.html
--- postgresql-10-10.17/doc/src/sgml/html/backup-dump.html 2021-05-10 20:58:11.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/backup-dump.html 2021-11-08 22:24:54.000000000 +0000
@@ -1,5 +1,5 @@
-25.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.
PostgreSQL provides the utility program
@@ -151,13 +151,20 @@
Use split. The split command
allows you to split the output into smaller files that are
acceptable in size to the underlying file system. For example, to
- make chunks of 1 megabyte:
+ make 2 gigabyte chunks:
-
pg_dump dbname | split -b 1m - filename
+
pg_dump dbname | split -b 2G - filename
Reload with:
cat filename* | psql dbname
+
+ If using GNU split, it is possible to
+ use it and gzip together:
+
+
Use pg_dump's custom dump format. If PostgreSQL was built on a system with the
zlib compression library installed, the custom dump
format will compress data as it writes it to the output file. This will
@@ -186,4 +193,4 @@
You can use 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 -Nru postgresql-10-10.17/doc/src/sgml/html/backup-file.html postgresql-10-10.19/doc/src/sgml/html/backup-file.html
--- postgresql-10-10.17/doc/src/sgml/html/backup-file.html 2021-05-10 20:58:11.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/backup-file.html 2021-11-08 22:24:54.000000000 +0000
@@ -1,5 +1,5 @@
-25.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 18.2 explains where these files
are located. You can use whatever method you prefer
@@ -77,4 +77,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/backup.html postgresql-10-10.19/doc/src/sgml/html/backup.html
--- postgresql-10-10.17/doc/src/sgml/html/backup.html 2021-05-10 20:58:11.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/backup.html 2021-11-08 22:24:54.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 25. 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
the underlying techniques and assumptions.
@@ -8,4 +8,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 -Nru postgresql-10-10.17/doc/src/sgml/html/bgworker.html postgresql-10-10.19/doc/src/sgml/html/bgworker.html
--- postgresql-10-10.17/doc/src/sgml/html/bgworker.html 2021-05-10 20:58:16.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/bgworker.html 2021-11-08 22:24:59.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 47. 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.
These processes have the option to attach to PostgreSQL's
@@ -71,8 +71,8 @@
when the processes are to be started; they do not stop when a different state
is reached.
bgw_restart_time is the interval, in seconds, that
- postgres should wait before restarting the process, in
- case it crashes. It can be any positive value,
+ postgres should wait before restarting the process in
+ the event that it crashes. It can be any positive value,
or BGW_NEVER_RESTART, indicating not to restart the
process in case of a crash.
bgw_library_name is the name of a library in
@@ -187,4 +187,4 @@
which demonstrates some useful techniques.
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 -Nru postgresql-10-10.17/doc/src/sgml/html/biblio.html postgresql-10-10.19/doc/src/sgml/html/biblio.html
--- postgresql-10-10.17/doc/src/sgml/html/biblio.html 2021-05-10 20:58:29.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/biblio.html 2021-11-08 22:25:12.000000000 +0000
@@ -1,5 +1,5 @@
-Bibliography
Selected references and readings for SQL
and PostgreSQL.
Some white papers and technical reports from the original
POSTGRES development team
@@ -17,4 +17,4 @@
system”. M.Stonebraker, M.Hearst, and S.Potamianos. SIGMOD Record 18(3). Sept. 1989.
[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 -Nru postgresql-10-10.17/doc/src/sgml/html/bki-commands.html postgresql-10-10.19/doc/src/sgml/html/bki-commands.html
--- postgresql-10-10.17/doc/src/sgml/html/bki-commands.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/bki-commands.html 2021-11-08 22:25:08.000000000 +0000
@@ -1,5 +1,5 @@
-67.2. BKI Commands
The following sequence of commands will create the
table test_table with OID 420, having two columns
cola and colb of type
int4 and text, respectively, and insert
@@ -9,4 +9,4 @@
insert OID=421 ( 1 "value1" )
insert OID=422 ( 2 _null_ )
close test_table
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/bki-format.html postgresql-10-10.19/doc/src/sgml/html/bki-format.html
--- postgresql-10-10.17/doc/src/sgml/html/bki-format.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/bki-format.html 2021-11-08 22:25:08.000000000 +0000
@@ -1,5 +1,5 @@
-67.1. BKI File Format
This section describes how the PostgreSQL
backend interprets BKI files. This description
will be easier to understand if the postgres.bki
file is at hand as an example.
@@ -13,4 +13,4 @@
characters (parentheses, commas, etc.), numbers, or double-quoted
strings. Everything is case sensitive.
Lines starting with # are ignored.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/bki.html postgresql-10-10.19/doc/src/sgml/html/bki.html
--- postgresql-10-10.17/doc/src/sgml/html/bki.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/bki.html 2021-11-08 22:25:08.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 67. BKI Backend Interface
Backend Interface (BKI) files are scripts in a
special language that is understood by the
PostgreSQL backend when running in the
“bootstrap” mode. The bootstrap mode allows system catalogs
@@ -20,4 +20,4 @@
share subdirectory of the installation tree.
Related information can be found in the documentation for
initdb.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/bki-structure.html postgresql-10-10.19/doc/src/sgml/html/bki-structure.html
--- postgresql-10-10.17/doc/src/sgml/html/bki-structure.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/bki-structure.html 2021-11-08 22:25:08.000000000 +0000
@@ -1,5 +1,5 @@
-67.3. 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,
pg_attribute, pg_proc, and
@@ -24,4 +24,4 @@
build indices
There are doubtless other, undocumented ordering dependencies.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/bloom.html postgresql-10-10.19/doc/src/sgml/html/bloom.html
--- postgresql-10-10.17/doc/src/sgml/html/bloom.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/bloom.html 2021-11-08 22:25:11.000000000 +0000
@@ -1,5 +1,5 @@
-F.5. bloom
bloom provides an index access method based on
Bloom filters.
A Bloom filter is a space-efficient data structure that is used to test
whether an element is a member of a set. In the case of an index access
@@ -151,4 +151,4 @@
Postgres Professional, Moscow, Russia
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/bookindex.html postgresql-10-10.19/doc/src/sgml/html/bookindex.html
--- postgresql-10-10.17/doc/src/sgml/html/bookindex.html 2021-05-10 20:58:30.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/bookindex.html 2021-11-08 22:25:13.000000000 +0000
@@ -1,5 +1,5 @@
-Index
The core PostgreSQL distribution
includes the BRIN operator classes shown in
Table 65.1.
The minmax
@@ -179,4 +179,4 @@
=>=>
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/brin-extensibility.html postgresql-10-10.19/doc/src/sgml/html/brin-extensibility.html
--- postgresql-10-10.17/doc/src/sgml/html/brin-extensibility.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/brin-extensibility.html 2021-11-08 22:25:08.000000000 +0000
@@ -1,5 +1,5 @@
-65.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
itself takes care of concurrency, logging and searching the index structure.
@@ -100,4 +100,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/brin.html postgresql-10-10.19/doc/src/sgml/html/brin.html
--- postgresql-10-10.17/doc/src/sgml/html/brin.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/brin.html 2021-11-08 22:25:08.000000000 +0000
@@ -1,2 +1,2 @@
-Chapter 65. BRIN Indexes
BRIN stands for Block Range Index.
BRIN is designed for handling very large tables
in which certain columns have some natural correlation with their
physical location within the table.
@@ -64,4 +64,4 @@
LOG: request for BRIN range summarization for index "brin_wi_idx" page 128 was not recorded
When this happens, the range will be summarized normally during the next
regular vacuum of the table.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/btree-gin.html postgresql-10-10.19/doc/src/sgml/html/btree-gin.html
--- postgresql-10-10.17/doc/src/sgml/html/btree-gin.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/btree-gin.html 2021-11-08 22:25:11.000000000 +0000
@@ -1,5 +1,5 @@
-F.6. btree_gin
btree_gin provides sample GIN operator classes that
implement B-tree equivalent behavior for the data types
int2, int4, int8, float4,
float8, timestamp with time zone,
@@ -25,4 +25,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/btree-gist.html postgresql-10-10.19/doc/src/sgml/html/btree-gist.html
--- postgresql-10-10.17/doc/src/sgml/html/btree-gist.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/btree-gist.html 2021-11-08 22:25:11.000000000 +0000
@@ -1,5 +1,5 @@
-F.7. btree_gist
btree_gist provides GiST index operator classes that
implement B-tree equivalent behavior for the data types
int2, int4, int8, float4,
float8, numeric, timestamp with time zone,
@@ -62,4 +62,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/bug-reporting.html postgresql-10-10.19/doc/src/sgml/html/bug-reporting.html
--- postgresql-10-10.17/doc/src/sgml/html/bug-reporting.html 2021-05-10 20:58:05.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/bug-reporting.html 2021-11-08 22:24:48.000000000 +0000
@@ -1,5 +1,5 @@
-5. Bug Reporting Guidelines
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
care cannot guarantee that every part of
@@ -130,7 +130,7 @@
If you run a prepackaged version, such as RPMs, say so, including any
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 10.17 we will almost certainly
+
If your version is older than 10.19 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
@@ -209,4 +209,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 -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-aggregate.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-aggregate.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-aggregate.html 2021-05-10 20:58:22.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-aggregate.html 2021-11-08 22:25:05.000000000 +0000
@@ -1,5 +1,5 @@
-51.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
that matches a query condition) and returns a single value computed
@@ -34,4 +34,4 @@
command. See Section 37.10 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 -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-am.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-am.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-am.html 2021-05-10 20:58:22.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-am.html 2021-11-08 22:25:05.000000000 +0000
@@ -1,5 +1,5 @@
-51.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.
Currently, only indexes have access methods. The requirements for index
@@ -14,4 +14,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.63.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-amop.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-amop.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-amop.html 2021-05-10 20:58:22.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-amop.html 2021-11-08 22:25:05.000000000 +0000
@@ -1,5 +1,5 @@
-51.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
member can be either a search operator or an
@@ -40,4 +40,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 -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-amproc.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-amproc.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-amproc.html 2021-05-10 20:58:22.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-amproc.html 2021-11-08 22:25:05.000000000 +0000
@@ -1,5 +1,5 @@
-51.5. pg_amproc
The catalog pg_amproc stores information about
support procedures associated with access method operator families. There
is one row for each support procedure belonging to an operator family.
Table 51.5. pg_amproc Columns
Name
Type
References
Description
oid
oid
Row identifier (hidden attribute; must be explicitly selected)
The usual interpretation of the
@@ -11,4 +11,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 -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-attrdef.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-attrdef.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-attrdef.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-attrdef.html 2021-11-08 22:25:05.000000000 +0000
@@ -1,5 +1,5 @@
-51.6. pg_attrdef
The catalog pg_attrdef stores column default values. The main information
about columns is stored in pg_attribute
(see below). Only columns that explicitly specify a default value
(when the table is created or the column is added) will have an
@@ -9,4 +9,4 @@
the representation of the default value. Reverse-compiling the
adbin field (with pg_get_expr for
example) is a better way to display the default value.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-attribute.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-attribute.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-attribute.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-attribute.html 2021-11-08 22:25:05.000000000 +0000
@@ -1,5 +1,5 @@
-51.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
table in the database. (There will also be attribute entries for
@@ -65,4 +65,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 -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-authid.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-authid.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-authid.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-authid.html 2021-11-08 22:25:05.000000000 +0000
@@ -1,5 +1,5 @@
-51.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
role with the rolcanlogin flag set. Any role (with or
@@ -41,4 +41,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-auth-members.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-auth-members.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-auth-members.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-auth-members.html 2021-11-08 22:25:05.000000000 +0000
@@ -1,5 +1,5 @@
-51.9. pg_auth_members
The catalog pg_cast stores data type conversion
paths, both built-in and user-defined.
It should be noted that pg_cast does not represent
every type conversion that the system knows how to perform; only those that
@@ -43,4 +43,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 -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-class.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-class.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-class.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-class.html 2021-11-08 22:25:05.000000000 +0000
@@ -1,5 +1,5 @@
-51.11. pg_class
The catalog pg_class catalogs tables and most
everything else that has columns or is otherwise similar to a
table. This includes indexes (but see also
pg_index), sequences (but see also
@@ -99,4 +99,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 -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-collation.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-collation.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-collation.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-collation.html 2021-11-08 22:25:05.000000000 +0000
@@ -1,5 +1,5 @@
-51.12. pg_collation
The catalog pg_collation describes the
available collations, which are essentially mappings from an SQL
name to operating system locale categories.
See Section 23.2 for more information.
@@ -27,4 +27,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 -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-constraint.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-constraint.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-constraint.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-constraint.html 2021-11-08 22:25:05.000000000 +0000
@@ -1,5 +1,5 @@
-51.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
equivalent to some table constraint.)
@@ -55,4 +55,4 @@
Note
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 -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-conversion.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-conversion.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-conversion.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-conversion.html 2021-11-08 22:25:05.000000000 +0000
@@ -1,6 +1,6 @@
-51.14. pg_conversion
The catalog pg_database stores information about
the available databases. Databases are created with the CREATE DATABASE command.
Consult Chapter 22 for details about the meaning
of some of the parameters.
@@ -40,4 +40,4 @@
GRANT and
REVOKE
for details
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-db-role-setting.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-db-role-setting.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-db-role-setting.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-db-role-setting.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,9 +1,9 @@
-51.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.
Unlike most system catalogs, pg_db_role_setting
is shared across all databases of a cluster: there is only one
copy of pg_db_role_setting per cluster, not
one per database.
-
The OID of the namespace associated with this entry,
or 0 if none
defaclobjtype
char
Type of object this entry is for:
@@ -22,4 +22,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 -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-depend.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-depend.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-depend.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-depend.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.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
by DROP CASCADE or prevent dropping in the DROP
@@ -64,4 +64,4 @@
Other dependency flavors might be needed in future.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-description.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-description.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-description.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-description.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.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
psql's \d commands.
@@ -12,4 +12,4 @@
objoid and classoid refer to
the table itself). For all other object types, this column is
zero.
-
description
text
Arbitrary text that serves as the description of this object
\ No newline at end of file
+
description
text
Arbitrary text that serves as the description of this object
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-enum.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-enum.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-enum.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-enum.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.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
of its associated row in pg_enum.
@@ -17,4 +17,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 -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-event-trigger.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-event-trigger.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-event-trigger.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-event-trigger.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.21. pg_event_trigger
Array of regclass OIDs for the extension's configuration
@@ -12,4 +12,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 -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-foreign-data-wrapper.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-foreign-data-wrapper.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-foreign-data-wrapper.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-foreign-data-wrapper.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.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
accessed.
@@ -16,4 +16,4 @@
REVOKE
for details
fdwoptions
text[]
Foreign-data wrapper specific options, as “keyword=value” strings
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-foreign-server.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-foreign-server.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-foreign-server.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-foreign-server.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.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
servers are accessed via foreign-data wrappers.
@@ -8,4 +8,4 @@
REVOKE
for details
srvoptions
text[]
Foreign server specific options, as “keyword=value” strings
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-foreign-table.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-foreign-table.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-foreign-table.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-foreign-table.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,9 +1,9 @@
-51.25. pg_foreign_table
The catalog pg_foreign_table contains
auxiliary information about foreign tables. A foreign table is
primarily represented by a pg_class entry,
just like a regular table. Its pg_foreign_table
entry contains the information that is pertinent only to foreign tables
and not any other kind of relation.
The catalog pg_inherits records information about
table inheritance hierarchies. There is one entry for each direct
child table in the database. (Indirect inheritance can be determined
by following chains of entries.)
@@ -8,4 +8,4 @@
inhseqno
int4
If there is more than one direct parent for a child table (multiple
inheritance), this number tells the order in which the
inherited columns are to be arranged. The count starts at 1.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-init-privs.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-init-privs.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-init-privs.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-init-privs.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.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)
initial set of privileges.
@@ -28,4 +28,4 @@
GRANT and
REVOKE
for details
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-language.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-language.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-language.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-language.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.29. pg_language
The catalog pg_language registers
languages in which you can write functions or stored procedures.
See CREATE LANGUAGE
and Chapter 41 for more information about language handlers.
@@ -27,4 +27,4 @@
GRANT and
REVOKE
for details
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-largeobject.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-largeobject.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-largeobject.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-largeobject.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.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
segments or “pages” small enough to be conveniently stored as rows
@@ -22,4 +22,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 -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-largeobject-metadata.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-largeobject-metadata.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-largeobject-metadata.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-largeobject-metadata.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.31. pg_largeobject_metadata
The catalog pg_largeobject_metadata
holds metadata associated with large objects. The actual large object
data is stored in
pg_largeobject.
@@ -7,4 +7,4 @@
GRANT and
REVOKE
for details
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-namespace.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-namespace.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-namespace.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-namespace.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.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
conflicts.
@@ -7,4 +7,4 @@
GRANT and
REVOKE
for details
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-opclass.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-opclass.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-opclass.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-opclass.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.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
index access method. An operator class essentially specifies that a
@@ -13,4 +13,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 -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-operator.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-operator.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-operator.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-operator.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,10 +1,10 @@
-51.34. pg_operator
Join selectivity estimation function for this operator
Unused columns contain zeroes. For example, oprleft
is zero for a prefix operator.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-opfamily.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-opfamily.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-opfamily.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-opfamily.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.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
index access method. Furthermore, the operators in a family are all
@@ -14,4 +14,4 @@
pg_amproc,
and
pg_opclass.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-partitioned-table.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-partitioned-table.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-partitioned-table.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-partitioned-table.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.36. pg_partitioned_table
The OID of the pg_class entry for this partitioned table
partstrat
char
Partitioning strategy; l = list partitioned table,
r = range partitioned table
@@ -20,4 +20,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 -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-pltemplate.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-pltemplate.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-pltemplate.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-pltemplate.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.37. pg_pltemplate
The catalog pg_pltemplate stores
“template” information for procedural languages.
A template for a language allows the language to be created in a
particular database by a simple CREATE LANGUAGE command,
@@ -17,4 +17,4 @@
future release of PostgreSQL, in favor of
keeping this knowledge about procedural languages in their respective
extension installation scripts.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-policy.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-policy.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-policy.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-policy.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.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
applies to, the expression to be added as a security-barrier
@@ -14,4 +14,4 @@
or * for all
The expression tree to be added to the security barrier qualifications for queries that use the table
polwithcheck
pg_node_tree
The expression tree to be added to the WITH CHECK qualifications for queries that attempt to add rows to the table
Note
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 -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-proc.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-proc.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-proc.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-proc.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.39. pg_proc
The catalog pg_proc stores information about functions (or procedures).
See CREATE FUNCTION
and Section 37.3 for more information.
The table contains data for aggregate functions as well as plain functions.
@@ -89,4 +89,4 @@
text. probin is unused 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 -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-publication.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-publication.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-publication.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-publication.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.40. pg_publication
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 51.78
for a more user-friendly view of this information.
-
OID of the function to convert a range value into canonical form,
@@ -9,4 +9,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 -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-replication-origin.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-replication-origin.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-replication-origin.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-replication-origin.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,7 +1,7 @@
-51.43. pg_replication_origin
The catalog pg_seclabel stores security
labels on database objects. Security labels can be manipulated
with the SECURITY LABEL command. For an easier
way to view security labels, see Section 51.83.
@@ -10,4 +10,4 @@
objoid and classoid refer to
the table itself). For all other object types, this column is
zero.
-
provider
text
The label provider associated with this label.
label
text
The security label applied to this object.
\ No newline at end of file
+
provider
text
The label provider associated with this label.
label
text
The security label applied to this object.
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-sequence.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-sequence.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-sequence.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-sequence.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.46. 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 pg_class.
-
The catalog pg_shdepend records the
dependency relationships between database objects and shared objects,
such as roles. This information allows
PostgreSQL to ensure that those objects are
@@ -40,4 +40,4 @@
Other dependency flavors might be needed in future. Note in particular
that the current definition only supports roles as referenced objects.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-shdescription.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-shdescription.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-shdescription.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-shdescription.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.48. 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
psql's \d commands.
@@ -10,4 +10,4 @@
is shared across all databases of a cluster: there is only one
copy of pg_shdescription per cluster, not
one per database.
-
Table 51.48. pg_shdescription Columns
Name
Type
References
Description
objoid
oid
any OID column
The OID of the object this description pertains to
The catalog pg_shseclabel stores security
labels on shared database objects. Security labels can be manipulated
with the SECURITY LABEL command. For an easier
way to view security labels, see Section 51.83.
@@ -10,4 +10,4 @@
is shared across all databases of a cluster: there is only one
copy of pg_shseclabel per cluster, not
one per database.
-
Table 51.49. pg_shseclabel Columns
Name
Type
References
Description
objoid
oid
any OID column
The OID of the object this security label pertains to
The catalog pg_statistic_ext
holds extended planner statistics.
Each row in this catalog corresponds to a statistics object
created with CREATE STATISTICS.
@@ -19,4 +19,4 @@
statistics object, indicating which statistic type(s) are desired.
The fields after it are initially NULL and are filled only when the
corresponding statistic has been computed by ANALYZE.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-statistic.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-statistic.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-statistic.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-statistic.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.50. pg_statistic
The catalog pg_statistic stores
statistical data about the contents of the database. Entries are
created by ANALYZE
and subsequently used by the query planner. Note that all the
@@ -63,4 +63,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 -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-subscription.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-subscription.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-subscription.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-subscription.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.52. pg_subscription
The catalog pg_subscription contains all existing
logical replication subscriptions. For more information about logical
replication see Chapter 31.
Unlike most system catalogs, pg_subscription is
@@ -15,4 +15,4 @@
null represents NONE
subpublications
text[]
Array of subscribed publication names. These reference the
publications on the publisher server. For more on publications
see Section 31.1.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-subscription-rel.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-subscription-rel.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-subscription-rel.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-subscription-rel.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.53. 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.
This catalog only contains tables known to the subscription after running
@@ -13,4 +13,4 @@
srsublsn
pg_lsn
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 -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-tablespace.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-tablespace.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-tablespace.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-tablespace.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.54. 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.
Unlike most system catalogs, pg_tablespace
@@ -11,4 +11,4 @@
REVOKE
for details
spcoptions
text[]
Tablespace-level options, as “keyword=value” strings
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-transform.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-transform.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-transform.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-transform.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.55. 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.
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 this operation is not supported.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-trigger.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-trigger.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-trigger.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-trigger.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.56. pg_trigger
The catalog pg_trigger stores triggers on tables
and views.
See CREATE TRIGGER
for more information.
@@ -30,4 +30,4 @@
deferrable and some non-deferrable triggers.
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 -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-ts-config.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-ts-config.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-ts-config.html 2021-05-10 20:58:23.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-ts-config.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,5 +1,5 @@
-51.57. 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
for each of the parser's output token types. The parser is shown
@@ -8,4 +8,4 @@
PostgreSQL's text search features are
described at length in Chapter 12.
Table 51.57. pg_ts_config Columns
Name
Type
References
Description
oid
oid
Row identifier (hidden attribute; must be explicitly selected)
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
parser.
PostgreSQL's text search features are
described at length in Chapter 12.
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
needed; the dictionary itself provides values for the user-settable
@@ -10,4 +10,4 @@
PostgreSQL's text search features are
described at length in Chapter 12.
Table 51.59. pg_ts_dict Columns
Name
Type
References
Description
oid
oid
Row identifier (hidden attribute; must be explicitly selected)
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.
Since a parser must be implemented by C-language-level functions,
@@ -7,4 +7,4 @@
PostgreSQL's text search features are
described at length in Chapter 12.
Table 51.60. pg_ts_parser Columns
Name
Type
References
Description
oid
oid
Row identifier (hidden attribute; must be explicitly selected)
The pg_ts_template catalog contains entries
defining text search templates. A template is the implementation
skeleton for a class of text search dictionaries.
Since a template must be implemented by C-language-level functions,
@@ -7,4 +7,4 @@
PostgreSQL's text search features are
described at length in Chapter 12.
Table 51.61. pg_ts_template Columns
Name
Type
References
Description
oid
oid
Row identifier (hidden attribute; must be explicitly selected)
The catalog pg_type stores information about data
types. Base types and enum types (scalar types) are created with
CREATE TYPE, and
domains with
@@ -136,4 +136,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 51.63. 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
\ No newline at end of file
+
Table 51.63. 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
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/catalog-pg-user-mapping.html postgresql-10-10.19/doc/src/sgml/html/catalog-pg-user-mapping.html
--- postgresql-10-10.17/doc/src/sgml/html/catalog-pg-user-mapping.html 2021-05-10 20:58:24.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalog-pg-user-mapping.html 2021-11-08 22:25:06.000000000 +0000
@@ -1,9 +1,9 @@
-51.63. 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
pg_user_mappings
instead.
Table 51.64. pg_user_mapping Columns
Name
Type
References
Description
oid
oid
Row identifier (hidden attribute; must be explicitly selected)
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.
PostgreSQL's system catalogs are regular
@@ -13,4 +13,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 -Nru postgresql-10-10.17/doc/src/sgml/html/catalogs-overview.html postgresql-10-10.19/doc/src/sgml/html/catalogs-overview.html
--- postgresql-10-10.17/doc/src/sgml/html/catalogs-overview.html 2021-05-10 20:58:22.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/catalogs-overview.html 2021-11-08 22:25:05.000000000 +0000
@@ -1,8 +1,8 @@
-51.1. Overview
Table 51.1 lists the system catalogs.
More detailed documentation of each catalog follows below.
Most system catalogs are copied from the template database during
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.
-
This chapter describes the available localization features from the
point of view of the administrator.
PostgreSQL supports two localization
facilities:
@@ -14,4 +14,4 @@
between client and server.
This is covered in Section 23.3.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/chkpass.html postgresql-10-10.19/doc/src/sgml/html/chkpass.html
--- postgresql-10-10.17/doc/src/sgml/html/chkpass.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/chkpass.html 2021-11-08 22:25:11.000000000 +0000
@@ -1,5 +1,5 @@
-F.8. chkpass
This module implements a data type chkpass that is
designed for storing encrypted passwords.
Each password is automatically converted to encrypted form upon entry,
and is always stored encrypted. To compare, simply compare against a clear
@@ -49,4 +49,4 @@
----------
f
(1 row)
The citext module provides a case-insensitive
character string type, citext. Essentially, it internally calls
lower when comparing values. Otherwise, it behaves almost
exactly like text.
@@ -113,4 +113,4 @@
will be invoked instead.
Inspired by the original citext module by Donald Fraser.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/client-authentication.html postgresql-10-10.19/doc/src/sgml/html/client-authentication.html
--- postgresql-10-10.17/doc/src/sgml/html/client-authentication.html 2021-05-10 20:58:11.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/client-authentication.html 2021-11-08 22:24:53.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 20. 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
as a particular user. Within the SQL environment the active database
@@ -29,4 +29,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 -Nru postgresql-10-10.17/doc/src/sgml/html/client-authentication-problems.html postgresql-10-10.19/doc/src/sgml/html/client-authentication-problems.html
--- postgresql-10-10.17/doc/src/sgml/html/client-authentication-problems.html 2021-05-10 20:58:11.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/client-authentication-problems.html 2021-11-08 22:24:53.000000000 +0000
@@ -1,5 +1,5 @@
-20.4. Authentication Problems
Authentication failures and related problems generally
manifest themselves through error messages like the following:
FATAL: no pg_hba.conf entry for host "123.123.123.123", user "andym", database "testdb"
This is what you are most likely to get if you succeed in contacting
@@ -23,4 +23,4 @@
Tip
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 -Nru postgresql-10-10.17/doc/src/sgml/html/client-interfaces.html postgresql-10-10.19/doc/src/sgml/html/client-interfaces.html
--- postgresql-10-10.17/doc/src/sgml/html/client-interfaces.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/client-interfaces.html 2021-11-08 22:24:57.000000000 +0000
@@ -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
interfaces for client programs that are distributed separately and
@@ -8,4 +8,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.
-
Here are some examples:
@@ -274,12 +274,8 @@
and BCP 47 for
details. The list of possible collation types (co
subtag) can be found in
- the CLDR
+ the CLDR
repository.
- The ICU Locale
- Explorer can be used to check the details of a particular locale
- definition. The examples using the k* subtags require
- at least ICU version 54.
Note that while this system allows creating collations that “ignore
case” or “ignore accents” or similar (using
the ks key), PostgreSQL does not at the moment allow
@@ -300,4 +296,4 @@
under a more readable name. For example:
CREATE COLLATION german FROM "de_DE";
CREATE COLLATION french FROM "fr-x-icu";
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/config-setting.html postgresql-10-10.19/doc/src/sgml/html/config-setting.html
--- postgresql-10-10.17/doc/src/sgml/html/config-setting.html 2021-05-10 20:58:10.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/config-setting.html 2021-11-08 22:24:53.000000000 +0000
@@ -1,5 +1,5 @@
-19.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
parameter:
@@ -254,4 +254,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/connect-estab.html postgresql-10-10.19/doc/src/sgml/html/connect-estab.html
--- postgresql-10-10.17/doc/src/sgml/html/connect-estab.html 2021-05-10 20:58:22.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/connect-estab.html 2021-11-08 22:25:05.000000000 +0000
@@ -1,5 +1,5 @@
-50.2. How Connections are Established
PostgreSQL is implemented using a
simple “process per user” client/server model. In this model
there is one client process connected to
exactly one server process. As we do not
@@ -25,4 +25,4 @@
server 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 -Nru postgresql-10-10.17/doc/src/sgml/html/continuous-archiving.html postgresql-10-10.19/doc/src/sgml/html/continuous-archiving.html
--- postgresql-10-10.17/doc/src/sgml/html/continuous-archiving.html 2021-05-10 20:58:11.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/continuous-archiving.html 2021-11-08 22:24:54.000000000 +0000
@@ -1,5 +1,5 @@
-25.3. Continuous Archiving and Point-in-Time Recovery (PITR)
25.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
every change made to the database's data files. This log exists
@@ -735,4 +735,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-build-sql-delete.html postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-build-sql-delete.html
--- postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-build-sql-delete.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-build-sql-delete.html 2021-11-08 22:25:11.000000000 +0000
@@ -1,5 +1,5 @@
-dblink_build_sql_delete
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
is in progress on the named connection. Note that this is not
certain to succeed (since, for example, the remote query might
already have finished). A cancel request simply improves the
@@ -9,4 +9,4 @@
Arguments
connname
Name of the connection to use.
Return Value
Returns OK if the cancel request has been sent, or
the text of an error message on failure.
-
Examples
SELECT dblink_cancel_query('dtest1');
\ No newline at end of file
+
Examples
SELECT dblink_cancel_query('dtest1');
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-close.html postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-close.html
--- postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-close.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-close.html 2021-11-08 22:25:11.000000000 +0000
@@ -1,5 +1,5 @@
-dblink_close
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
dblink_connect() establishes a connection to a remote
PostgreSQL database. The server and database to
be contacted are identified through a standard libpq
@@ -92,4 +92,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
+DROP SERVER fdtest;
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-connect-u.html postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-connect-u.html
--- postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-connect-u.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-connect-u.html 2021-11-08 22:25:11.000000000 +0000
@@ -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
dblink_connect_u() is identical to
dblink_connect(), except that it will allow non-superusers
to connect using any authentication method.
@@ -21,4 +21,4 @@
that any ~/.pgpass file belonging to the server's user
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 -Nru postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-disconnect.html postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-disconnect.html
--- postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-disconnect.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-disconnect.html 2021-11-08 22:25:11.000000000 +0000
@@ -1,5 +1,5 @@
-dblink_disconnect
dblink_disconnect — closes a persistent connection to a remote database
Synopsis
dblink_disconnect() returns text
dblink_disconnect(text connname) returns text
Description
dblink_disconnect() closes a connection previously opened
by dblink_connect(). The form with no arguments closes
an unnamed connection.
@@ -16,4 +16,4 @@
dblink_disconnect
-------------------
OK
-(1 row)
\ No newline at end of file
+(1 row)
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-error-message.html postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-error-message.html
--- postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-error-message.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-error-message.html 2021-11-08 22:25:11.000000000 +0000
@@ -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
error message for a given connection.
Arguments
connname
Name of the connection to use.
Return Value
Returns last error message, or OK if there has been
@@ -11,4 +11,4 @@
or dblink_get_result should be called prior to
dblink_error_message, so that any error generated by
the asynchronous query will be visible.
-
Examples
SELECT dblink_error_message('dtest1');
\ No newline at end of file
+
Examples
SELECT dblink_error_message('dtest1');
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-exec.html postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-exec.html
--- postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-exec.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-exec.html 2021-11-08 22:25:11.000000000 +0000
@@ -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
Description
dblink_exec executes a command (that is, any SQL statement
that doesn't return rows) in a remote database.
@@ -51,4 +51,4 @@
dblink_exec
-------------
ERROR
-(1 row)
\ No newline at end of file
+(1 row)
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-fetch.html postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-fetch.html
--- postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-fetch.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-fetch.html 2021-11-08 22:25:11.000000000 +0000
@@ -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
Description
dblink_fetch fetches rows from a cursor previously
established by dblink_open.
Arguments
connname
Name of the connection to use; omit this parameter to use the
@@ -63,4 +63,4 @@
SELECT * FROM dblink_fetch('foo', 5) AS (funcname name, source text);
funcname | source
----------+--------
-(0 rows)
\ No newline at end of file
+(0 rows)
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-function.html postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-function.html
--- postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-function.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-function.html 2021-11-08 22:25:11.000000000 +0000
@@ -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
Description
dblink executes a query (usually a SELECT,
but it can be any SQL statement that returns rows) in a remote database.
@@ -124,4 +124,4 @@
bytealt | bytealt
byteain | byteain
byteaout | byteaout
-(14 rows)
\ No newline at end of file
+(14 rows)
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-get-connections.html postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-get-connections.html
--- postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-get-connections.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-get-connections.html 2021-11-08 22:25:11.000000000 +0000
@@ -1,4 +1,4 @@
-dblink_get_connections
dblink_get_notify — retrieve async notifications on a connection
Synopsis
dblink_get_notify() returns setof (notify_name text, be_pid int, extra text)
dblink_get_notify(text connname) returns setof (notify_name text, be_pid int, extra text)
Description
dblink_get_notify retrieves notifications on either
the unnamed connection, or on a named connection if specified.
To receive notifications via dblink, LISTEN must
@@ -24,4 +24,4 @@
notify_name | be_pid | extra
-------------+--------+-------
virtual | 1229 |
-(1 row)
\ No newline at end of file
+(1 row)
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-get-pkey.html postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-get-pkey.html
--- postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-get-pkey.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-get-pkey.html 2021-11-08 22:25:11.000000000 +0000
@@ -1,5 +1,5 @@
-dblink_get_pkey
dblink_get_pkey provides information about the primary
key of a relation in the local database. This is sometimes useful
@@ -31,4 +31,4 @@
1 | f1
2 | f2
3 | f3
-(3 rows)
\ No newline at end of file
+(3 rows)
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-get-result.html postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-get-result.html
--- postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-get-result.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-get-result.html 2021-11-08 22:25:11.000000000 +0000
@@ -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
asynchronous query previously sent with dblink_send_query.
If the query is not already completed, dblink_get_result
will wait until it is.
@@ -84,4 +84,4 @@
contrib_regression=# SELECT * FROM dblink_get_result('dtest1') AS t1(f1 int, f2 text, f3 text[]);
f1 | f2 | f3
----+----+----
-(0 rows)
\ No newline at end of file
+(0 rows)
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-is-busy.html postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-is-busy.html
--- postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-is-busy.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-is-busy.html 2021-11-08 22:25:11.000000000 +0000
@@ -1,7 +1,7 @@
-dblink_is_busy
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
dblink_open() opens a cursor in a remote database.
The cursor can subsequently be manipulated with
dblink_fetch() and dblink_close().
@@ -34,4 +34,4 @@
dblink_open
-------------
OK
-(1 row)
\ No newline at end of file
+(1 row)
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-send-query.html postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-send-query.html
--- postgresql-10-10.17/doc/src/sgml/html/contrib-dblink-send-query.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/contrib-dblink-send-query.html 2021-11-08 22:25:11.000000000 +0000
@@ -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
asynchronously, that is, without immediately waiting for the result.
There must not be an async query already in progress on the
connection.
@@ -12,4 +12,4 @@
sql
The SQL statement that you wish to execute in the remote database,
for example select * from pg_class.
Return Value
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
+
Examples
SELECT dblink_send_query('dtest1', 'SELECT * FROM foo WHERE f1 < 3');
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/contrib.html postgresql-10-10.19/doc/src/sgml/html/contrib.html
--- postgresql-10-10.17/doc/src/sgml/html/contrib.html 2021-05-10 20:58:29.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/contrib.html 2021-11-08 22:25:12.000000000 +0000
@@ -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
primary key field values with alternative supplied values
@@ -72,4 +72,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/contrib-prog-client.html postgresql-10-10.19/doc/src/sgml/html/contrib-prog-client.html
--- postgresql-10-10.17/doc/src/sgml/html/contrib-prog-client.html 2021-05-10 20:58:29.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/contrib-prog-client.html 2021-11-08 22:25:12.000000000 +0000
@@ -1,8 +1,8 @@
-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 are that part of the core PostgreSQL
distribution.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/contrib-prog.html postgresql-10-10.19/doc/src/sgml/html/contrib-prog.html
--- postgresql-10-10.17/doc/src/sgml/html/contrib-prog.html 2021-05-10 20:58:29.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/contrib-prog.html 2021-11-08 22:25:12.000000000 +0000
@@ -1,5 +1,5 @@
-Appendix G. Additional Supplied Programs
pg_standby — supports the creation of a PostgreSQL warm standby server
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
more information about the contrib section in general and
@@ -10,4 +10,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 -Nru postgresql-10-10.17/doc/src/sgml/html/contrib-prog-server.html postgresql-10-10.19/doc/src/sgml/html/contrib-prog-server.html
--- postgresql-10-10.17/doc/src/sgml/html/contrib-prog-server.html 2021-05-10 20:58:29.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/contrib-prog-server.html 2021-11-08 22:25:12.000000000 +0000
@@ -1,6 +1,6 @@
-G.2. Server Applications
pg_standby — supports the creation of a PostgreSQL warm standby server
This section covers PostgreSQL server-related
applications in contrib. They are typically run on the
host where the database server resides. 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 -Nru postgresql-10-10.17/doc/src/sgml/html/contrib-spi.html postgresql-10-10.19/doc/src/sgml/html/contrib-spi.html
--- postgresql-10-10.17/doc/src/sgml/html/contrib-spi.html 2021-05-10 20:58:29.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/contrib-spi.html 2021-11-08 22:25:12.000000000 +0000
@@ -1,5 +1,5 @@
-F.37. spi
The spi module provides several workable examples
of using the Server Programming Interface
(SPI) and triggers. While these functions are of
some value in
@@ -120,4 +120,4 @@
The column must be of type timestamp or timestamp with
time zone.
There is an example in moddatetime.example.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/creating-cluster.html postgresql-10-10.19/doc/src/sgml/html/creating-cluster.html
--- postgresql-10-10.17/doc/src/sgml/html/creating-cluster.html 2021-05-10 20:58:10.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/creating-cluster.html 2021-11-08 22:24:53.000000000 +0000
@@ -1,5 +1,5 @@
-18.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
database cluster is a collection of databases that is managed by a
@@ -129,4 +129,4 @@
documentation concerning data consistency guarantees.
PostgreSQL cannot be more reliable than
the file system it's using.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/cube.html postgresql-10-10.19/doc/src/sgml/html/cube.html
--- postgresql-10-10.17/doc/src/sgml/html/cube.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/cube.html 2021-11-08 22:25:11.000000000 +0000
@@ -1,5 +1,5 @@
-F.10. cube
This module implements a data type cube for
representing multidimensional cubes.
F.10.1. Syntax
Table F.3 shows the valid external
representations for the cube
@@ -166,4 +166,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/custom-scan-execution.html postgresql-10-10.19/doc/src/sgml/html/custom-scan-execution.html
--- postgresql-10-10.17/doc/src/sgml/html/custom-scan-execution.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/custom-scan-execution.html 2021-11-08 22:25:07.000000000 +0000
@@ -1,5 +1,5 @@
-58.3. Executing Custom Scans
When a CustomScan is executed, its execution state is
represented by a CustomScanState, which is declared as
follows:
typedef struct CustomScanState
@@ -96,4 +96,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/custom-scan.html postgresql-10-10.19/doc/src/sgml/html/custom-scan.html
--- postgresql-10-10.17/doc/src/sgml/html/custom-scan.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/custom-scan.html 2021-11-08 22:25:07.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 58. 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
responsible for knowing how to scan its own foreign tables, a custom scan
@@ -16,4 +16,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 -Nru postgresql-10-10.17/doc/src/sgml/html/custom-scan-path.html postgresql-10-10.19/doc/src/sgml/html/custom-scan-path.html
--- postgresql-10-10.17/doc/src/sgml/html/custom-scan-path.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/custom-scan-path.html 2021-11-08 22:25:07.000000000 +0000
@@ -1,5 +1,5 @@
-58.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
Gather paths, which are made after this call so that they can use
@@ -63,4 +63,4 @@
Convert a custom path to a finished plan. The return value will generally
be a CustomScan object, which the callback must allocate and
initialize. See Section 58.2 for more details.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/custom-scan-plan.html postgresql-10-10.19/doc/src/sgml/html/custom-scan-plan.html
--- postgresql-10-10.17/doc/src/sgml/html/custom-scan-plan.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/custom-scan-plan.html 2021-11-08 22:25:07.000000000 +0000
@@ -1,5 +1,5 @@
-58.2. Creating Custom Scan Plans
A custom scan is represented in a finished plan tree using the following
structure:
typedef struct CustomScan
{
@@ -55,4 +55,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/database-roles.html postgresql-10-10.19/doc/src/sgml/html/database-roles.html
--- postgresql-10-10.17/doc/src/sgml/html/database-roles.html 2021-05-10 20:58:11.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/database-roles.html 2021-11-08 22:24:53.000000000 +0000
@@ -1,5 +1,5 @@
-21.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
are global across a database cluster installation (and not
@@ -53,4 +53,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/datatype-binary.html postgresql-10-10.19/doc/src/sgml/html/datatype-binary.html
--- postgresql-10-10.17/doc/src/sgml/html/datatype-binary.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/datatype-binary.html 2021-11-08 22:24:49.000000000 +0000
@@ -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
A binary string is a sequence of octets (or bytes). Binary
strings are distinguished from character strings in two
@@ -107,4 +107,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/datatype-bit.html postgresql-10-10.19/doc/src/sgml/html/datatype-bit.html
--- postgresql-10-10.17/doc/src/sgml/html/datatype-bit.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/datatype-bit.html 2021-11-08 22:24:49.000000000 +0000
@@ -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
varying(n), where
@@ -35,4 +35,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/datatype-boolean.html postgresql-10-10.19/doc/src/sgml/html/datatype-boolean.html
--- postgresql-10-10.17/doc/src/sgml/html/datatype-boolean.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/datatype-boolean.html 2021-11-08 22:24:49.000000000 +0000
@@ -1,5 +1,5 @@
-8.6. Boolean Type
PostgreSQL provides the
standard SQL type boolean;
see Table 8.19.
The boolean type can have several states:
@@ -47,4 +47,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/datatype-character.html postgresql-10-10.19/doc/src/sgml/html/datatype-character.html
--- postgresql-10-10.17/doc/src/sgml/html/datatype-character.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/datatype-character.html 2021-11-08 22:24:49.000000000 +0000
@@ -1,5 +1,5 @@
-8.3. Character Types
Table 8.4 shows the
general-purpose character types available in
PostgreSQL.
SQL defines two primary character types:
@@ -117,4 +117,4 @@
(note the quotes) is different from char(1) in that it
only uses one byte of storage. It is internally 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 -Nru postgresql-10-10.17/doc/src/sgml/html/datatype-datetime.html postgresql-10-10.19/doc/src/sgml/html/datatype-datetime.html
--- postgresql-10-10.17/doc/src/sgml/html/datatype-datetime.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/datatype-datetime.html 2021-11-08 22:24:49.000000000 +0000
@@ -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
Section 9.9.
@@ -102,7 +102,7 @@
is required in order to determine whether standard or daylight-savings
time applies. The appropriate time zone offset is recorded in the
time with time zone value.
-
Table 8.11. Time Input
Example
Description
04:05:06.789
ISO 8601
04:05:06
ISO 8601
04:05
ISO 8601
040506
ISO 8601
04:05 AM
same as 04:05; AM does not affect value
04:05 PM
same as 16:05; input hour must be <= 12
04:05:06.789-8
ISO 8601
04:05:06-08:00
ISO 8601
04:05-08:00
ISO 8601
040506-08
ISO 8601
04:05:06 PST
time zone specified by abbreviation
2003-04-12 04:05:06 America/New_York
time zone specified by full name
Table 8.12. Time Zone Input
Example
Description
PST
Abbreviation (for Pacific Standard Time)
America/New_York
Full time zone name
PST8PDT
POSIX-style time zone specification
-8:00
ISO-8601 offset for PST
-800
ISO-8601 offset for PST
-8
ISO-8601 offset for PST
zulu
Military abbreviation for UTC
z
Short form of zulu
Refer to Section 8.5.3 for more information on how
+
Table 8.11. Time Input
Example
Description
04:05:06.789
ISO 8601
04:05:06
ISO 8601
04:05
ISO 8601
040506
ISO 8601
04:05 AM
same as 04:05; AM does not affect value
04:05 PM
same as 16:05; input hour must be <= 12
04:05:06.789-8
ISO 8601, with time zone as UTC offset
04:05:06-08:00
ISO 8601, with time zone as UTC offset
04:05-08:00
ISO 8601, with time zone as UTC offset
040506-08
ISO 8601, with time zone as UTC offset
040506+0730
ISO 8601, with fractional-hour time zone as UTC offset
040506+07:30:00
UTC offset specified to seconds (not allowed in ISO 8601)
04:05:06 PST
time zone specified by abbreviation
2003-04-12 04:05:06 America/New_York
time zone specified by full name
Table 8.12. Time Zone Input
Example
Description
PST
Abbreviation (for Pacific Standard Time)
America/New_York
Full time zone name
PST8PDT
POSIX-style time zone specification
-8:00:00
UTC offset for PST
-8:00
UTC offset for PST (ISO 8601 extended format)
-800
UTC offset for PST (ISO 8601 basic format)
-8
UTC offset for PST (ISO 8601 basic format)
zulu
Military abbreviation for UTC
z
Short form of zulu (also in ISO 8601)
Refer to Section 8.5.3 for more information on how
to specify time zones.
8.5.1.3. Time Stamps
Valid input for the time stamp types consists of the concatenation
of a date and a time, followed by an optional time zone,
@@ -217,7 +217,22 @@
(See Section 8.5.1
for how this setting also affects interpretation of input values.)
Table 8.15 shows examples.
-
Table 8.15. Date Order Conventions
datestyle Setting
Input Ordering
Example Output
SQL, DMY
day/month/year
17/12/1997 15:37:16.00 CET
SQL, MDY
month/day/year
12/17/1997 07:37:16.00 PST
Postgres, DMY
day/month/year
Wed 17 Dec 07:37:16 1997 PST
The date/time style can be selected by the user using the
+
Table 8.15. Date Order Conventions
datestyle Setting
Input Ordering
Example Output
SQL, DMY
day/month/year
17/12/1997 15:37:16.00 CET
SQL, MDY
month/day/year
12/17/1997 07:37:16.00 PST
Postgres, DMY
day/month/year
Wed 17 Dec 07:37:16 1997 PST
In the ISO style, the time zone is always shown as
+ a signed numeric offset from UTC, with positive sign used for zones
+ east of Greenwich. The offset will be shown
+ as hh (hours only) if it is an integral
+ number of hours, else
+ as hh:mm if it
+ is an integral number of minutes, else as
+ hh:mm:ss.
+ (The third case is not possible with any modern time zone standard,
+ but it can appear when working with timestamps that predate the
+ adoption of standardized time zones.)
+ In the other date styles, the time zone is shown as an alphabetic
+ abbreviation if one is in common use in the current zone. Otherwise
+ it appears as a signed numeric offset in ISO 8601 basic format
+ (hh or hhmm).
+
The date/time style can be selected by the user using the
SET datestyle command, the DateStyle parameter in the
postgresql.conf configuration file, or the
PGDATESTYLE environment variable on the server or
@@ -396,22 +411,25 @@
Otherwise the traditional PostgreSQL interpretation is
used. To avoid ambiguity, it's recommended to attach an explicit sign
to each field if any field is negative.
-
In the verbose input format, and in some fields of the more compact
- input formats, field values can have fractional parts; for example
- '1.5 week' or '01:02:03.45'. Such input is
- converted to the appropriate number of months, days, and seconds
- for storage. When this would result in a fractional number of
- months or days, the fraction is added to the lower-order fields
- using the conversion factors 1 month = 30 days and 1 day = 24 hours.
- For example, '1.5 month' becomes 1 month and 15 days.
- Only seconds will ever be shown as fractional on output.
+
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
+ units. Fractional parts of units greater than months are truncated to
+ be an integer number of months, e.g. '1.5 years'
+ becomes '1 year 6 mons'. Fractional parts of
+ weeks and days are computed to be an integer number of days and
+ microseconds, assuming 30 days per month and 24 hours per day, e.g.,
+ '1.75 months' becomes 1 mon 22 days
+ 12:00:00. Only seconds will ever be shown as fractional
+ on output.
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 seconds. This is done because the number of days in a month
+ 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 seconds field can store fractions. Because intervals are
+ 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:
@@ -452,4 +470,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/datatype-enum.html postgresql-10-10.19/doc/src/sgml/html/datatype-enum.html
--- postgresql-10-10.17/doc/src/sgml/html/datatype-enum.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/datatype-enum.html 2021-11-08 22:24:49.000000000 +0000
@@ -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
types supported in a number of programming languages. An example of an enum
@@ -93,4 +93,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/datatype-geometric.html postgresql-10-10.19/doc/src/sgml/html/datatype-geometric.html
--- postgresql-10-10.17/doc/src/sgml/html/datatype-geometric.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/datatype-geometric.html 2021-11-08 22:24:49.000000000 +0000
@@ -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.
Table 8.20. Geometric Types
Name
Storage Size
Description
Representation
point
16 bytes
Point on a plane
(x,y)
line
32 bytes
Infinite line
{A,B,C}
lseg
32 bytes
Finite line segment
((x1,y1),(x2,y2))
box
32 bytes
Rectangular box
((x1,y1),(x2,y2))
path
16+16n bytes
Closed path (similar to polygon)
((x1,y1),...)
path
16+16n bytes
Open path
[(x1,y1),...]
polygon
40+16n bytes
Polygon (similar to closed path)
((x1,y1),...)
circle
24 bytes
Circle
<(x,y),r> (center point and radius)
A rich set of functions and operators is available to perform various geometric
@@ -114,4 +114,4 @@
is the center point and r is the radius of the
circle.
Circles are output using the first syntax.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/datatype.html postgresql-10-10.19/doc/src/sgml/html/datatype.html
--- postgresql-10-10.17/doc/src/sgml/html/datatype.html 2021-05-10 20:58:07.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/datatype.html 2021-11-08 22:24:49.000000000 +0000
@@ -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.
Table 8.1 shows all the built-in general-purpose data
@@ -29,4 +29,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 -Nru postgresql-10-10.17/doc/src/sgml/html/datatype-json.html postgresql-10-10.19/doc/src/sgml/html/datatype-json.html
--- postgresql-10-10.17/doc/src/sgml/html/datatype-json.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/datatype-json.html 2021-11-08 22:24:49.000000000 +0000
@@ -1,5 +1,5 @@
-8.14. JSON Types
JSON data types are for storing JSON (JavaScript Object Notation)
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
@@ -363,4 +363,4 @@
[6] 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 -Nru postgresql-10-10.17/doc/src/sgml/html/datatype-money.html postgresql-10-10.19/doc/src/sgml/html/datatype-money.html
--- postgresql-10-10.17/doc/src/sgml/html/datatype-money.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/datatype-money.html 2021-11-08 22:24:49.000000000 +0000
@@ -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.
The range shown in the table assumes there are two fractional digits.
@@ -32,4 +32,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/datatype-net-types.html postgresql-10-10.19/doc/src/sgml/html/datatype-net-types.html
--- postgresql-10-10.17/doc/src/sgml/html/datatype-net-types.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/datatype-net-types.html 2021-11-08 22:24:49.000000000 +0000
@@ -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
network addresses, because
@@ -112,4 +112,4 @@
0a:00:2b:ff:fe:01:02:03
(1 row)
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/datatype-numeric.html postgresql-10-10.19/doc/src/sgml/html/datatype-numeric.html
--- postgresql-10-10.17/doc/src/sgml/html/datatype-numeric.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/datatype-numeric.html 2021-11-08 22:24:49.000000000 +0000
@@ -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
available types.
@@ -244,4 +244,4 @@
automatically dropped when the owning column is dropped.
You can drop the sequence without dropping the column, but this
will force removal of the column default expression.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/datatype-oid.html postgresql-10-10.19/doc/src/sgml/html/datatype-oid.html
--- postgresql-10-10.17/doc/src/sgml/html/datatype-oid.html 2021-05-10 20:58:07.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/datatype-oid.html 2021-11-08 22:24:49.000000000 +0000
@@ -1,5 +1,5 @@
-8.18. Object Identifier Types
Object identifiers (OIDs) are used internally by
PostgreSQL as primary keys for various
system tables. OIDs are not added to user-created tables, unless
WITH OIDS is specified when the table is
@@ -77,4 +77,4 @@
(block number, tuple index within block) that identifies the
physical location of the row within its table.
(The system columns are further explained in Section 5.4.)
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/datatype-pg-lsn.html postgresql-10-10.19/doc/src/sgml/html/datatype-pg-lsn.html
--- postgresql-10-10.17/doc/src/sgml/html/datatype-pg-lsn.html 2021-05-10 20:58:07.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/datatype-pg-lsn.html 2021-11-08 22:24:49.000000000 +0000
@@ -1,5 +1,5 @@
-8.19. 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
PostgreSQL.
@@ -11,4 +11,4 @@
>. Two LSNs can be subtracted using the
- operator; the result is the number of bytes separating
those write-ahead log locations.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/datatype-pseudo.html postgresql-10-10.19/doc/src/sgml/html/datatype-pseudo.html
--- postgresql-10-10.17/doc/src/sgml/html/datatype-pseudo.html 2021-05-10 20:58:07.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/datatype-pseudo.html 2021-11-08 22:24:49.000000000 +0000
@@ -1,5 +1,5 @@
-8.20. 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
column data type, but it can be used to declare a function's
@@ -40,4 +40,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 -Nru postgresql-10-10.17/doc/src/sgml/html/datatype-textsearch.html postgresql-10-10.19/doc/src/sgml/html/datatype-textsearch.html
--- postgresql-10-10.17/doc/src/sgml/html/datatype-textsearch.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/datatype-textsearch.html 2021-11-08 22:24:49.000000000 +0000
@@ -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
to locate those that best match a query.
@@ -157,4 +157,4 @@
---------------+------------
'postgradu':1 | 'postgr':*
which will match the stemmed form of postgraduate.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/datatype-uuid.html postgresql-10-10.19/doc/src/sgml/html/datatype-uuid.html
--- postgresql-10-10.17/doc/src/sgml/html/datatype-uuid.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/datatype-uuid.html 2021-11-08 22:24:49.000000000 +0000
@@ -1,5 +1,5 @@
-8.12. UUID Type
The data type uuid stores Universally Unique Identifiers
(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
@@ -35,4 +35,4 @@
function for random UUIDs.
Alternatively, UUIDs could be generated by client applications or
other libraries invoked through a server-side function.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/datatype-xml.html postgresql-10-10.19/doc/src/sgml/html/datatype-xml.html
--- postgresql-10-10.17/doc/src/sgml/html/datatype-xml.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/datatype-xml.html 2021-11-08 22:24:49.000000000 +0000
@@ -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
functions to perform type-safe operations on it; see Section 9.14. Use of this data type requires the
@@ -122,4 +122,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/datetime-appendix.html postgresql-10-10.19/doc/src/sgml/html/datetime-appendix.html
--- postgresql-10-10.17/doc/src/sgml/html/datetime-appendix.html 2021-05-10 20:58:26.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/datetime-appendix.html 2021-11-08 22:25:09.000000000 +0000
@@ -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
determination of what kind of information can be in the
@@ -10,4 +10,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 -Nru postgresql-10-10.17/doc/src/sgml/html/datetime-config-files.html postgresql-10-10.19/doc/src/sgml/html/datetime-config-files.html
--- postgresql-10-10.17/doc/src/sgml/html/datetime-config-files.html 2021-05-10 20:58:26.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/datetime-config-files.html 2021-11-08 22:25:09.000000000 +0000
@@ -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
timezone_abbreviations run-time parameter
@@ -80,4 +80,4 @@
Caution
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 -Nru postgresql-10-10.17/doc/src/sgml/html/datetime-input-rules.html postgresql-10-10.19/doc/src/sgml/html/datetime-input-rules.html
--- postgresql-10-10.17/doc/src/sgml/html/datetime-input-rules.html 2021-05-10 20:58:26.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/datetime-input-rules.html 2021-11-08 22:25:08.000000000 +0000
@@ -1,5 +1,5 @@
-B.1. Date/Time Input Interpretation
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.
During a daylight-savings-time transition, it is possible for a
@@ -50,4 +50,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 -Nru postgresql-10-10.17/doc/src/sgml/html/datetime-julian-dates.html postgresql-10-10.19/doc/src/sgml/html/datetime-julian-dates.html
--- postgresql-10-10.17/doc/src/sgml/html/datetime-julian-dates.html 2021-05-10 20:58:26.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/datetime-julian-dates.html 2021-11-08 22:25:09.000000000 +0000
@@ -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
named similarly to that calendar.
@@ -39,4 +39,4 @@
-----------
2459389
(1 row)
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/datetime-keywords.html postgresql-10-10.19/doc/src/sgml/html/datetime-keywords.html
--- postgresql-10-10.17/doc/src/sgml/html/datetime-keywords.html 2021-05-10 20:58:26.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/datetime-keywords.html 2021-11-08 22:25:09.000000000 +0000
@@ -1,8 +1,8 @@
-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
Table B.2 shows the tokens that are
recognized as names of days of the week.
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 -Nru postgresql-10-10.17/doc/src/sgml/html/datetime-posix-timezone-specs.html postgresql-10-10.19/doc/src/sgml/html/datetime-posix-timezone-specs.html
--- postgresql-10-10.17/doc/src/sgml/html/datetime-posix-timezone-specs.html 2021-05-10 20:58:26.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/datetime-posix-timezone-specs.html 2021-11-08 22:25:09.000000000 +0000
@@ -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
variable. POSIX time zone specifications are
@@ -123,4 +123,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 -Nru postgresql-10-10.17/doc/src/sgml/html/datetime-units-history.html postgresql-10-10.19/doc/src/sgml/html/datetime-units-history.html
--- postgresql-10-10.17/doc/src/sgml/html/datetime-units-history.html 2021-05-10 20:58:26.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/datetime-units-history.html 2021-11-08 22:25:09.000000000 +0000
@@ -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
times according to the Gregorian calendar”.
@@ -73,4 +73,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/dblink.html postgresql-10-10.19/doc/src/sgml/html/dblink.html
--- postgresql-10-10.17/doc/src/sgml/html/dblink.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/dblink.html 2021-11-08 22:25:11.000000000 +0000
@@ -1,5 +1,5 @@
-F.11. 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
primary key field values with alternative supplied values
@@ -12,4 +12,4 @@
session.
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 -Nru postgresql-10-10.17/doc/src/sgml/html/ddl-alter.html postgresql-10-10.19/doc/src/sgml/html/ddl-alter.html
--- postgresql-10-10.17/doc/src/sgml/html/ddl-alter.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ddl-alter.html 2021-11-08 22:24:48.000000000 +0000
@@ -1,5 +1,5 @@
-5.5. 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
the table is already filled with data, or if the table is
@@ -101,4 +101,4 @@
ALTER TABLE products RENAME COLUMN product_no TO product_number;
5.5.8. Renaming a Table
To rename a table:
ALTER TABLE products RENAME TO items;
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/ddl-basics.html postgresql-10-10.19/doc/src/sgml/html/ddl-basics.html
--- postgresql-10-10.17/doc/src/sgml/html/ddl-basics.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ddl-basics.html 2021-11-08 22:24:48.000000000 +0000
@@ -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
variable — it reflects how much data is stored at a given moment.
@@ -82,4 +82,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/ddl-constraints.html postgresql-10-10.19/doc/src/sgml/html/ddl-constraints.html
--- postgresql-10-10.17/doc/src/sgml/html/ddl-constraints.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ddl-constraints.html 2021-11-08 22:24:48.000000000 +0000
@@ -1,5 +1,5 @@
-5.3. 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
price should probably only accept positive values. But there is no
@@ -442,4 +442,4 @@
TABLE ... CONSTRAINT ... EXCLUDE for details.
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 -Nru postgresql-10-10.17/doc/src/sgml/html/ddl-default.html postgresql-10-10.19/doc/src/sgml/html/ddl-default.html
--- postgresql-10-10.17/doc/src/sgml/html/ddl-default.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ddl-default.html 2021-11-08 22:24:48.000000000 +0000
@@ -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
data manipulation command can also request explicitly that a column
@@ -36,4 +36,4 @@
...
);
The SERIAL shorthand is discussed further in Section 8.1.4.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/ddl-depend.html postgresql-10-10.19/doc/src/sgml/html/ddl-depend.html
--- postgresql-10-10.17/doc/src/sgml/html/ddl-depend.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ddl-depend.html 2021-11-08 22:24:48.000000000 +0000
@@ -1,5 +1,5 @@
-5.13. 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.
For instance, a table with a foreign key constraint depends on the
@@ -68,4 +68,4 @@
there are also benefits. The function is still valid in some sense if the
table is missing, though executing it would cause an error; creating a new
table of the same name would allow the function to work again.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/ddl-foreign-data.html postgresql-10-10.19/doc/src/sgml/html/ddl-foreign-data.html
--- postgresql-10-10.17/doc/src/sgml/html/ddl-foreign-data.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ddl-foreign-data.html 2021-11-08 22:24:48.000000000 +0000
@@ -1,5 +1,5 @@
-5.11. 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
foreign data. (Note that this usage is not to be confused
@@ -33,4 +33,4 @@
CREATE USER MAPPING,
CREATE FOREIGN TABLE, and
IMPORT FOREIGN SCHEMA.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/ddl.html postgresql-10-10.19/doc/src/sgml/html/ddl.html
--- postgresql-10-10.17/doc/src/sgml/html/ddl.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ddl.html 2021-11-08 22:24:48.000000000 +0000
@@ -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
explaining how tables are created and modified and what features are
@@ -9,4 +9,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 -Nru postgresql-10-10.17/doc/src/sgml/html/ddl-inherit.html postgresql-10-10.19/doc/src/sgml/html/ddl-inherit.html
--- postgresql-10-10.17/doc/src/sgml/html/ddl-inherit.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ddl-inherit.html 2021-11-08 22:24:48.000000000 +0000
@@ -1,5 +1,5 @@
-5.9. 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
respects from the features described here.)
@@ -247,4 +247,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/ddl-others.html postgresql-10-10.19/doc/src/sgml/html/ddl-others.html
--- postgresql-10-10.17/doc/src/sgml/html/ddl-others.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ddl-others.html 2021-11-08 22:24:48.000000000 +0000
@@ -1,5 +1,5 @@
-5.12. 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
created to make the use and management of the data more efficient
@@ -11,4 +11,4 @@
Triggers and rewrite rules
Detailed information on
these topics appears in Part V.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/ddl-partitioning.html postgresql-10-10.19/doc/src/sgml/html/ddl-partitioning.html
--- postgresql-10-10.17/doc/src/sgml/html/ddl-partitioning.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ddl-partitioning.html 2021-11-08 22:24:48.000000000 +0000
@@ -1,5 +1,5 @@
-5.10. Table Partitioning
PostgreSQL supports basic table
partitioning. This section describes why and how to implement
partitioning as part of your database design.
5.10.1. Overview
Partitioning refers to splitting what is logically one large table into
@@ -79,7 +79,8 @@
That means partitioned tables and partitions do not participate in
inheritance with regular tables. Since a partition hierarchy consisting
of the partitioned table and its partitions is still an inheritance
- hierarchy, all the normal rules of inheritance apply as described in
+ hierarchy, tableoid and all the normal rules
+ of inheritance apply as described in
Section 5.9 with some exceptions, most notably:
Both CHECK and NOT NULL
@@ -698,4 +699,4 @@
painfully slow. Simulations of the intended workload are often beneficial
for optimizing the partitioning strategy. Never assume that more
partitions are better than fewer partitions and vice-versa.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/ddl-priv.html postgresql-10-10.19/doc/src/sgml/html/ddl-priv.html
--- postgresql-10-10.17/doc/src/sgml/html/ddl-priv.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ddl-priv.html 2021-11-08 22:24:48.000000000 +0000
@@ -1,5 +1,5 @@
-5.6. 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
(or a superuser) can do anything with the object. To allow
@@ -53,4 +53,4 @@
recipient (directly or through a chain of grants) will lose the
privilege. For details see the GRANT and
REVOKE reference pages.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/ddl-rowsecurity.html postgresql-10-10.19/doc/src/sgml/html/ddl-rowsecurity.html
--- postgresql-10-10.17/doc/src/sgml/html/ddl-rowsecurity.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ddl-rowsecurity.html 2021-11-08 22:24:48.000000000 +0000
@@ -1,5 +1,5 @@
-5.7. Row Security Policies
In addition to the SQL-standard privilege
system available through GRANT,
tables can have row security policies that restrict,
on a per-user basis, which rows can be returned by normal queries
@@ -338,4 +338,4 @@
situation.
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
can only access data in a single database, the one specified in the
@@ -246,4 +246,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/ddl-system-columns.html postgresql-10-10.19/doc/src/sgml/html/ddl-system-columns.html
--- postgresql-10-10.17/doc/src/sgml/html/ddl-system-columns.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ddl-system-columns.html 2021-11-08 22:24:48.000000000 +0000
@@ -1,5 +1,5 @@
-5.4. 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
restrictions are separate from whether the name is a key word or
@@ -76,4 +76,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 -Nru postgresql-10-10.17/doc/src/sgml/html/default-roles.html postgresql-10-10.19/doc/src/sgml/html/default-roles.html
--- postgresql-10-10.17/doc/src/sgml/html/default-roles.html 2021-05-10 20:58:11.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/default-roles.html 2021-11-08 22:24:53.000000000 +0000
@@ -1,5 +1,5 @@
-21.5. Default Roles
PostgreSQL provides a set of default roles
which provide access to certain, commonly needed, privileged capabilities
and information. Administrators can GRANT these roles to users and/or
other roles in their environment, providing those users with access to
@@ -32,4 +32,4 @@
GRANT command, for example:
GRANT pg_signal_backend TO admin_user;
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/dict-int.html postgresql-10-10.19/doc/src/sgml/html/dict-int.html
--- postgresql-10-10.17/doc/src/sgml/html/dict-int.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/dict-int.html 2021-11-08 22:25:11.000000000 +0000
@@ -1,5 +1,5 @@
-F.12. 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
numbers to be indexed while preventing excessive growth in the number of
@@ -37,4 +37,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 -Nru postgresql-10-10.17/doc/src/sgml/html/dict-xsyn.html postgresql-10-10.19/doc/src/sgml/html/dict-xsyn.html
--- postgresql-10-10.17/doc/src/sgml/html/dict-xsyn.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/dict-xsyn.html 2021-11-08 22:25:11.000000000 +0000
@@ -1,5 +1,5 @@
-F.13. 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
search for a word using any of its synonyms.
@@ -73,4 +73,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 -Nru postgresql-10-10.17/doc/src/sgml/html/different-replication-solutions.html postgresql-10-10.19/doc/src/sgml/html/different-replication-solutions.html
--- postgresql-10-10.17/doc/src/sgml/html/different-replication-solutions.html 2021-05-10 20:58:11.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/different-replication-solutions.html 2021-11-08 22:24:54.000000000 +0000
@@ -1,5 +1,5 @@
-26.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
is able to mount and start the database as though it were recovering from
@@ -117,4 +117,4 @@
part of the query and return results to a central server where they
are combined and returned to the user. This can be implemented using the
PL/Proxy tool set.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/disk-full.html postgresql-10-10.19/doc/src/sgml/html/disk-full.html
--- postgresql-10-10.17/doc/src/sgml/html/disk-full.html 2021-05-10 20:58:12.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/disk-full.html 2021-11-08 22:24:55.000000000 +0000
@@ -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
from occurring. If the disk holding the WAL files grows full, database
@@ -13,4 +13,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 -Nru postgresql-10-10.17/doc/src/sgml/html/disk-usage.html postgresql-10-10.19/doc/src/sgml/html/disk-usage.html
--- postgresql-10-10.17/doc/src/sgml/html/disk-usage.html 2021-05-10 20:58:12.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/disk-usage.html 2021-11-08 22:24:55.000000000 +0000
@@ -1,14 +1,14 @@
-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,
which is used to store values too wide to fit comfortably in the main
- table (see Section 66.2). There will be one valid index
+ table (see Section 67.2). There will be one valid index
on the TOAST table, if present. There also might be indexes
associated with the base table. Each table and index is stored in a
separate disk file — possibly more than one file, if the file would
exceed one gigabyte. Naming conventions for these files are described
- in Section 66.1.
+ in Section 67.1.
You can monitor disk space in three ways:
using the SQL functions listed in Table 9.84,
using the oid2name module, or
@@ -66,4 +66,4 @@
----------------------+----------
bigtable | 3290
customer | 3144
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/diskusage.html postgresql-10-10.19/doc/src/sgml/html/diskusage.html
--- postgresql-10-10.17/doc/src/sgml/html/diskusage.html 2021-05-10 20:58:12.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/diskusage.html 2021-11-08 22:24:55.000000000 +0000
@@ -1,4 +1,4 @@
-Chapter 29. Monitoring Disk Usage
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
rows, you can only remove entire rows from a table. In the
@@ -18,4 +18,4 @@
If you simply write:
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 -Nru postgresql-10-10.17/doc/src/sgml/html/dml.html postgresql-10-10.19/doc/src/sgml/html/dml.html
--- postgresql-10-10.17/doc/src/sgml/html/dml.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/dml.html 2021-11-08 22:24:48.000000000 +0000
@@ -1,8 +1,8 @@
-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 -Nru postgresql-10-10.17/doc/src/sgml/html/dml-insert.html postgresql-10-10.19/doc/src/sgml/html/dml-insert.html
--- postgresql-10-10.17/doc/src/sgml/html/dml-insert.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/dml-insert.html 2021-11-08 22:24:48.000000000 +0000
@@ -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
conceptually inserted one row at a time. Of course you can also
insert more than one row, but there is no way to insert less than
@@ -56,4 +56,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/dml-returning.html postgresql-10-10.19/doc/src/sgml/html/dml-returning.html
--- postgresql-10-10.17/doc/src/sgml/html/dml-returning.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/dml-returning.html 2021-11-08 22:24:48.000000000 +0000
@@ -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
optional RETURNING clause that supports this. Use
@@ -38,4 +38,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/dml-update.html postgresql-10-10.19/doc/src/sgml/html/dml-update.html
--- postgresql-10-10.17/doc/src/sgml/html/dml-update.html 2021-05-10 20:58:06.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/dml-update.html 2021-11-08 22:24:48.000000000 +0000
@@ -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
updated separately; the other columns are not affected.
@@ -46,4 +46,4 @@
UPDATE command by listing more than one
assignment in the SET clause. For example:
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 -Nru postgresql-10-10.17/doc/src/sgml/html/docguide-authoring.html postgresql-10-10.19/doc/src/sgml/html/docguide-authoring.html
--- postgresql-10-10.17/doc/src/sgml/html/docguide-authoring.html 2021-05-10 20:58:29.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/docguide-authoring.html 2021-11-08 22:25:12.000000000 +0000
@@ -1,5 +1,5 @@
-J.4. Documentation Authoring
SGML and DocBook do
not suffer from an oversupply of open-source authoring tools. The
most common tool set is the
Emacs/XEmacs
@@ -73,4 +73,4 @@
major mode
specifically for DocBook which also has font-lock and a number of features to
reduce typing.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/docguide-build.html postgresql-10-10.19/doc/src/sgml/html/docguide-build.html
--- postgresql-10-10.17/doc/src/sgml/html/docguide-build.html 2021-05-10 20:58:29.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/docguide-build.html 2021-11-08 22:25:12.000000000 +0000
@@ -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
documentation. (Remember to use GNU make.)
@@ -58,4 +58,4 @@
method to just check the correct syntax of the documentation
files, which only takes a few seconds:
doc/src/sgml$ make check
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/docguide-docbook.html postgresql-10-10.19/doc/src/sgml/html/docguide-docbook.html
--- postgresql-10-10.17/doc/src/sgml/html/docguide-docbook.html 2021-05-10 20:58:29.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/docguide-docbook.html 2021-11-08 22:25:12.000000000 +0000
@@ -1,5 +1,5 @@
-J.1. DocBook
The documentation sources are written in
DocBook, which is a markup language
superficially similar to HTML. Both of these
languages are applications of the Standard Generalized
@@ -21,4 +21,4 @@
The 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 -Nru postgresql-10-10.17/doc/src/sgml/html/docguide.html postgresql-10-10.19/doc/src/sgml/html/docguide.html
--- postgresql-10-10.17/doc/src/sgml/html/docguide.html 2021-05-10 20:58:29.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/docguide.html 2021-11-08 22:25:12.000000000 +0000
@@ -1,5 +1,5 @@
-Appendix J. Documentation
PostgreSQL has four primary documentation
formats:
Plain text, for pre-installation information
@@ -15,4 +15,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 -Nru postgresql-10-10.17/doc/src/sgml/html/docguide-style.html postgresql-10-10.19/doc/src/sgml/html/docguide-style.html
--- postgresql-10-10.17/doc/src/sgml/html/docguide-style.html 2021-05-10 20:58:29.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/docguide-style.html 2021-11-08 22:25:12.000000000 +0000
@@ -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.
Consistency is not only desired among
@@ -69,4 +69,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 -Nru postgresql-10-10.17/doc/src/sgml/html/docguide-toolsets.html postgresql-10-10.19/doc/src/sgml/html/docguide-toolsets.html
--- postgresql-10-10.17/doc/src/sgml/html/docguide-toolsets.html 2021-05-10 20:58:29.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/docguide-toolsets.html 2021-11-08 22:25:12.000000000 +0000
@@ -1,5 +1,5 @@
-J.2. Tool Sets
This is the definition of DocBook itself. We currently use version
@@ -125,4 +125,4 @@
the DocBook DTD kit in a place where OpenSP can find it, or you have
not set up the catalog files correctly. See the installation hints
above.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/dynamic-trace.html postgresql-10-10.19/doc/src/sgml/html/dynamic-trace.html
--- postgresql-10-10.17/doc/src/sgml/html/dynamic-trace.html 2021-05-10 20:58:12.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/dynamic-trace.html 2021-11-08 22:24:54.000000000 +0000
@@ -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
execution.
@@ -263,4 +263,4 @@
Each trace macro has a corresponding ENABLED macro.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/earthdistance.html postgresql-10-10.19/doc/src/sgml/html/earthdistance.html
--- postgresql-10-10.17/doc/src/sgml/html/earthdistance.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/earthdistance.html 2021-11-08 22:25:11.000000000 +0000
@@ -1,5 +1,5 @@
-F.14. 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.
The second one is based on the built-in point data type,
@@ -77,4 +77,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 -Nru postgresql-10-10.17/doc/src/sgml/html/ecpg-commands.html postgresql-10-10.19/doc/src/sgml/html/ecpg-commands.html
--- postgresql-10-10.17/doc/src/sgml/html/ecpg-commands.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ecpg-commands.html 2021-11-08 22:24:55.000000000 +0000
@@ -1,5 +1,5 @@
-35.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.
35.3.1. Executing SQL Statements
Creating a table:
EXEC SQL CREATE TABLE foo (number integer, ascii char(16));
@@ -112,4 +112,4 @@
see PREPARE. Also
see Section 35.5 for more details about using
placeholders and input parameters.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/ecpg-concept.html postgresql-10-10.19/doc/src/sgml/html/ecpg-concept.html
--- postgresql-10-10.17/doc/src/sgml/html/ecpg-concept.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ecpg-concept.html 2021-11-08 22:24:55.000000000 +0000
@@ -1,5 +1,5 @@
-35.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)
is first passed through the embedded SQL preprocessor, which converts it
@@ -34,4 +34,4 @@
C-style comments that are part of the SQL standard. The C part of the
program, however, follows the C standard of not accepting nested comments.
The following sections explain all the embedded SQL statements.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/ecpg-connect.html postgresql-10-10.19/doc/src/sgml/html/ecpg-connect.html
--- postgresql-10-10.17/doc/src/sgml/html/ecpg-connect.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ecpg-connect.html 2021-11-08 22:24:55.000000000 +0000
@@ -1,5 +1,5 @@
-35.2. Managing Database Connections
ECPG has some limited support for C++ applications. This section
describes some caveats.
The ecpg preprocessor takes an input file
written in C (or something like C) and embedded SQL commands,
@@ -192,4 +192,4 @@
and test_mod.o, into one executable, using the C++
compiler driver:
c++ test_cpp.o test_mod.o -lecpg -o test_cpp
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/ecpg-descriptors.html postgresql-10-10.19/doc/src/sgml/html/ecpg-descriptors.html
--- postgresql-10-10.17/doc/src/sgml/html/ecpg-descriptors.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ecpg-descriptors.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-35.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
the data of one row of data together with metadata items into one
@@ -568,4 +568,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
+tup_deleted = 0 (type: 9)
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/ecpg-develop.html postgresql-10-10.19/doc/src/sgml/html/ecpg-develop.html
--- postgresql-10-10.17/doc/src/sgml/html/ecpg-develop.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ecpg-develop.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-35.16. Internals
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
or provided by an external source. In these cases you cannot embed
@@ -83,4 +83,4 @@
EXEC SQL COMMIT;
EXEC SQL DISCONNECT ALL;
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/ecpg-errors.html postgresql-10-10.19/doc/src/sgml/html/ecpg-errors.html
--- postgresql-10-10.17/doc/src/sgml/html/ecpg-errors.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ecpg-errors.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-35.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.
@@ -344,4 +344,4 @@
-604 (ECPG_WARNING_NO_TRANSACTION)
There is no active (in-progress) transaction. (SQLSTATE 25P01)
-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 -Nru postgresql-10-10.17/doc/src/sgml/html/ecpg.html postgresql-10-10.19/doc/src/sgml/html/ecpg.html
--- postgresql-10-10.17/doc/src/sgml/html/ecpg.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ecpg.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 35. 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
(<meskes@postgresql.org>). Originally it was written to work with
@@ -8,4 +8,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 -Nru postgresql-10-10.17/doc/src/sgml/html/ecpg-informix-compat.html postgresql-10-10.19/doc/src/sgml/html/ecpg-informix-compat.html
--- postgresql-10-10.17/doc/src/sgml/html/ecpg-informix-compat.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ecpg-informix-compat.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-35.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
the dollar sign instead of the EXEC SQL primitive to introduce
@@ -304,7 +304,7 @@
Note that the ECPG implementation differs from the Informix
implementation. Informix limits an integer to the range from -32767 to
32767, while the limits in the ECPG implementation depend on the
- architecture (-INT_MAX .. INT_MAX).
+ architecture (INT_MIN .. INT_MAX).
dectolong
Convert a variable to type decimal to a long integer.
int dectolong(decimal *np, long *lngp);
The function receives a pointer to the decimal value to convert
@@ -629,4 +629,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/ecpg-library.html postgresql-10-10.19/doc/src/sgml/html/ecpg-library.html
--- postgresql-10-10.17/doc/src/sgml/html/ecpg-library.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ecpg-library.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-35.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
are some functions that can usefully be called directly. Note that
@@ -36,4 +36,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 -Nru postgresql-10-10.17/doc/src/sgml/html/ecpg-lo.html postgresql-10-10.19/doc/src/sgml/html/ecpg-lo.html
--- postgresql-10-10.17/doc/src/sgml/html/ecpg-lo.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ecpg-lo.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-35.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
object by calling the ECPGget_PGconn()
@@ -91,4 +91,4 @@
EXEC SQL COMMIT;
EXEC SQL DISCONNECT ALL;
return 0;
-}
\ No newline at end of file
+}
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/ecpg-pgtypes.html postgresql-10-10.19/doc/src/sgml/html/ecpg-pgtypes.html
--- postgresql-10-10.17/doc/src/sgml/html/ecpg-pgtypes.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ecpg-pgtypes.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-35.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
the help of the PostgreSQL server. See the
@@ -525,4 +525,4 @@
errno != 0 after each call to
PGTYPEStimestamp_from_asc.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/ecpg-preproc.html postgresql-10-10.19/doc/src/sgml/html/ecpg-preproc.html
--- postgresql-10-10.17/doc/src/sgml/html/ecpg-preproc.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ecpg-preproc.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-35.9. Preprocessor Directives
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
C preprocessor, which converts the
@@ -49,4 +49,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/ecpg-sql-allocate-descriptor.html postgresql-10-10.19/doc/src/sgml/html/ecpg-sql-allocate-descriptor.html
--- postgresql-10-10.17/doc/src/sgml/html/ecpg-sql-allocate-descriptor.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ecpg-sql-allocate-descriptor.html 2021-11-08 22:24:56.000000000 +0000
@@ -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 -Nru postgresql-10-10.17/doc/src/sgml/html/ecpg-sql-connect.html postgresql-10-10.19/doc/src/sgml/html/ecpg-sql-connect.html
--- postgresql-10-10.17/doc/src/sgml/html/ecpg-sql-connect.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ecpg-sql-connect.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-CONNECT
DECLARE cursor_name [ BINARY ] [ INSENSITIVE ] [ [ NO ] SCROLL ] CURSOR [ { WITH | WITHOUT } HOLD ] FOR prepared_name
DECLARE cursor_name [ BINARY ] [ INSENSITIVE ] [ [ NO ] SCROLL ] CURSOR [ { WITH | WITHOUT } HOLD ] FOR query
Description
DECLARE declares a cursor for iterating over
the result set of a prepared statement. This command has
slightly different semantics from the direct SQL
@@ -26,4 +26,4 @@
EXEC SQL PREPARE stmt1 AS SELECT version();
EXEC SQL DECLARE cur1 CURSOR FOR stmt1;
DESCRIBE — obtain information about a prepared statement or result set
Synopsis
DESCRIBE [ OUTPUT ] prepared_name USING [ SQL ] DESCRIPTOR descriptor_name
DESCRIBE [ OUTPUT ] prepared_name INTO [ SQL ] DESCRIPTOR descriptor_name
DESCRIBE [ OUTPUT ] prepared_name INTO sqlda_name
Description
DESCRIBE retrieves metadata information about
the result columns contained in a prepared statement, without
@@ -14,4 +14,4 @@
EXEC SQL DESCRIBE stmt1 INTO SQL DESCRIPTOR mydesc;
EXEC SQL GET DESCRIPTOR mydesc VALUE 1 :charvar = NAME;
EXEC SQL DEALLOCATE DESCRIPTOR mydesc;
GET DESCRIPTOR — get information from an SQL descriptor area
Synopsis
GET DESCRIPTOR descriptor_name:cvariable = descriptor_header_item [, ... ]
GET DESCRIPTOR descriptor_name VALUE column_number:cvariable = descriptor_item [, ... ]
Description
GET DESCRIPTOR retrieves information about a
query result set from an SQL descriptor area and stores it into
host variables. A descriptor area is typically populated
@@ -77,4 +77,4 @@
d_returned_octet_length = 6
d_data = testdb
Compatibility
GET DESCRIPTOR is specified in the SQL standard.
-
OPEN cursor_name
OPEN cursor_name USING value [, ... ]
OPEN cursor_name USING SQL DESCRIPTOR descriptor_name
Description
OPEN opens a cursor and optionally binds
actual values to the placeholders in the cursor's declaration.
@@ -19,4 +19,4 @@
EXEC SQL OPEN d USING 1, 'test';
EXEC SQL OPEN c1 USING SQL DESCRIPTOR mydesc;
EXEC SQL OPEN :curname1;
PREPARE prepares a statement dynamically
specified as a string for execution. This is different from the
direct SQL statement PREPARE, which can also
be used in embedded programs. The EXECUTE
@@ -14,4 +14,4 @@
EXEC SQL PREPARE foo FROM :stmt;
EXEC SQL EXECUTE foo USING SQL DESCRIPTOR indesc INTO SQL DESCRIPTOR outdesc;
SET AUTOCOMMIT — set the autocommit behavior of the current session
Synopsis
SET AUTOCOMMIT { = | TO } { ON | OFF }
Description
SET AUTOCOMMIT sets the autocommit behavior of
the current database session. By default, embedded SQL programs
are not in autocommit mode,
so COMMIT needs to be issued explicitly when
desired. This command can change the session to autocommit mode,
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 -Nru postgresql-10-10.17/doc/src/sgml/html/ecpg-sql-set-connection.html postgresql-10-10.19/doc/src/sgml/html/ecpg-sql-set-connection.html
--- postgresql-10-10.17/doc/src/sgml/html/ecpg-sql-set-connection.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/ecpg-sql-set-connection.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-SET CONNECTION
SET DESCRIPTOR — set information in an SQL descriptor area
Synopsis
SET DESCRIPTOR descriptor_namedescriptor_header_item = value [, ... ]
SET DESCRIPTOR descriptor_name VALUE numberdescriptor_item = value [, ...]
Description
SET DESCRIPTOR populates an SQL descriptor
area with values. The descriptor area is then typically used to
bind parameters in a prepared query execution.
@@ -23,4 +23,4 @@
EXEC SQL SET DESCRIPTOR indesc VALUE 1 DATA = :val1;
EXEC SQL SET DESCRIPTOR indesc VALUE 2 INDICATOR = :val1, DATA = 'some string';
EXEC SQL SET DESCRIPTOR indesc VALUE 2 INDICATOR = :val2null, DATA = :val2;
Compatibility
SET DESCRIPTOR is specified in the SQL standard.
-
In Section 35.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
user-supplied values into statements or have the program process
@@ -720,4 +720,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/encryption-options.html postgresql-10-10.19/doc/src/sgml/html/encryption-options.html
--- postgresql-10-10.17/doc/src/sgml/html/encryption-options.html 2021-05-10 20:58:10.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/encryption-options.html 2021-11-08 22:24:53.000000000 +0000
@@ -1,5 +1,5 @@
-18.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
insecure networks. Encryption might also be required to secure
@@ -60,4 +60,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 -Nru postgresql-10-10.17/doc/src/sgml/html/errcodes-appendix.html postgresql-10-10.19/doc/src/sgml/html/errcodes-appendix.html
--- postgresql-10-10.17/doc/src/sgml/html/errcodes-appendix.html 2021-05-10 20:58:26.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/errcodes-appendix.html 2021-11-08 22:25:08.000000000 +0000
@@ -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
that need to know which error condition has occurred should usually
@@ -17,7 +17,7 @@
does not recognize the specific error code might still be able to infer
what to do from the error class.
Table A.1 lists all the error codes defined in
- PostgreSQL 10.17. (Some are not actually
+ PostgreSQL 10.19. (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
@@ -37,4 +37,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
Class 57 — Operator Intervention
57000
operator_intervention
57014
query_canceled
57P01
admin_shutdown
57P02
crash_shutdown
57P03
cannot_connect_now
57P04
database_dropped
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 -Nru postgresql-10-10.17/doc/src/sgml/html/error-message-reporting.html postgresql-10-10.19/doc/src/sgml/html/error-message-reporting.html
--- postgresql-10-10.17/doc/src/sgml/html/error-message-reporting.html 2021-05-10 20:58:24.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/error-message-reporting.html 2021-11-08 22:25:07.000000000 +0000
@@ -1,5 +1,5 @@
-53.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
require some explanation.
@@ -191,4 +191,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/error-style-guide.html postgresql-10-10.19/doc/src/sgml/html/error-style-guide.html
--- postgresql-10-10.17/doc/src/sgml/html/error-style-guide.html 2021-05-10 20:58:24.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/error-style-guide.html 2021-11-08 22:25:07.000000000 +0000
@@ -1,5 +1,5 @@
-53.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.
What Goes Where
The primary message should be short, factual, and avoid reference to
@@ -164,6 +164,10 @@
translation.
Contractions. Avoid contractions, like “can't”; use
“cannot” instead.
+
Non-negative. Avoid “non-negative” as it is ambiguous
+ about whether it accepts zero. It's better to use
+ “greater than zero” or
+ “greater than or equal to zero”.
Proper Spelling
Spell out words in full. For instance, avoid:
spec
stats
@@ -175,4 +179,4 @@
Localization
Keep in mind that error message texts need to be translated into other
languages. Follow the guidelines in Section 54.2.2
to avoid making life difficult for translators.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/event-log-registration.html postgresql-10-10.19/doc/src/sgml/html/event-log-registration.html
--- postgresql-10-10.17/doc/src/sgml/html/event-log-registration.html 2021-05-10 20:58:10.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/event-log-registration.html 2021-11-08 22:24:53.000000000 +0000
@@ -1,5 +1,5 @@
-18.11. Registering Event Log on Windows
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
ddl_command_start,
@@ -65,4 +65,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 -Nru postgresql-10-10.17/doc/src/sgml/html/event-trigger-example.html postgresql-10-10.19/doc/src/sgml/html/event-trigger-example.html
--- postgresql-10-10.17/doc/src/sgml/html/event-trigger-example.html 2021-05-10 20:58:15.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/event-trigger-example.html 2021-11-08 22:24:57.000000000 +0000
@@ -1,5 +1,5 @@
-39.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.)
The function noddl raises an exception each time it is called.
@@ -60,4 +60,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 -Nru postgresql-10-10.17/doc/src/sgml/html/event-trigger-interface.html postgresql-10-10.19/doc/src/sgml/html/event-trigger-interface.html
--- postgresql-10-10.17/doc/src/sgml/html/event-trigger-interface.html 2021-05-10 20:58:15.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/event-trigger-interface.html 2021-11-08 22:24:57.000000000 +0000
@@ -1,5 +1,5 @@
-39.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
then these details are handled for you. In most cases you should
@@ -50,4 +50,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/event-trigger-matrix.html postgresql-10-10.19/doc/src/sgml/html/event-trigger-matrix.html
--- postgresql-10-10.17/doc/src/sgml/html/event-trigger-matrix.html 2021-05-10 20:58:15.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/event-trigger-matrix.html 2021-11-08 22:24:57.000000000 +0000
@@ -1,4 +1,4 @@
-39.2. Event Trigger Firing Matrix
To supplement the trigger mechanism discussed in Chapter 38,
PostgreSQL also provides event triggers. Unlike regular
triggers, which are attached to a single table and capture only DML events,
event triggers are global to a particular database and are capable of
@@ -7,4 +7,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 -Nru postgresql-10-10.17/doc/src/sgml/html/event-trigger-table-rewrite-example.html postgresql-10-10.19/doc/src/sgml/html/event-trigger-table-rewrite-example.html
--- postgresql-10-10.17/doc/src/sgml/html/event-trigger-table-rewrite-example.html 2021-05-10 20:58:15.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/event-trigger-table-rewrite-example.html 2021-11-08 22:24:57.000000000 +0000
@@ -1,5 +1,5 @@
-39.5. A Table Rewrite Event Trigger Example
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.
Each time a plan node is called, it must deliver one more row, or
@@ -60,4 +60,4 @@
trivial plan tree consisting of a single Result
node, which computes just one result row, feeding that up
toModifyTable to perform the insertion.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/explicit-joins.html postgresql-10-10.19/doc/src/sgml/html/explicit-joins.html
--- postgresql-10-10.17/doc/src/sgml/html/explicit-joins.html 2021-05-10 20:58:09.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/explicit-joins.html 2021-11-08 22:24:52.000000000 +0000
@@ -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.
In a simple join query, such as:
@@ -116,4 +116,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/explicit-locking.html postgresql-10-10.19/doc/src/sgml/html/explicit-locking.html
--- postgresql-10-10.17/doc/src/sgml/html/explicit-locking.html 2021-05-10 20:58:09.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/explicit-locking.html 2021-11-08 22:24:52.000000000 +0000
@@ -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
MVCC does not give the desired behavior. Also,
@@ -331,4 +331,4 @@
pg_locks.
The functions provided to manipulate advisory locks are described in
Section 9.26.10.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/extend-extensions.html postgresql-10-10.19/doc/src/sgml/html/extend-extensions.html
--- postgresql-10-10.17/doc/src/sgml/html/extend-extensions.html 2021-05-10 20:58:15.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/extend-extensions.html 2021-11-08 22:24:57.000000000 +0000
@@ -1,5 +1,5 @@
-37.15. Packaging Related Objects into an Extension
37.15. 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.
It is helpful to collect all these objects into a single package
@@ -531,4 +531,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/extend-how.html postgresql-10-10.19/doc/src/sgml/html/extend-how.html
--- postgresql-10-10.17/doc/src/sgml/html/extend-how.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/extend-how.html 2021-11-08 22:24:57.000000000 +0000
@@ -1,5 +1,5 @@
-37.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
about databases, tables, columns, etc., in what are
@@ -28,4 +28,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 -Nru postgresql-10-10.17/doc/src/sgml/html/extend.html postgresql-10-10.19/doc/src/sgml/html/extend.html
--- postgresql-10-10.17/doc/src/sgml/html/extend.html 2021-05-10 20:58:15.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/extend.html 2021-11-08 22:24:57.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 37. Extending SQL
In the sections that follow, we will discuss how you
can extend the PostgreSQL
SQL query language by adding:
@@ -10,4 +10,4 @@
operator classes for indexes (starting in Section 37.14)
packages of related objects (starting in Section 37.15)
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/extend-pgxs.html postgresql-10-10.19/doc/src/sgml/html/extend-pgxs.html
--- postgresql-10-10.17/doc/src/sgml/html/extend-pgxs.html 2021-05-10 20:58:15.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/extend-pgxs.html 2021-11-08 22:24:57.000000000 +0000
@@ -1,5 +1,5 @@
-37.16. 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
the PostgreSQL installation provides a build
@@ -131,4 +131,4 @@
the actual result files found in the results/
directory, 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 -Nru postgresql-10-10.17/doc/src/sgml/html/extend-type-system.html postgresql-10-10.19/doc/src/sgml/html/extend-type-system.html
--- postgresql-10-10.17/doc/src/sgml/html/extend-type-system.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/extend-type-system.html 2021-11-08 22:24:57.000000000 +0000
@@ -1,5 +1,5 @@
-37.2. The PostgreSQL Type System
PostgreSQL data types are divided into base
types, composite types, domains, and pseudo-types.
37.2.1. Base Types
Base types are those, like int4, that are
implemented below the level of the SQL language
@@ -105,4 +105,4 @@
matching and determining the actual result type, such a function behaves
the same as if you had written the appropriate number of
anynonarray parameters.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/external-admin-tools.html postgresql-10-10.19/doc/src/sgml/html/external-admin-tools.html
--- postgresql-10-10.17/doc/src/sgml/html/external-admin-tools.html 2021-05-10 20:58:29.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/external-admin-tools.html 2021-11-08 22:25:12.000000000 +0000
@@ -1,6 +1,6 @@
-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 -Nru postgresql-10-10.17/doc/src/sgml/html/external-extensions.html postgresql-10-10.19/doc/src/sgml/html/external-extensions.html
--- postgresql-10-10.17/doc/src/sgml/html/external-extensions.html 2021-05-10 20:58:29.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/external-extensions.html 2021-11-08 22:25:12.000000000 +0000
@@ -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
contrib/ directory shipped with the source code
@@ -10,4 +10,4 @@
externally. For example, Slony-I is a popular
master/standby replication solution that is developed independently
from the core project.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/external-interfaces.html postgresql-10-10.19/doc/src/sgml/html/external-interfaces.html
--- postgresql-10-10.17/doc/src/sgml/html/external-interfaces.html 2021-05-10 20:58:29.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/external-interfaces.html 2021-11-08 22:25:12.000000000 +0000
@@ -1,5 +1,5 @@
-H.1. Client Interfaces
There are only two client interfaces included in the base
PostgreSQL distribution:
libpq is included because it is the
primary C language interface, and because many other client interfaces
@@ -15,4 +15,4 @@
released under the same license as PostgreSQL. For more
information on each language interface, including licensing terms, refer to
its website and documentation.
-
In addition, there are a number of procedural languages that are developed
@@ -9,4 +9,4 @@
license as PostgreSQL. For more information on each
procedural language, including licensing information, refer to its website
and documentation.
-
Table H.2. Externally Maintained Procedural Languages
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 -Nru postgresql-10-10.17/doc/src/sgml/html/fdw-callbacks.html postgresql-10-10.19/doc/src/sgml/html/fdw-callbacks.html
--- postgresql-10-10.17/doc/src/sgml/html/fdw-callbacks.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/fdw-callbacks.html 2021-11-08 22:25:07.000000000 +0000
@@ -1,5 +1,5 @@
-56.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.
The FdwRoutine struct type is declared in
@@ -788,4 +788,4 @@
destroyed just after this callback is invoked, foreign data wrappers that
wish to take some action before the DSM segment goes away should implement
this method.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/fdw-functions.html postgresql-10-10.19/doc/src/sgml/html/fdw-functions.html
--- postgresql-10-10.17/doc/src/sgml/html/fdw-functions.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/fdw-functions.html 2021-11-08 22:25:07.000000000 +0000
@@ -1,5 +1,5 @@
-56.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.
For details on C language calling conventions and dynamic loading,
@@ -30,4 +30,4 @@
or ForeignTableRelationId).
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 -Nru postgresql-10-10.17/doc/src/sgml/html/fdwhandler.html postgresql-10-10.19/doc/src/sgml/html/fdwhandler.html
--- postgresql-10-10.17/doc/src/sgml/html/fdwhandler.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/fdwhandler.html 2021-11-08 22:25:07.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 56. 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
data from the remote data source and returning it to the
@@ -15,4 +15,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 -Nru postgresql-10-10.17/doc/src/sgml/html/fdw-helpers.html postgresql-10-10.19/doc/src/sgml/html/fdw-helpers.html
--- postgresql-10-10.17/doc/src/sgml/html/fdw-helpers.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/fdw-helpers.html 2021-11-08 22:25:07.000000000 +0000
@@ -1,5 +1,5 @@
-56.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.
To use any of these functions, you need to include the header file
@@ -58,4 +58,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/fdw-planning.html postgresql-10-10.19/doc/src/sgml/html/fdw-planning.html
--- postgresql-10-10.17/doc/src/sgml/html/fdw-planning.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/fdw-planning.html 2021-11-08 22:25:07.000000000 +0000
@@ -1,5 +1,5 @@
-56.4. Foreign Data Wrapper Query Planning
The FDW callback functions GetForeignRelSize,
GetForeignPaths, GetForeignPlan,
PlanForeignModify, GetForeignJoinPaths,
GetForeignUpperPaths, and PlanDirectModify
@@ -172,4 +172,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 -Nru postgresql-10-10.17/doc/src/sgml/html/fdw-row-locking.html postgresql-10-10.19/doc/src/sgml/html/fdw-row-locking.html
--- postgresql-10-10.17/doc/src/sgml/html/fdw-row-locking.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/fdw-row-locking.html 2021-11-08 22:25:07.000000000 +0000
@@ -1,5 +1,5 @@
-56.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
close an approximation as practical to the semantics used in
@@ -82,4 +82,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 -Nru postgresql-10-10.17/doc/src/sgml/html/features.html postgresql-10-10.19/doc/src/sgml/html/features.html
--- postgresql-10-10.17/doc/src/sgml/html/features.html 2021-05-10 20:58:27.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/features.html 2021-11-08 22:25:10.000000000 +0000
@@ -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
@@ -65,4 +65,4 @@
Note
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 -Nru postgresql-10-10.17/doc/src/sgml/html/features-sql-standard.html postgresql-10-10.19/doc/src/sgml/html/features-sql-standard.html
--- postgresql-10-10.17/doc/src/sgml/html/features-sql-standard.html 2021-05-10 20:58:27.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/features-sql-standard.html 2021-11-08 22:25:10.000000000 +0000
@@ -1,3 +1,3 @@
-D.1. Supported Features
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
and read their output. The data file or program output must be in a format
@@ -108,4 +108,4 @@
OPTIONS ( filename '/home/josh/data/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 -Nru postgresql-10-10.17/doc/src/sgml/html/functions-admin.html postgresql-10-10.19/doc/src/sgml/html/functions-admin.html
--- postgresql-10-10.17/doc/src/sgml/html/functions-admin.html 2021-05-10 20:58:09.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions-admin.html 2021-11-08 22:24:51.000000000 +0000
@@ -1,5 +1,5 @@
-9.26. System Administration Functions
The functions described in this section are used to control and
monitor a PostgreSQL installation.
9.26.1. Configuration Settings Functions
Table 9.77 shows the functions
available to query and alter run-time configuration parameters.
@@ -507,9 +507,9 @@
'main' returns the size of the main
data fork of the relation.
'fsm' returns the size of the Free Space Map
- (see Section 66.3) associated with the relation.
+ (see Section 67.3) associated with the relation.
'vm' returns the size of the Visibility Map
- (see Section 66.4) associated with the relation.
+ (see Section 67.4) associated with the relation.
'init' returns the size of the initialization
fork, if any, associated with the relation.
@@ -546,7 +546,7 @@
pg_relation_filenode accepts the OID or name of a table,
index, sequence, or toast table, and returns the “filenode” number
currently assigned to it. The filenode is the base component of the file
- name(s) used for the relation (see Section 66.1
+ name(s) used for the relation (see Section 67.1
for more information). For most tables the result is the same as
pg_class.relfilenode, but for certain
system catalogs relfilenode is zero and this function must
@@ -586,6 +586,7 @@
be pg_catalog, but that is not a requirement;
the collations could be installed into some other schema as well.
The function returns the number of new collation objects it created.
+ Use of this function is restricted to superusers.
9.26.8. Index Maintenance Functions
Table 9.87 shows the functions
available for index maintenance tasks.
These functions cannot be executed during recovery.
@@ -744,4 +745,4 @@
pg_try_advisory_lock_shared, except the lock, if acquired,
is automatically released at the end of the current transaction and
cannot be released explicitly.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/functions-aggregate.html postgresql-10-10.19/doc/src/sgml/html/functions-aggregate.html
--- postgresql-10-10.17/doc/src/sgml/html/functions-aggregate.html 2021-05-10 20:58:08.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions-aggregate.html 2021-11-08 22:24:51.000000000 +0000
@@ -1,5 +1,5 @@
-9.20. 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.52
and statistical aggregates in Table 9.53.
@@ -386,4 +386,4 @@
Bar | | 1 | 20
| | 3 | 50
(7 rows)
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/functions-array.html postgresql-10-10.19/doc/src/sgml/html/functions-array.html
--- postgresql-10-10.17/doc/src/sgml/html/functions-array.html 2021-05-10 20:58:08.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions-array.html 2021-11-08 22:24:51.000000000 +0000
@@ -1,5 +1,5 @@
-9.18. Array Functions and Operators
Table 9.48 shows the operators
available for array types.
Table 9.48. Array Operators
Operator
Description
Example
Result
=
equal
ARRAY[1.1,2.1,3.1]::int[] = ARRAY[1,2,3]
t
<>
not equal
ARRAY[1,2,3] <> ARRAY[1,2,4]
t
<
less than
ARRAY[1,2,3] < ARRAY[1,2,4]
t
>
greater than
ARRAY[1,4,3] > ARRAY[1,2,4]
t
<=
less than or equal
ARRAY[1,2,3] <= ARRAY[1,2,3]
t
>=
greater than or equal
ARRAY[1,4,3] >= ARRAY[1,4,3]
t
@>
contains
ARRAY[1,4,3] @> ARRAY[3,1,3]
t
<@
is contained by
ARRAY[2,2,7] <@ ARRAY[1,7,4,2,6]
t
&&
overlap (have elements in common)
ARRAY[1,4,3] && ARRAY[2,1]
t
||
array-to-array concatenation
ARRAY[1,2,3] || ARRAY[4,5,6]
{1,2,3,4,5,6}
||
array-to-array concatenation
ARRAY[1,2,3] || ARRAY[[4,5,6],[7,8,9]]
{{1,2,3},{4,5,6},{7,8,9}}
||
element-to-array concatenation
3 || ARRAY[4,5,6]
{3,4,5,6}
||
array-to-element concatenation
ARRAY[4,5,6] || 7
{4,5,6,7}
The array ordering operators (<,
>=, etc) compare the array contents
@@ -102,4 +102,4 @@
than returning NULL as before.
See also Section 9.20 about the aggregate
function array_agg for use with arrays.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/functions-binarystring.html postgresql-10-10.19/doc/src/sgml/html/functions-binarystring.html
--- postgresql-10-10.17/doc/src/sgml/html/functions-binarystring.html 2021-05-10 20:58:07.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions-binarystring.html 2021-11-08 22:24:50.000000000 +0000
@@ -1,5 +1,5 @@
-9.5. Binary 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. Aside from the
usual comparison operators, the operators
@@ -35,4 +35,4 @@
Note
Casting an integer to bit(n) copies the rightmost
n bits. Casting an integer to a bit string width wider
than the integer itself will sign-extend on the left.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/functions-comparison.html postgresql-10-10.19/doc/src/sgml/html/functions-comparison.html
--- postgresql-10-10.17/doc/src/sgml/html/functions-comparison.html 2021-05-10 20:58:07.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions-comparison.html 2021-11-08 22:24:49.000000000 +0000
@@ -1,5 +1,5 @@
-9.2. Comparison Functions and Operators
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,
but do not involve subqueries.
@@ -169,4 +169,4 @@
materialized views and might be useful for other specialized purposes
such as replication but are not intended to be generally useful for
writing queries.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/functions-conditional.html postgresql-10-10.19/doc/src/sgml/html/functions-conditional.html
--- postgresql-10-10.17/doc/src/sgml/html/functions-conditional.html 2021-05-10 20:58:08.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions-conditional.html 2021-11-08 22:24:50.000000000 +0000
@@ -1,5 +1,5 @@
-9.17. Conditional Expressions
This section describes the SQL-compliant conditional expressions
available in PostgreSQL.
Tip
If your needs go beyond the capabilities of these conditional
expressions, you might want to consider writing a stored procedure
@@ -140,4 +140,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/functions-datetime.html postgresql-10-10.19/doc/src/sgml/html/functions-datetime.html
--- postgresql-10-10.17/doc/src/sgml/html/functions-datetime.html 2021-05-10 20:58:07.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions-datetime.html 2021-11-08 22:24:50.000000000 +0000
@@ -1,5 +1,5 @@
-9.9. Date/Time Functions and Operators
Table 9.30 shows the available
functions for date/time value processing, with details appearing in
the following subsections. Table 9.29 illustrates the behaviors of
the basic arithmetic operators (+,
@@ -564,4 +564,4 @@
other sessions might have to wait for your sleeping process, slowing down
the entire system.
[7] 60 if leap seconds are
- implemented by the operating system
\ No newline at end of file
+ implemented by the operating system
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/functions-enum.html postgresql-10-10.19/doc/src/sgml/html/functions-enum.html
--- postgresql-10-10.17/doc/src/sgml/html/functions-enum.html 2021-05-10 20:58:07.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions-enum.html 2021-11-08 22:24:50.000000000 +0000
@@ -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.
These are listed in Table 9.32. The examples
@@ -25,4 +25,4 @@
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 suggested by the examples.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/functions-event-triggers.html postgresql-10-10.19/doc/src/sgml/html/functions-event-triggers.html
--- postgresql-10-10.17/doc/src/sgml/html/functions-event-triggers.html 2021-05-10 20:58:09.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions-event-triggers.html 2021-11-08 22:24:51.000000000 +0000
@@ -1,5 +1,5 @@
-9.28. Event Trigger Functions
PostgreSQL provides these helper functions
to retrieve information from event triggers.
For more information about event triggers,
see Chapter 39.
@@ -93,4 +93,4 @@
CREATE EVENT TRIGGER test_table_rewrite_oid
ON table_rewrite
EXECUTE PROCEDURE test_event_trigger_table_rewrite_oid();
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/functions-formatting.html postgresql-10-10.19/doc/src/sgml/html/functions-formatting.html
--- postgresql-10-10.17/doc/src/sgml/html/functions-formatting.html 2021-05-10 20:58:07.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions-formatting.html 2021-11-08 22:24:50.000000000 +0000
@@ -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
and for converting from formatted strings to specific data types.
@@ -223,4 +223,4 @@
modifier patterns for numeric formatting.
Table 9.27. 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.28 shows some
examples of the use of the to_char function.
-
The geometric types point, box,
lseg, line, path,
polygon, and circle have a large set of
native support functions and operators, shown in Table 9.33, Table 9.34, and Table 9.35.
@@ -47,4 +47,4 @@
will work. If the concept of an intersecting versus
non-intersecting path is confusing, draw both of the
above paths side by side on a piece of graph paper.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/functions.html postgresql-10-10.19/doc/src/sgml/html/functions.html
--- postgresql-10-10.17/doc/src/sgml/html/functions.html 2021-05-10 20:58:09.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions.html 2021-11-08 22:24:51.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 9. Functions and Operators
PostgreSQL provides a large number of
functions and operators for the built-in data types. Users can also
define their own functions and operators, as described in
Part V. The
@@ -16,4 +16,4 @@
consistent between the various implementations. This chapter is also
not exhaustive; additional functions appear in relevant sections of
the manual.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/functions-info.html postgresql-10-10.19/doc/src/sgml/html/functions-info.html
--- postgresql-10-10.17/doc/src/sgml/html/functions-info.html 2021-05-10 20:58:08.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions-info.html 2021-11-08 22:24:51.000000000 +0000
@@ -1,5 +1,5 @@
-9.25. System Information Functions
Table 9.60 shows several
functions that extract session and system information.
In addition to the functions listed in this section, there are a number of
functions related to the statistics system that also provide system
@@ -692,4 +692,4 @@
Table 9.75
Table 9.75. pg_control_init 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
float4_pass_by_value
boolean
float8_pass_by_value
boolean
data_page_checksum_version
integer
pg_control_recovery returns a record, shown in
Table 9.76
-
Table 9.76. pg_control_recovery 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.76. pg_control_recovery 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 -Nru postgresql-10-10.17/doc/src/sgml/html/functions-json.html postgresql-10-10.19/doc/src/sgml/html/functions-json.html
--- postgresql-10-10.17/doc/src/sgml/html/functions-json.html 2021-05-10 20:58:08.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions-json.html 2021-11-08 22:24:50.000000000 +0000
@@ -1,5 +1,5 @@
-9.15. JSON Functions and Operators
Table 9.43 shows the operators that
are available for use with the two JSON data types (see Section 8.14).
Table 9.43. json and jsonb Operators
Operator
Right Operand Type
Description
Example
Example Result
->
int
Get JSON array element (indexed from zero, negative
integers count from the end)
'[{"a":"foo"},{"b":"bar"},{"c":"baz"}]'::json->2
{"c":"baz"}
->
text
Get JSON object field by key
'{"a": {"b":"foo"}}'::json->'a'
{"b":"foo"}
->>
int
Get JSON array element as text
'[1,2,3]'::json->>2
3
->>
text
Get JSON object field as text
'{"a":1,"b":2}'::json->>'b'
2
#>
text[]
Get JSON object at specified path
'{"a": {"b":{"c": "foo"}}}'::json#>'{a,b}'
{"c": "foo"}
#>>
text[]
Get JSON object at specified path as text
'{"a":[1,2,3],"b":[4,5,6]}'::json#>>'{a,2}'
3
Note
There are parallel variants of these operators for both the
@@ -317,4 +317,4 @@
json_object_agg which aggregates pairs of values
into a JSON object, and their jsonb equivalents,
jsonb_agg and jsonb_object_agg.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/functions-logical.html postgresql-10-10.19/doc/src/sgml/html/functions-logical.html
--- postgresql-10-10.17/doc/src/sgml/html/functions-logical.html 2021-05-10 20:58:07.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions-logical.html 2021-11-08 22:24:49.000000000 +0000
@@ -1,5 +1,5 @@
-9.1. Logical Operators
The usual logical operators are available:
@@ -26,4 +26,4 @@
commutative, that is, you can switch the left and right operand
without affecting the result. But 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 -Nru postgresql-10-10.17/doc/src/sgml/html/functions-matching.html postgresql-10-10.19/doc/src/sgml/html/functions-matching.html
--- postgresql-10-10.17/doc/src/sgml/html/functions-matching.html 2021-05-10 20:58:07.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions-matching.html 2021-11-08 22:24:50.000000000 +0000
@@ -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
more recent SIMILAR TO operator (added in
@@ -889,4 +889,4 @@
are synonyms for
[[:<:]] and [[:>:]]
respectively; no other escapes are available in BREs.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/functions-math.html postgresql-10-10.19/doc/src/sgml/html/functions-math.html
--- postgresql-10-10.17/doc/src/sgml/html/functions-math.html 2021-05-10 20:58:07.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions-math.html 2021-11-08 22:24:49.000000000 +0000
@@ -1,5 +1,5 @@
-9.3. Mathematical Functions and Operators
Mathematical operators are provided for many
PostgreSQL types. For types without
standard mathematical conventions
(e.g., date/time types) we
@@ -134,4 +134,4 @@
However, using the degree-based trigonometric functions is preferred,
as that way avoids round-off error for special cases such
as sind(30).
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/functions-net.html postgresql-10-10.19/doc/src/sgml/html/functions-net.html
--- postgresql-10-10.17/doc/src/sgml/html/functions-net.html 2021-05-10 20:58:08.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions-net.html 2021-11-08 22:24:50.000000000 +0000
@@ -1,5 +1,5 @@
-9.12. Network Address Functions and Operators
Table 9.36 shows the operators
available for the cidr and inet types.
The operators <<,
<<=, >>,
@@ -77,4 +77,4 @@
operators (>, <=, etc.) for
ordering, and the bitwise arithmetic operators (~,
& and |) for NOT, AND and OR.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/functions-range.html postgresql-10-10.19/doc/src/sgml/html/functions-range.html
--- postgresql-10-10.17/doc/src/sgml/html/functions-range.html 2021-05-10 20:58:08.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions-range.html 2021-11-08 22:24:51.000000000 +0000
@@ -1,5 +1,5 @@
-9.19. Range Functions and Operators
The simple comparison operators <,
@@ -37,4 +37,4 @@
The lower_inc, upper_inc,
lower_inf, and upper_inf
functions all return false for an empty range.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/functions-sequence.html postgresql-10-10.19/doc/src/sgml/html/functions-sequence.html
--- postgresql-10-10.17/doc/src/sgml/html/functions-sequence.html 2021-05-10 20:58:08.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions-sequence.html 2021-11-08 22:24:50.000000000 +0000
@@ -1,5 +1,5 @@
-9.16. 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.
Sequence objects are commonly used to generate unique identifiers
@@ -121,4 +121,4 @@
This function requires UPDATE privilege on the
sequence.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/functions-srf.html postgresql-10-10.19/doc/src/sgml/html/functions-srf.html
--- postgresql-10-10.17/doc/src/sgml/html/functions-srf.html 2021-05-10 20:58:08.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions-srf.html 2021-11-08 22:24:51.000000000 +0000
@@ -1,5 +1,5 @@
-9.24. 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.58 and
Table 9.59. Other, more specialized
@@ -156,4 +156,4 @@
pg_stat_tmp | 18
pg_subtrans | 19
(19 rows)
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/functions-string.html postgresql-10-10.19/doc/src/sgml/html/functions-string.html
--- postgresql-10-10.17/doc/src/sgml/html/functions-string.html 2021-05-10 20:58:07.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions-string.html 2021-11-08 22:24:50.000000000 +0000
@@ -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,
and text. Unless otherwise noted, all
@@ -450,4 +450,4 @@
The %I and %L format specifiers are particularly
useful for safely constructing dynamic SQL statements. See
Example 42.1.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/functions-subquery.html postgresql-10-10.19/doc/src/sgml/html/functions-subquery.html
--- postgresql-10-10.17/doc/src/sgml/html/functions-subquery.html 2021-05-10 20:58:08.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions-subquery.html 2021-11-08 22:24:51.000000000 +0000
@@ -1,5 +1,5 @@
-9.22. Subquery Expressions
This section describes the SQL-compliant subquery
expressions available in PostgreSQL.
All of the expression forms documented in this section return
Boolean (true/false) results.
@@ -159,4 +159,4 @@
compared row-wise to the single subquery result row.
See Section 9.23.5 for details about the meaning
of a row constructor comparison.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/functions-textsearch.html postgresql-10-10.19/doc/src/sgml/html/functions-textsearch.html
--- postgresql-10-10.17/doc/src/sgml/html/functions-textsearch.html 2021-05-10 20:58:08.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions-textsearch.html 2021-11-08 22:24:50.000000000 +0000
@@ -1,5 +1,5 @@
-9.13. Text Search Functions and Operators
Table 9.40,
Table 9.41 and
Table 9.42
summarize the functions and operators that are provided
@@ -90,4 +90,4 @@
ts_token_type(parser_nametext, OUT tokidinteger, OUT aliastext, OUT descriptiontext)
setof record
get token types defined by parser
ts_token_type('default')
(1,asciiword,"Word, all ASCII") ...
ts_token_type(parser_oidoid, OUT tokidinteger, OUT aliastext, OUT descriptiontext)
setof record
get token types defined by parser
ts_token_type(3722)
(1,asciiword,"Word, all ASCII") ...
ts_stat(sqlquerytext, [weightstext, ] OUT wordtext, OUT ndocinteger, OUT nentryinteger)
-
setof record
get statistics of a tsvector column
ts_stat('SELECT vector from apod')
(foo,10,15) ...
\ No newline at end of file
+
setof record
get statistics of a tsvector column
ts_stat('SELECT vector from apod')
(foo,10,15) ...
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/functions-trigger.html postgresql-10-10.19/doc/src/sgml/html/functions-trigger.html
--- postgresql-10-10.17/doc/src/sgml/html/functions-trigger.html 2021-05-10 20:58:09.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions-trigger.html 2021-11-08 22:24:51.000000000 +0000
@@ -1,5 +1,5 @@
-9.27. Trigger Functions
Currently PostgreSQL provides one built in trigger
function, suppress_redundant_updates_trigger,
which will prevent any update
that does not actually change the data in the row from taking place, in
@@ -30,4 +30,4 @@
you might have on the table.
For more information about creating triggers, see
CREATE TRIGGER.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/functions-window.html postgresql-10-10.19/doc/src/sgml/html/functions-window.html
--- postgresql-10-10.17/doc/src/sgml/html/functions-window.html 2021-05-10 20:58:08.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions-window.html 2021-11-08 22:24:51.000000000 +0000
@@ -1,5 +1,5 @@
-9.21. 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
feature, and Section 4.2.8 for syntax
@@ -127,4 +127,4 @@
percent_rank computes the fraction of partition rows that
are less than the current row, assuming the current row does not exist
in the partition.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/functions-xml.html postgresql-10-10.19/doc/src/sgml/html/functions-xml.html
--- postgresql-10-10.17/doc/src/sgml/html/functions-xml.html 2021-05-10 20:58:08.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/functions-xml.html 2021-11-08 22:24:50.000000000 +0000
@@ -1,5 +1,5 @@
-9.14. 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
and xmlserialize for converting to and from
@@ -678,4 +678,4 @@
</html>
</xsl:template>
-</xsl:stylesheet>
\ No newline at end of file
+</xsl:stylesheet>
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/fuzzystrmatch.html postgresql-10-10.19/doc/src/sgml/html/fuzzystrmatch.html
--- postgresql-10-10.17/doc/src/sgml/html/fuzzystrmatch.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/fuzzystrmatch.html 2021-11-08 22:25:11.000000000 +0000
@@ -1,5 +1,5 @@
-F.16. fuzzystrmatch
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
custom access methods, because they cannot register their own WAL redo
@@ -74,4 +74,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 -Nru postgresql-10-10.17/doc/src/sgml/html/geqo-biblio.html postgresql-10-10.19/doc/src/sgml/html/geqo-biblio.html
--- postgresql-10-10.17/doc/src/sgml/html/geqo-biblio.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/geqo-biblio.html 2021-11-08 22:25:08.000000000 +0000
@@ -1,5 +1,5 @@
-59.4. Further Reading
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 -Nru postgresql-10-10.17/doc/src/sgml/html/geqo-intro2.html postgresql-10-10.19/doc/src/sgml/html/geqo-intro2.html
--- postgresql-10-10.17/doc/src/sgml/html/geqo-intro2.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/geqo-intro2.html 2021-11-08 22:25:07.000000000 +0000
@@ -1,5 +1,5 @@
-59.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
population of individuals.
@@ -39,4 +39,4 @@
| | evaluate FITNESS of P''(t) |
| +-------------------------------------+
| | t := t + 1 |
-+===+=====================================+
\ No newline at end of file
++===+=====================================+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/geqo-intro.html postgresql-10-10.19/doc/src/sgml/html/geqo-intro.html
--- postgresql-10-10.17/doc/src/sgml/html/geqo-intro.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/geqo-intro.html 2021-11-08 22:25:07.000000000 +0000
@@ -1,5 +1,5 @@
-59.1. Query Handling as a Complex Optimization Problem
59.1. Query Handling as a Complex Optimization Problem
59.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
number of joins in the query. Further optimization effort is
@@ -29,4 +29,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 -Nru postgresql-10-10.17/doc/src/sgml/html/geqo-pg-intro.html postgresql-10-10.19/doc/src/sgml/html/geqo-pg-intro.html
--- postgresql-10-10.17/doc/src/sgml/html/geqo-pg-intro.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/geqo-pg-intro.html 2021-11-08 22:25:07.000000000 +0000
@@ -1,5 +1,5 @@
-59.3. Genetic Query Optimization (GEQO) in PostgreSQL
59.3. Genetic Query Optimization (GEQO) in PostgreSQL
The GEQO module approaches the query
optimization problem as though it were the well-known traveling salesman
problem (TSP).
@@ -88,4 +88,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 -Nru postgresql-10-10.17/doc/src/sgml/html/gin-builtin-opclasses.html postgresql-10-10.19/doc/src/sgml/html/gin-builtin-opclasses.html
--- postgresql-10-10.17/doc/src/sgml/html/gin-builtin-opclasses.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/gin-builtin-opclasses.html 2021-11-08 22:25:08.000000000 +0000
@@ -1,5 +1,5 @@
-64.2. Built-in Operator Classes
The core PostgreSQL distribution
includes the GIN operator classes shown in
Table 64.1.
(Some of the optional modules described in Appendix F
@@ -19,4 +19,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 -Nru postgresql-10-10.17/doc/src/sgml/html/gin-examples.html postgresql-10-10.19/doc/src/sgml/html/gin-examples.html
--- postgresql-10-10.17/doc/src/sgml/html/gin-examples.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/gin-examples.html 2021-11-08 22:25:08.000000000 +0000
@@ -1,9 +1,9 @@
-64.7. Examples
The core PostgreSQL distribution
includes the GIN operator classes previously shown in
Table 64.1.
The following contrib modules also contain
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 -Nru postgresql-10-10.17/doc/src/sgml/html/gin-extensibility.html postgresql-10-10.19/doc/src/sgml/html/gin-extensibility.html
--- postgresql-10-10.17/doc/src/sgml/html/gin-extensibility.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/gin-extensibility.html 2021-11-08 22:25:08.000000000 +0000
@@ -1,5 +1,5 @@
-64.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
takes care of concurrency, logging and searching the tree structure.
@@ -201,4 +201,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 -Nru postgresql-10-10.17/doc/src/sgml/html/gin.html postgresql-10-10.19/doc/src/sgml/html/gin.html
--- postgresql-10-10.17/doc/src/sgml/html/gin.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/gin.html 2021-11-08 22:25:08.000000000 +0000
@@ -1,2 +1,2 @@
-Chapter 64. GIN Indexes
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
page contains either a pointer to a B-tree of heap pointers (a
@@ -53,4 +53,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 -Nru postgresql-10-10.17/doc/src/sgml/html/gin-intro.html postgresql-10-10.19/doc/src/sgml/html/gin-intro.html
--- postgresql-10-10.17/doc/src/sgml/html/gin-intro.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/gin-intro.html 2021-11-08 22:25:08.000000000 +0000
@@ -1,5 +1,5 @@
-64.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
the index need to search for element values that appear within
@@ -31,4 +31,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 -Nru postgresql-10-10.17/doc/src/sgml/html/gin-limit.html postgresql-10-10.19/doc/src/sgml/html/gin-limit.html
--- postgresql-10-10.17/doc/src/sgml/html/gin-limit.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/gin-limit.html 2021-11-08 22:25:08.000000000 +0000
@@ -1,9 +1,9 @@
-64.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),
and extractQuery will not be called on a null query
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 -Nru postgresql-10-10.17/doc/src/sgml/html/gin-tips.html postgresql-10-10.19/doc/src/sgml/html/gin-tips.html
--- postgresql-10-10.17/doc/src/sgml/html/gin-tips.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/gin-tips.html 2021-11-08 22:25:08.000000000 +0000
@@ -1,5 +1,5 @@
-64.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
index and recreate it after finishing bulk insertion.
@@ -45,4 +45,4 @@
and the quality of the system's random number generator.
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 -Nru postgresql-10-10.17/doc/src/sgml/html/gist-builtin-opclasses.html postgresql-10-10.19/doc/src/sgml/html/gist-builtin-opclasses.html
--- postgresql-10-10.17/doc/src/sgml/html/gist-builtin-opclasses.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/gist-builtin-opclasses.html 2021-11-08 22:25:08.000000000 +0000
@@ -1,5 +1,5 @@
-62.2. Built-in Operator Classes
The core PostgreSQL distribution
includes the GiST operator classes shown in
Table 62.1.
(Some of the optional modules described in Appendix F
@@ -86,4 +86,4 @@
To use it, mention the class name in CREATE INDEX,
for example
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 -Nru postgresql-10-10.17/doc/src/sgml/html/gist-examples.html postgresql-10-10.19/doc/src/sgml/html/gist-examples.html
--- postgresql-10-10.17/doc/src/sgml/html/gist-examples.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/gist-examples.html 2021-11-08 22:25:08.000000000 +0000
@@ -1,5 +1,5 @@
-62.5. Examples
The PostgreSQL source distribution includes
several examples of index methods implemented using
GiST. The core system currently provides text search
support (indexing for tsvector and tsquery) as well as
@@ -9,4 +9,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 -Nru postgresql-10-10.17/doc/src/sgml/html/gist-extensibility.html postgresql-10-10.19/doc/src/sgml/html/gist-extensibility.html
--- postgresql-10-10.17/doc/src/sgml/html/gist-extensibility.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/gist-extensibility.html 2021-11-08 22:25:08.000000000 +0000
@@ -1,5 +1,5 @@
-62.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
GiST interface has a high level of abstraction,
@@ -525,4 +525,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/gist.html postgresql-10-10.19/doc/src/sgml/html/gist.html
--- postgresql-10-10.17/doc/src/sgml/html/gist.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/gist.html 2021-11-08 22:25:08.000000000 +0000
@@ -1,2 +1,2 @@
-Chapter 62. GiST Indexes
Building large GiST indexes by simply inserting all the tuples tends to be
slow, because if the index tuples are scattered across the index and the
index is large enough to not fit in cache, the insertions need to perform
a lot of random I/O. Beginning in version 9.2, PostgreSQL supports a more
@@ -21,4 +21,4 @@
to the 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 -Nru postgresql-10-10.17/doc/src/sgml/html/gist-intro.html postgresql-10-10.19/doc/src/sgml/html/gist-intro.html
--- postgresql-10-10.17/doc/src/sgml/html/gist-intro.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/gist-intro.html 2021-11-08 22:25:08.000000000 +0000
@@ -1,5 +1,5 @@
-62.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
other indexing schemes can be implemented in GiST.
@@ -16,4 +16,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 -Nru postgresql-10-10.17/doc/src/sgml/html/git.html postgresql-10-10.19/doc/src/sgml/html/git.html
--- postgresql-10-10.17/doc/src/sgml/html/git.html 2021-05-10 20:58:29.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/git.html 2021-11-08 22:25:12.000000000 +0000
@@ -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
patches.
@@ -27,4 +27,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/hash-implementation.html postgresql-10-10.19/doc/src/sgml/html/hash-implementation.html
--- postgresql-10-10.17/doc/src/sgml/html/hash-implementation.html 1970-01-01 00:00:00.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/hash-implementation.html 2021-11-08 22:25:08.000000000 +0000
@@ -0,0 +1,31 @@
+
+66.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
+ pages that have been freed and are available for re-use. For addressing
+ purposes, bitmap pages are regarded as a subset of the overflow pages.
+
Both scanning the index and inserting tuples require locating the bucket
+ where a given tuple ought to be located. To do this, we need the bucket
+ count, highmask, and lowmask from the metapage; however, it's undesirable
+ for performance reasons to have to have to lock and pin the metapage for
+ every such operation. Instead, we retain a cached copy of the metapage
+ in each backend's relcache entry. This will produce the correct bucket
+ mapping as long as the target bucket hasn't been split since the last
+ cache refresh.
+
Primary bucket pages and overflow pages are allocated independently since
+ any given index might need more or fewer overflow pages relative to its
+ number of buckets. The hash code uses an interesting set of addressing
+ rules to support a variable number of overflow pages while not having to
+ move primary bucket pages around after they are created.
+
Each row in the table indexed is represented by a single index tuple in
+ the hash index. Hash index tuples are stored in bucket pages, and if
+ they exist, overflow pages. We speed up searches by keeping the index entries
+ in any one index page sorted by hash code, thus allowing binary search to be
+ used within an index page. Note however that there is *no* assumption about
+ the relative ordering of hash codes across different index pages of a bucket.
+
The bucket splitting algorithms to expand the hash index are too complex to
+ be worthy of mention here, though are described in more detail in
+ 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
diff -Nru postgresql-10-10.17/doc/src/sgml/html/hash-index.html postgresql-10-10.19/doc/src/sgml/html/hash-index.html
--- postgresql-10-10.17/doc/src/sgml/html/hash-index.html 1970-01-01 00:00:00.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/hash-index.html 2021-11-08 22:25:08.000000000 +0000
@@ -0,0 +1,2 @@
+
+Chapter 66. Hash Indexes
PostgreSQL
+ includes an implementation of persistent on-disk hash indexes,
+ which are fully crash recoverable. Any data type can be indexed by a
+ hash index, including data types that do not have a well-defined linear
+ ordering. Hash indexes store only the hash value of the data being
+ indexed, thus there are no restrictions on the size of the data column
+ being indexed.
+
Hash indexes support only single-column indexes and do not allow
+ uniqueness checking.
+
Hash indexes support only the = operator,
+ so WHERE clauses that specify range operations will not be able to take
+ advantage of hash indexes.
+
Each hash index tuple stores just the 4-byte hash value, not the actual
+ column value. As a result, hash indexes may be much smaller than B-trees
+ when indexing longer data items such as UUIDs, URLs, etc. The absence of
+ the column value also makes all hash index scans lossy. Hash indexes may
+ take part in bitmap index scans and backward scans.
+
Hash indexes are best optimized for SELECT and UPDATE-heavy workloads
+ that use equality scans on larger tables. In a B-tree index, searches must
+ descend through the tree until the leaf page is found. In tables with
+ millions of rows, this descent can increase access time to data. The
+ equivalent of a leaf page in a hash index is referred to as a bucket page. In
+ contrast, a hash index allows accessing the bucket pages directly,
+ thereby potentially reducing index access time in larger tables. This
+ reduction in "logical I/O" becomes even more pronounced on indexes/data
+ larger than shared_buffers/RAM.
+
Hash indexes have been designed to cope with uneven distributions of
+ hash values. Direct access to the bucket pages works well if the hash
+ values are evenly distributed. When inserts mean that the bucket page
+ becomes full, additional overflow pages are chained to that specific
+ bucket page, locally expanding the storage for index tuples that match
+ that hash value. When scanning a hash bucket during queries, we need to
+ scan through all of the overflow pages. Thus an unbalanced hash index
+ might actually be worse than a B-tree in terms of number of block
+ accesses required, for some data.
+
As a result of the overflow cases, we can say that hash indexes are
+ most suitable for unique, nearly unique data or data with a low number
+ of rows per hash bucket.
+ One possible way to avoid problems is to exclude highly non-unique
+ values from the index using a partial index condition, but this may
+ not be suitable in many cases.
+
Like B-Trees, hash indexes perform simple index tuple deletion. This
+ is a deferred maintenance operation that deletes index tuples that are
+ known to be safe to delete (those whose item identifier's LP_DEAD bit
+ is already set). If an insert finds no space is available on a page we
+ try to avoid creating a new overflow page by attempting to remove dead
+ index tuples. Removal cannot occur if the page is pinned at that time.
+ Deletion of dead index pointers also occurs during VACUUM.
+
If it can, VACUUM will also try to squeeze the index tuples onto as
+ few overflow pages as possible, minimizing the overflow chain. If an
+ overflow page becomes empty, overflow pages can be recycled for reuse
+ in other buckets, though we never return them to the operating system.
+ There is currently no provision to shrink a hash index, other than by
+ rebuilding it with REINDEX.
+ There is no provision for reducing the number of buckets, either.
+
Hash indexes may expand the number of bucket pages as the number of
+ rows indexed grows. The hash key-to-bucket-number mapping is chosen so that
+ the index can be incrementally expanded. When a new bucket is to be added to
+ the index, exactly one existing bucket will need to be "split", with some of
+ its tuples being transferred to the new bucket according to the updated
+ key-to-bucket-number mapping.
+
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
diff -Nru postgresql-10-10.17/doc/src/sgml/html/high-availability.html postgresql-10-10.19/doc/src/sgml/html/high-availability.html
--- postgresql-10-10.17/doc/src/sgml/html/high-availability.html 2021-05-10 20:58:11.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/high-availability.html 2021-11-08 22:24:54.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 26. High Availability, Load Balancing, and Replication
Chapter 26. 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
data (load balancing). Ideally, database servers could work
@@ -47,4 +47,4 @@
one might have a minimal performance impact.
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 -Nru postgresql-10-10.17/doc/src/sgml/html/history.html postgresql-10-10.19/doc/src/sgml/html/history.html
--- postgresql-10-10.17/doc/src/sgml/html/history.html 2021-05-10 20:58:05.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/history.html 2021-11-08 22:24:48.000000000 +0000
@@ -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
University of California at Berkeley. With over two decades of
@@ -118,4 +118,4 @@
all areas.
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 -Nru postgresql-10-10.17/doc/src/sgml/html/hot-standby.html postgresql-10-10.19/doc/src/sgml/html/hot-standby.html
--- postgresql-10-10.17/doc/src/sgml/html/hot-standby.html 2021-05-10 20:58:11.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/hot-standby.html 2021-11-08 22:24:54.000000000 +0000
@@ -1,5 +1,5 @@
-26.5. 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
is useful both for replication purposes and for restoring a backup
@@ -436,4 +436,4 @@
hot standby mode will generate an error.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/how-parallel-query-works.html postgresql-10-10.19/doc/src/sgml/html/how-parallel-query-works.html
--- postgresql-10-10.17/doc/src/sgml/html/how-parallel-query-works.html 2021-05-10 20:58:09.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/how-parallel-query-works.html 2021-11-08 22:24:52.000000000 +0000
@@ -1,6 +1,6 @@
-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 which includes
+
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
node. Here is a simple example:
@@ -24,7 +24,7 @@
Gather node, it will run in parallel.
Using EXPLAIN, you can see the number of
workers chosen by the planner. When the Gather node is reached
- during query execution, the process which is implementing the user's
+ during query execution, the process that is implementing the user's
session will request a number of background
worker processes equal to the number
of workers chosen by the planner. The number of background workers that
@@ -41,7 +41,7 @@
so that more workers can be run simultaneously or alternatively reducing
max_parallel_workers_per_gather so that the planner
requests fewer workers.
-
Every background worker process which is successfully started for a given
+
Every background worker process that is successfully started for a given
parallel query will execute the parallel portion of the plan. The leader
will also execute that portion of the plan, but it has an additional
responsibility: it must also read all of the tuples generated by the
@@ -50,7 +50,7 @@
worker, speeding up query execution. Conversely, when the parallel portion
of the plan generates a large number of tuples, the leader may be almost
entirely occupied with reading the tuples generated by the workers and
- performing any further processing steps which are required by plan nodes
+ performing any further processing steps that are required by plan nodes
above the level of the Gather node or
Gather Merge node. In such cases, the leader will
do very little of the work of executing the parallel portion of the plan.
@@ -61,4 +61,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/hstore.html postgresql-10-10.19/doc/src/sgml/html/hstore.html
--- postgresql-10-10.17/doc/src/sgml/html/hstore.html 2021-05-10 20:58:28.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/hstore.html 2021-11-08 22:25:11.000000000 +0000
@@ -1,5 +1,5 @@
-F.17. 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
that are rarely examined, or semi-structured data. Keys and values are
@@ -171,4 +171,4 @@
Teodor Sigaev <teodor@sigaev.ru>, Moscow, Delta-Soft Ltd., Russia
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/indexam.html postgresql-10-10.19/doc/src/sgml/html/indexam.html
--- postgresql-10-10.17/doc/src/sgml/html/indexam.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/indexam.html 2021-11-08 22:25:08.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 60. Index Access Method Interface Definition
Chapter 60. 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
knows nothing about indexes beyond what is specified here, so it is
@@ -13,12 +13,12 @@
practice, all index access methods divide indexes into standard-size
pages so that they can use the regular storage manager and buffer manager
to access the index contents. (All the existing index access methods
- furthermore use the standard page layout described in Section 66.6, and most use the same format for index
+ furthermore use the standard page layout described in Section 67.6, and most use the same format for index
tuple headers; but these decisions are not forced on an access method.)
An index is effectively a mapping from some data key values to
tuple identifiers, or TIDs, of row versions
(tuples) in the index's parent table. A TID consists of a
- block number and an item number within that block (see Section 66.6). This is sufficient
+ block number and an item number within that block (see Section 67.6). This is sufficient
information to fetch a particular row version from the table.
Indexes are not directly aware that under MVCC, there might be multiple
extant versions of the same logical row; to an index, each tuple is
@@ -28,4 +28,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 -Nru postgresql-10-10.17/doc/src/sgml/html/index-api.html postgresql-10-10.19/doc/src/sgml/html/index-api.html
--- postgresql-10-10.17/doc/src/sgml/html/index-api.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/index-api.html 2021-11-08 22:25:08.000000000 +0000
@@ -1,5 +1,5 @@
-60.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
specifies a name and a handler function for the access
@@ -148,4 +148,4 @@
amsearchnulls, indicating that it supports
IS NULL and IS NOT NULL clauses as search
conditions.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/index-cost-estimation.html postgresql-10-10.19/doc/src/sgml/html/index-cost-estimation.html
--- postgresql-10-10.17/doc/src/sgml/html/index-cost-estimation.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/index-cost-estimation.html 2021-11-08 22:25:08.000000000 +0000
@@ -1,5 +1,5 @@
-60.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
of the cost of accessing the index and the selectivity of the WHERE
@@ -107,4 +107,4 @@
is not known, the conservative estimate is zero (no correlation).
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 -Nru postgresql-10-10.17/doc/src/sgml/html/indexes-bitmap-scans.html postgresql-10-10.19/doc/src/sgml/html/indexes-bitmap-scans.html
--- postgresql-10-10.17/doc/src/sgml/html/indexes-bitmap-scans.html 2021-05-10 20:58:09.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/indexes-bitmap-scans.html 2021-11-08 22:24:51.000000000 +0000
@@ -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)
a query condition like WHERE a = 5 AND b = 6 could
@@ -54,4 +54,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 -Nru postgresql-10-10.17/doc/src/sgml/html/indexes-collations.html postgresql-10-10.19/doc/src/sgml/html/indexes-collations.html
--- postgresql-10-10.17/doc/src/sgml/html/indexes-collations.html 2021-05-10 20:58:09.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/indexes-collations.html 2021-11-08 22:24:52.000000000 +0000
@@ -1,5 +1,5 @@
-11.10. Indexes and Collations
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.
Examining index usage for an individual query is done with the
@@ -69,4 +69,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 -Nru postgresql-10-10.17/doc/src/sgml/html/indexes-expressional.html postgresql-10-10.19/doc/src/sgml/html/indexes-expressional.html
--- postgresql-10-10.17/doc/src/sgml/html/indexes-expressional.html 2021-05-10 20:58:09.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/indexes-expressional.html 2021-11-08 22:24:51.000000000 +0000
@@ -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
access to tables based on the results of computations.
@@ -32,4 +32,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/indexes.html postgresql-10-10.19/doc/src/sgml/html/indexes.html
--- postgresql-10-10.17/doc/src/sgml/html/indexes.html 2021-05-10 20:58:09.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/indexes.html 2021-11-08 22:24:52.000000000 +0000
@@ -1,7 +1,7 @@
-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 -Nru postgresql-10-10.17/doc/src/sgml/html/indexes-index-only-scans.html postgresql-10-10.19/doc/src/sgml/html/indexes-index-only-scans.html
--- postgresql-10-10.17/doc/src/sgml/html/indexes-index-only-scans.html 2021-05-10 20:58:09.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/indexes-index-only-scans.html 2021-11-08 22:24:52.000000000 +0000
@@ -1,5 +1,5 @@
-11.11. Index-Only Scans
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 table's heap
in PostgreSQL terminology). This means that in an
@@ -120,4 +120,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/indexes-intro.html postgresql-10-10.19/doc/src/sgml/html/indexes-intro.html
--- postgresql-10-10.17/doc/src/sgml/html/indexes-intro.html 2021-05-10 20:58:09.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/indexes-intro.html 2021-11-08 22:24:51.000000000 +0000
@@ -1,5 +1,5 @@
-11.1. Introduction
CREATE TABLE test1 (
id integer,
content varchar
@@ -58,4 +58,4 @@
table. This adds overhead to data manipulation operations.
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 -Nru postgresql-10-10.17/doc/src/sgml/html/indexes-multicolumn.html postgresql-10-10.19/doc/src/sgml/html/indexes-multicolumn.html
--- postgresql-10-10.17/doc/src/sgml/html/indexes-multicolumn.html 2021-05-10 20:58:09.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/indexes-multicolumn.html 2021-11-08 22:24:51.000000000 +0000
@@ -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:
CREATE TABLE test2 (
major int,
@@ -63,4 +63,4 @@
Section 11.5 and
Section 11.11 for some discussion of the
merits of different index configurations.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/indexes-opclass.html postgresql-10-10.19/doc/src/sgml/html/indexes-opclass.html
--- postgresql-10-10.17/doc/src/sgml/html/indexes-opclass.html 2021-05-10 20:58:09.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/indexes-opclass.html 2021-11-08 22:24:52.000000000 +0000
@@ -1,5 +1,5 @@
-11.9. Operator Classes and Operator Families
An index definition can specify an operator
class for each column of an index.
CREATE INDEX name ON table (columnopclass [sort options] [, ...]);
The operator class identifies the operators to be used by the index
@@ -82,4 +82,4 @@
WHERE opf.opfmethod = am.oid AND
amop.amopfamily = opf.oid
ORDER BY index_method, opfamily_name, opfamily_operator;
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/indexes-ordering.html postgresql-10-10.19/doc/src/sgml/html/indexes-ordering.html
--- postgresql-10-10.17/doc/src/sgml/html/indexes-ordering.html 2021-05-10 20:58:09.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/indexes-ordering.html 2021-11-08 22:24:51.000000000 +0000
@@ -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
without a separate sorting step. Of the index types currently
@@ -52,4 +52,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/indexes-partial.html postgresql-10-10.19/doc/src/sgml/html/indexes-partial.html
--- postgresql-10-10.17/doc/src/sgml/html/indexes-partial.html 2021-05-10 20:58:09.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/indexes-partial.html 2021-11-08 22:24:52.000000000 +0000
@@ -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
partial index). The index contains entries only for those table
@@ -166,4 +166,4 @@
does understand that the tables and indexes are non-overlapping, so
far better performance is possible.
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/indexes-types.html postgresql-10-10.19/doc/src/sgml/html/indexes-types.html
--- postgresql-10-10.17/doc/src/sgml/html/indexes-types.html 2021-05-10 20:58:09.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/indexes-types.html 2021-11-08 22:24:51.000000000 +0000
@@ -1,5 +1,5 @@
-11.2. Index Types
PostgreSQL provides several index types:
B-tree, Hash, GiST, SP-GiST, GIN and BRIN.
Each index type uses a different
algorithm that is best suited to different types of queries.
@@ -129,4 +129,4 @@
The BRIN operator classes included in the standard distribution are
documented in Table 65.1.
For more information see Chapter 65.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/indexes-unique.html postgresql-10-10.19/doc/src/sgml/html/indexes-unique.html
--- postgresql-10-10.17/doc/src/sgml/html/indexes-unique.html 2021-05-10 20:58:09.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/indexes-unique.html 2021-11-08 22:24:51.000000000 +0000
@@ -1,5 +1,5 @@
-11.6. Unique Indexes
The index construction and maintenance functions that an index access
method must provide in IndexAmRoutine are:
IndexBuildResult *
ambuild (Relation heapRelation,
@@ -219,7 +219,7 @@
feature is used when a new outer tuple is selected by a nested-loop join
and so a new key comparison value is needed, but the scan key structure
remains the same.
-
Fetch the next tuple in the given scan, moving in the given
@@ -337,4 +337,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/index.html postgresql-10-10.19/doc/src/sgml/html/index.html
--- postgresql-10-10.17/doc/src/sgml/html/index.html 2021-05-10 20:58:30.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/index.html 2021-11-08 22:25:13.000000000 +0000
@@ -1,2 +1,2 @@
-PostgreSQL 10.17 Documentation
Index access methods must handle concurrent updates
of the index by multiple processes.
The core PostgreSQL system obtains
AccessShareLock on the index during an index scan, and
@@ -77,4 +77,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 -Nru postgresql-10-10.17/doc/src/sgml/html/index-scanning.html postgresql-10-10.19/doc/src/sgml/html/index-scanning.html
--- postgresql-10-10.17/doc/src/sgml/html/index-scanning.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/index-scanning.html 2021-11-08 22:25:08.000000000 +0000
@@ -1,5 +1,5 @@
-60.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
actually fetching those tuples from the index's parent table, nor in
@@ -107,4 +107,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 -Nru postgresql-10-10.17/doc/src/sgml/html/index-unique-checks.html postgresql-10-10.19/doc/src/sgml/html/index-unique-checks.html
--- postgresql-10-10.17/doc/src/sgml/html/index-unique-checks.html 2021-05-10 20:58:25.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/index-unique-checks.html 2021-11-08 22:25:08.000000000 +0000
@@ -1,5 +1,5 @@
-60.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
feature sets amcanunique true.
@@ -90,4 +90,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 -Nru postgresql-10-10.17/doc/src/sgml/html/information-schema.html postgresql-10-10.19/doc/src/sgml/html/information-schema.html
--- postgresql-10-10.17/doc/src/sgml/html/information-schema.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/information-schema.html 2021-11-08 22:24:57.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 36. 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
be expected to be portable and remain stable — unlike the system
@@ -25,4 +25,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 -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-administrable-role-authorizations.html postgresql-10-10.19/doc/src/sgml/html/infoschema-administrable-role-authorizations.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-administrable-role-authorizations.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-administrable-role-authorizations.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,8 +1,8 @@
-36.4. administrable_role_authorizations
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
question. The current user itself is also an applicable role. The
@@ -11,4 +11,4 @@
memberships)
role_name
sql_identifier
Name of a role
is_grantable
yes_or_no
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 -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-attributes.html postgresql-10-10.19/doc/src/sgml/html/infoschema-attributes.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-attributes.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-attributes.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.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,
which are sometimes called attributes in PostgreSQL contexts.)
@@ -78,4 +78,4 @@
versions.)
is_derived_reference_attribute
yes_or_no
Applies to a feature not available in PostgreSQL
See also under Section 36.16, 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 -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-character-sets.html postgresql-10-10.19/doc/src/sgml/html/infoschema-character-sets.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-character-sets.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-character-sets.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.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
shows one, which is the database encoding.
@@ -34,4 +34,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 -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-check-constraint-routine-usage.html postgresql-10-10.19/doc/src/sgml/html/infoschema-check-constraint-routine-usage.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-check-constraint-routine-usage.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-check-constraint-routine-usage.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,7 +1,7 @@
-36.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
a currently enabled role.
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
domain is the owner of the constraint.)
-
Table 36.7. check_constraints Columns
Name
Data Type
Description
constraint_catalog
sql_identifier
Name of the database containing the constraint (always the current database)
constraint_schema
sql_identifier
Name of the schema containing the constraint
constraint_name
sql_identifier
Name of the constraint
check_clause
character_data
The check expression of the check constraint
\ No newline at end of file
+
Table 36.7. check_constraints Columns
Name
Data Type
Description
constraint_catalog
sql_identifier
Name of the database containing the constraint (always the current database)
constraint_schema
sql_identifier
Name of the schema containing the constraint
constraint_name
sql_identifier
Name of the constraint
check_clause
character_data
The check expression of the check constraint
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-collation-character-set-applicab.html postgresql-10-10.19/doc/src/sgml/html/infoschema-collation-character-set-applicab.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-collation-character-set-applicab.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-collation-character-set-applicab.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,8 +1,8 @@
-36.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
database (see explanation
in Section 36.7), so this view does
not provide much useful information.
-
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.
-
Table 36.10. column_domain_usage Columns
Name
Data Type
Description
domain_catalog
sql_identifier
Name of the database containing the domain (always the current database)
domain_schema
sql_identifier
Name of the schema containing the domain
domain_name
sql_identifier
Name of the domain
table_catalog
sql_identifier
Name of the database containing the table (always the current database)
table_schema
sql_identifier
Name of the schema containing the table
table_name
sql_identifier
Name of the table
column_name
sql_identifier
Name of the column
\ No newline at end of file
+
Table 36.10. column_domain_usage Columns
Name
Data Type
Description
domain_catalog
sql_identifier
Name of the database containing the domain (always the current database)
domain_schema
sql_identifier
Name of the schema containing the domain
domain_name
sql_identifier
Name of the domain
table_catalog
sql_identifier
Name of the database containing the table (always the current database)
table_schema
sql_identifier
Name of the schema containing the table
table_name
sql_identifier
Name of the table
column_name
sql_identifier
Name of the column
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-column-options.html postgresql-10-10.19/doc/src/sgml/html/infoschema-column-options.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-column-options.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-column-options.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,6 +1,6 @@
-36.13. 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
(by way of being the owner or having some privilege).
-
Table 36.11. column_options Columns
Name
Data Type
Description
table_catalog
sql_identifier
Name of the database that contains the foreign table (always the current database)
table_schema
sql_identifier
Name of the schema that contains the foreign table
table_name
sql_identifier
Name of the foreign table
column_name
sql_identifier
Name of the column
option_name
sql_identifier
Name of an option
option_value
character_data
Value of the option
\ No newline at end of file
+
Table 36.11. column_options Columns
Name
Data Type
Description
table_catalog
sql_identifier
Name of the database that contains the foreign table (always the current database)
table_schema
sql_identifier
Name of the schema that contains the foreign table
table_name
sql_identifier
Name of the foreign table
column_name
sql_identifier
Name of the column
option_name
sql_identifier
Name of an option
option_value
character_data
Value of the option
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-column-privileges.html postgresql-10-10.19/doc/src/sgml/html/infoschema-column-privileges.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-column-privileges.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-column-privileges.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.14. 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
column, grantor, and grantee.
@@ -11,4 +11,4 @@
Table 36.12. column_privileges Columns
Name
Data Type
Description
grantor
sql_identifier
Name of the role that granted the privilege
grantee
sql_identifier
Name of the role that the privilege was granted to
table_catalog
sql_identifier
Name of the database that contains the table that contains the column (always the current database)
table_schema
sql_identifier
Name of the schema that contains the table that contains the column
table_name
sql_identifier
Name of the table that contains the column
column_name
sql_identifier
Name of the column
privilege_type
character_data
Type of the privilege: SELECT,
INSERT, UPDATE, or
REFERENCES
-
is_grantable
yes_or_no
YES if the privilege is grantable, NO if not
\ No newline at end of file
+
is_grantable
yes_or_no
YES if the privilege is grantable, NO if not
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-columns.html postgresql-10-10.19/doc/src/sgml/html/infoschema-columns.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-columns.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-columns.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.16. columns
The view columns contains information about all
table columns (or view columns) in the database. System columns
(oid, etc.) are not included. Only those columns are
shown that the current user has access to (by way of being the
@@ -132,4 +132,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 -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-column-udt-usage.html postgresql-10-10.19/doc/src/sgml/html/infoschema-column-udt-usage.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-column-udt-usage.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-column-udt-usage.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.15. 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
like user-defined types, so they are included here as well. See
@@ -11,4 +11,4 @@
type of the domain, if applicable) is defined in
udt_name
sql_identifier
Name of the column data type (the underlying type of the
domain, if applicable)
-
table_catalog
sql_identifier
Name of the database containing the table (always the current database)
table_schema
sql_identifier
Name of the schema containing the table
table_name
sql_identifier
Name of the table
column_name
sql_identifier
Name of the column
\ No newline at end of file
+
table_catalog
sql_identifier
Name of the database containing the table (always the current database)
table_schema
sql_identifier
Name of the schema containing the table
table_name
sql_identifier
Name of the table
column_name
sql_identifier
Name of the column
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-constraint-column-usage.html postgresql-10-10.19/doc/src/sgml/html/infoschema-constraint-column-usage.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-constraint-column-usage.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-constraint-column-usage.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.17. 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
a currently enabled role. For a check constraint, this view
@@ -15,4 +15,4 @@
table_name
sql_identifier
Name of the table that contains the column that is used by some
constraint
column_name
sql_identifier
Name of the column that is used by some constraint
-
constraint_catalog
sql_identifier
Name of the database that contains the constraint (always the current database)
constraint_schema
sql_identifier
Name of the schema that contains the constraint
constraint_name
sql_identifier
Name of the constraint
\ No newline at end of file
+
constraint_catalog
sql_identifier
Name of the database that contains the constraint (always the current database)
constraint_schema
sql_identifier
Name of the schema that contains the constraint
constraint_name
sql_identifier
Name of the constraint
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-constraint-table-usage.html postgresql-10-10.19/doc/src/sgml/html/infoschema-constraint-table-usage.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-constraint-table-usage.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-constraint-table-usage.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.18. 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
view table_constraints, which identifies all
@@ -13,4 +13,4 @@
some constraint (always the current database)
table_schema
sql_identifier
Name of the schema that contains the table that is used by some
constraint
-
table_name
sql_identifier
Name of the table that is used by some constraint
constraint_catalog
sql_identifier
Name of the database that contains the constraint (always the current database)
constraint_schema
sql_identifier
Name of the schema that contains the constraint
constraint_name
sql_identifier
Name of the constraint
\ No newline at end of file
+
table_name
sql_identifier
Name of the table that is used by some constraint
constraint_catalog
sql_identifier
Name of the database that contains the constraint (always the current database)
constraint_schema
sql_identifier
Name of the schema that contains the constraint
constraint_name
sql_identifier
Name of the constraint
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-data-type-privileges.html postgresql-10-10.19/doc/src/sgml/html/infoschema-data-type-privileges.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-data-type-privileges.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-data-type-privileges.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.19. 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
for it. A data type descriptor is generated whenever a data type
@@ -20,4 +20,4 @@
to a parameter or the return data type of that function).
dtd_identifier
sql_identifier
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 -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-datatypes.html postgresql-10-10.19/doc/src/sgml/html/infoschema-datatypes.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-datatypes.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-datatypes.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.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
these types for work outside the information schema, but your
@@ -23,4 +23,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 -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-domain-constraints.html postgresql-10-10.19/doc/src/sgml/html/infoschema-domain-constraints.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-domain-constraints.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-domain-constraints.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,6 +1,6 @@
-36.20. 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
having some privilege).
-
Table 36.18. domain_constraints Columns
Name
Data Type
Description
constraint_catalog
sql_identifier
Name of the database that contains the constraint (always the current database)
constraint_schema
sql_identifier
Name of the schema that contains the constraint
constraint_name
sql_identifier
Name of the constraint
domain_catalog
sql_identifier
Name of the database that contains the domain (always the current database)
domain_schema
sql_identifier
Name of the schema that contains the domain
domain_name
sql_identifier
Name of the domain
is_deferrable
yes_or_no
YES if the constraint is deferrable, NO if not
initially_deferred
yes_or_no
YES if the constraint is deferrable and initially deferred, NO if not
\ No newline at end of file
+
Table 36.18. domain_constraints Columns
Name
Data Type
Description
constraint_catalog
sql_identifier
Name of the database that contains the constraint (always the current database)
constraint_schema
sql_identifier
Name of the schema that contains the constraint
constraint_name
sql_identifier
Name of the constraint
domain_catalog
sql_identifier
Name of the database that contains the domain (always the current database)
domain_schema
sql_identifier
Name of the schema that contains the domain
domain_name
sql_identifier
Name of the domain
is_deferrable
yes_or_no
YES if the constraint is deferrable, NO if not
initially_deferred
yes_or_no
YES if the constraint is deferrable and initially deferred, NO if not
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-domains.html postgresql-10-10.19/doc/src/sgml/html/infoschema-domains.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-domains.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-domains.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.22. domains
The view domains contains all 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 having some privilege).
Table 36.20. domains Columns
Name
Data Type
Description
domain_catalog
sql_identifier
Name of the database that contains the domain (always the current database)
domain_schema
sql_identifier
Name of the schema that contains the domain
domain_name
sql_identifier
Name of the domain
data_type
character_data
Data type of the domain, if it is a built-in type, or
@@ -65,4 +65,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 -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-domain-udt-usage.html postgresql-10-10.19/doc/src/sgml/html/infoschema-domain-udt-usage.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-domain-udt-usage.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-domain-udt-usage.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,7 +1,7 @@
-36.21. 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
types behave like user-defined types, so they are included here as
well.
-
Table 36.19. domain_udt_usage Columns
Name
Data Type
Description
udt_catalog
sql_identifier
Name of the database that the domain data type is defined in (always the current database)
udt_schema
sql_identifier
Name of the schema that the domain data type is defined in
udt_name
sql_identifier
Name of the domain data type
domain_catalog
sql_identifier
Name of the database that contains the domain (always the current database)
domain_schema
sql_identifier
Name of the schema that contains the domain
domain_name
sql_identifier
Name of the domain
\ No newline at end of file
+
Table 36.19. domain_udt_usage Columns
Name
Data Type
Description
udt_catalog
sql_identifier
Name of the database that the domain data type is defined in (always the current database)
udt_schema
sql_identifier
Name of the schema that the domain data type is defined in
udt_name
sql_identifier
Name of the domain data type
domain_catalog
sql_identifier
Name of the database that contains the domain (always the current database)
domain_schema
sql_identifier
Name of the schema that contains the domain
domain_name
sql_identifier
Name of the domain
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-element-types.html postgresql-10-10.19/doc/src/sgml/html/infoschema-element-types.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-element-types.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-element-types.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.23. 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
be of an array type, the respective information schema view only
@@ -51,4 +51,4 @@
udt_name
sql_identifier
Name of the data type of the elements
scope_catalog
sql_identifier
Applies to a feature not available in PostgreSQL
scope_schema
sql_identifier
Applies to a feature not available in PostgreSQL
scope_name
sql_identifier
Applies to a feature not available in PostgreSQL
maximum_cardinality
cardinal_number
Always null, because arrays always have unlimited maximum cardinality in PostgreSQL
dtd_identifier
sql_identifier
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 -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-enabled-roles.html postgresql-10-10.19/doc/src/sgml/html/infoschema-enabled-roles.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-enabled-roles.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-enabled-roles.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.24. 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
granted to the enabled roles with automatic inheritance. In other
@@ -13,4 +13,4 @@
applicable_roles instead of this one; See
Section 36.5 for details on
applicable_roles view.
-
Table 36.22. enabled_roles Columns
Name
Data Type
Description
role_name
sql_identifier
Name of a role
\ No newline at end of file
+
Table 36.22. enabled_roles Columns
Name
Data Type
Description
role_name
sql_identifier
Name of a role
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-foreign-data-wrapper-options.html postgresql-10-10.19/doc/src/sgml/html/infoschema-foreign-data-wrapper-options.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-foreign-data-wrapper-options.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-foreign-data-wrapper-options.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,7 +1,7 @@
-36.25. 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
current user has access to (by way of being the owner or having
some privilege).
-
Table 36.23. foreign_data_wrapper_options Columns
Name
Data Type
Description
foreign_data_wrapper_catalog
sql_identifier
Name of the database that the foreign-data wrapper is defined in (always the current database)
foreign_data_wrapper_name
sql_identifier
Name of the foreign-data wrapper
option_name
sql_identifier
Name of an option
option_value
character_data
Value of the option
\ No newline at end of file
+
Table 36.23. foreign_data_wrapper_options Columns
Name
Data Type
Description
foreign_data_wrapper_catalog
sql_identifier
Name of the database that the foreign-data wrapper is defined in (always the current database)
foreign_data_wrapper_name
sql_identifier
Name of the foreign-data wrapper
option_name
sql_identifier
Name of an option
option_value
character_data
Value of the option
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-foreign-data-wrappers.html postgresql-10-10.19/doc/src/sgml/html/infoschema-foreign-data-wrappers.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-foreign-data-wrappers.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-foreign-data-wrappers.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,7 +1,7 @@
-36.26. 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
(by way of being the owner or having some privilege).
Table 36.24. foreign_data_wrappers Columns
Name
Data Type
Description
foreign_data_wrapper_catalog
sql_identifier
Name of the database that contains the foreign-data
- wrapper (always the current database)
foreign_data_wrapper_name
sql_identifier
Name of the foreign-data wrapper
authorization_identifier
sql_identifier
Name of the owner of the foreign server
library_name
character_data
File name of the library that implementing this foreign-data wrapper
foreign_data_wrapper_language
character_data
Language used to implement this foreign-data wrapper
\ No newline at end of file
+ wrapper (always the current database)
foreign_data_wrapper_name
sql_identifier
Name of the foreign-data wrapper
authorization_identifier
sql_identifier
Name of the owner of the foreign server
library_name
character_data
File name of the library that implementing this foreign-data wrapper
foreign_data_wrapper_language
character_data
Language used to implement this foreign-data wrapper
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-foreign-server-options.html postgresql-10-10.19/doc/src/sgml/html/infoschema-foreign-server-options.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-foreign-server-options.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-foreign-server-options.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,6 +1,6 @@
-36.27. 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
(by way of being the owner or having some privilege).
-
Table 36.25. foreign_server_options Columns
Name
Data Type
Description
foreign_server_catalog
sql_identifier
Name of the database that the foreign server is defined in (always the current database)
foreign_server_name
sql_identifier
Name of the foreign server
option_name
sql_identifier
Name of an option
option_value
character_data
Value of the option
\ No newline at end of file
+
Table 36.25. foreign_server_options Columns
Name
Data Type
Description
foreign_server_catalog
sql_identifier
Name of the database that the foreign server is defined in (always the current database)
foreign_server_name
sql_identifier
Name of the foreign server
option_name
sql_identifier
Name of an option
option_value
character_data
Value of the option
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-foreign-servers.html postgresql-10-10.19/doc/src/sgml/html/infoschema-foreign-servers.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-foreign-servers.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-foreign-servers.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,7 +1,7 @@
-36.28. 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
being the owner or having some privilege).
Table 36.26. foreign_servers Columns
Name
Data Type
Description
foreign_server_catalog
sql_identifier
Name of the database that the foreign server is defined in (always the current database)
foreign_server_name
sql_identifier
Name of the foreign server
foreign_data_wrapper_catalog
sql_identifier
Name of the database that contains the foreign-data
- wrapper used by the foreign server (always the current database)
foreign_data_wrapper_name
sql_identifier
Name of the foreign-data wrapper used by the foreign server
foreign_server_type
character_data
Foreign server type information, if specified upon creation
foreign_server_version
character_data
Foreign server version information, if specified upon creation
authorization_identifier
sql_identifier
Name of the owner of the foreign server
\ No newline at end of file
+ wrapper used by the foreign server (always the current database)
foreign_data_wrapper_name
sql_identifier
Name of the foreign-data wrapper used by the foreign server
foreign_server_type
character_data
Foreign server type information, if specified upon creation
foreign_server_version
character_data
Foreign server version information, if specified upon creation
authorization_identifier
sql_identifier
Name of the owner of the foreign server
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-foreign-table-options.html postgresql-10-10.19/doc/src/sgml/html/infoschema-foreign-table-options.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-foreign-table-options.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-foreign-table-options.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,6 +1,6 @@
-36.29. 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
(by way of being the owner or having some privilege).
-
Table 36.27. foreign_table_options Columns
Name
Data Type
Description
foreign_table_catalog
sql_identifier
Name of the database that contains the foreign table (always the current database)
foreign_table_schema
sql_identifier
Name of the schema that contains the foreign table
foreign_table_name
sql_identifier
Name of the foreign table
option_name
sql_identifier
Name of an option
option_value
character_data
Value of the option
\ No newline at end of file
+
Table 36.27. foreign_table_options Columns
Name
Data Type
Description
foreign_table_catalog
sql_identifier
Name of the database that contains the foreign table (always the current database)
foreign_table_schema
sql_identifier
Name of the schema that contains the foreign table
foreign_table_name
sql_identifier
Name of the foreign table
option_name
sql_identifier
Name of an option
option_value
character_data
Value of the option
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-foreign-tables.html postgresql-10-10.19/doc/src/sgml/html/infoschema-foreign-tables.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-foreign-tables.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-foreign-tables.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,6 +1,6 @@
-36.30. 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
being the owner or having some privilege).
-
Table 36.28. foreign_tables Columns
Name
Data Type
Description
foreign_table_catalog
sql_identifier
Name of the database that the foreign table is defined in (always the current database)
foreign_table_schema
sql_identifier
Name of the schema that contains the foreign table
foreign_table_name
sql_identifier
Name of the foreign table
foreign_server_catalog
sql_identifier
Name of the database that the foreign server is defined in (always the current database)
foreign_server_name
sql_identifier
Name of the foreign server
\ No newline at end of file
+
Table 36.28. foreign_tables Columns
Name
Data Type
Description
foreign_table_catalog
sql_identifier
Name of the database that the foreign table is defined in (always the current database)
foreign_table_schema
sql_identifier
Name of the schema that contains the foreign table
foreign_table_name
sql_identifier
Name of the foreign table
foreign_server_catalog
sql_identifier
Name of the database that the foreign server is defined in (always the current database)
foreign_server_name
sql_identifier
Name of the foreign server
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-information-schema-catalog-name.html postgresql-10-10.19/doc/src/sgml/html/infoschema-information-schema-catalog-name.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-information-schema-catalog-name.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-information-schema-catalog-name.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.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).
-
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
in this view. Only those columns are shown that the current user
@@ -17,4 +17,4 @@
position_in_unique_constraint
cardinal_number
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 -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-parameters.html postgresql-10-10.19/doc/src/sgml/html/infoschema-parameters.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-parameters.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-parameters.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.32. 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
(by way of being the owner or having some privilege).
@@ -28,4 +28,4 @@
in future versions.)
parameter_default
character_data
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 -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-referential-constraints.html postgresql-10-10.19/doc/src/sgml/html/infoschema-referential-constraints.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-referential-constraints.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-referential-constraints.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.33. 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
write access to the referencing table (by way of being the
@@ -22,4 +22,4 @@
CASCADE, SET NULL,
SET DEFAULT, RESTRICT, or
NO ACTION.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-role-column-grants.html postgresql-10-10.19/doc/src/sgml/html/infoschema-role-column-grants.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-role-column-grants.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-role-column-grants.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.34. 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
column_privileges. The only effective
@@ -10,4 +10,4 @@
Table 36.32. role_column_grants Columns
Name
Data Type
Description
grantor
sql_identifier
Name of the role that granted the privilege
grantee
sql_identifier
Name of the role that the privilege was granted to
table_catalog
sql_identifier
Name of the database that contains the table that contains the column (always the current database)
table_schema
sql_identifier
Name of the schema that contains the table that contains the column
table_name
sql_identifier
Name of the table that contains the column
column_name
sql_identifier
Name of the column
privilege_type
character_data
Type of the privilege: SELECT,
INSERT, UPDATE, or
REFERENCES
-
is_grantable
yes_or_no
YES if the privilege is grantable, NO if not
\ No newline at end of file
+
is_grantable
yes_or_no
YES if the privilege is grantable, NO if not
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-role-routine-grants.html postgresql-10-10.19/doc/src/sgml/html/infoschema-role-routine-grants.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-role-routine-grants.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-role-routine-grants.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.35. 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
routine_privileges. The only effective
@@ -8,4 +8,4 @@
functions that have been made accessible to the current user by way
of a grant to PUBLIC.
Table 36.33. role_routine_grants Columns
Name
Data Type
Description
grantor
sql_identifier
Name of the role that granted the privilege
grantee
sql_identifier
Name of the role that the privilege was granted to
specific_catalog
sql_identifier
Name of the database containing the function (always the current database)
specific_schema
sql_identifier
Name of the schema containing the function
specific_name
sql_identifier
The “specific name” of the function. See Section 36.40 for more information.
-
routine_catalog
sql_identifier
Name of the database containing the function (always the current database)
routine_schema
sql_identifier
Name of the schema containing the function
routine_name
sql_identifier
Name of the function (might be duplicated in case of overloading)
privilege_type
character_data
Always EXECUTE (the only privilege type for functions)
is_grantable
yes_or_no
YES if the privilege is grantable, NO if not
\ No newline at end of file
+
routine_catalog
sql_identifier
Name of the database containing the function (always the current database)
routine_schema
sql_identifier
Name of the schema containing the function
routine_name
sql_identifier
Name of the function (might be duplicated in case of overloading)
privilege_type
character_data
Always EXECUTE (the only privilege type for functions)
is_grantable
yes_or_no
YES if the privilege is grantable, NO if not
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-role-table-grants.html postgresql-10-10.19/doc/src/sgml/html/infoschema-role-table-grants.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-role-table-grants.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-role-table-grants.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.36. 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
under table_privileges. The only effective
@@ -17,4 +17,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 -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-role-udt-grants.html postgresql-10-10.19/doc/src/sgml/html/infoschema-role-udt-grants.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-role-udt-grants.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-role-udt-grants.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.37. 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
information can be found under
@@ -9,4 +9,4 @@
current user by way of a grant to PUBLIC. Since
data types do not have real privileges in PostgreSQL, but only an
implicit grant to PUBLIC, this view is empty.
-
Table 36.35. role_udt_grants Columns
Name
Data Type
Description
grantor
sql_identifier
The name of the role that granted the privilege
grantee
sql_identifier
The name of the role that the privilege was granted to
udt_catalog
sql_identifier
Name of the database containing the type (always the current database)
udt_schema
sql_identifier
Name of the schema containing the type
udt_name
sql_identifier
Name of the type
privilege_type
character_data
Always TYPE USAGE
is_grantable
yes_or_no
YES if the privilege is grantable, NO if not
\ No newline at end of file
+
Table 36.35. role_udt_grants Columns
Name
Data Type
Description
grantor
sql_identifier
The name of the role that granted the privilege
grantee
sql_identifier
The name of the role that the privilege was granted to
udt_catalog
sql_identifier
Name of the database containing the type (always the current database)
udt_schema
sql_identifier
Name of the schema containing the type
udt_name
sql_identifier
Name of the type
privilege_type
character_data
Always TYPE USAGE
is_grantable
yes_or_no
YES if the privilege is grantable, NO if not
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-role-usage-grants.html postgresql-10-10.19/doc/src/sgml/html/infoschema-role-usage-grants.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-role-usage-grants.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-role-usage-grants.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.38. 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.
Further information can be found under
@@ -8,4 +8,4 @@
this view omits objects that have been made accessible to the
current user by way of a grant to PUBLIC.
Table 36.36. role_usage_grants Columns
Name
Data Type
Description
grantor
sql_identifier
The name of the role that granted the privilege
grantee
sql_identifier
The name of the role that the privilege was granted to
object_catalog
sql_identifier
Name of the database containing the object (always the current database)
object_schema
sql_identifier
Name of the schema containing the object, if applicable,
- else an empty string
object_name
sql_identifier
Name of the object
object_type
character_data
COLLATION or DOMAIN or FOREIGN DATA WRAPPER or FOREIGN SERVER or SEQUENCE
privilege_type
character_data
Always USAGE
is_grantable
yes_or_no
YES if the privilege is grantable, NO if not
\ No newline at end of file
+ else an empty string
object_name
sql_identifier
Name of the object
object_type
character_data
COLLATION or DOMAIN or FOREIGN DATA WRAPPER or FOREIGN SERVER or SEQUENCE
privilege_type
character_data
Always USAGE
is_grantable
yes_or_no
YES if the privilege is grantable, NO if not
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-routine-privileges.html postgresql-10-10.19/doc/src/sgml/html/infoschema-routine-privileges.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-routine-privileges.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-routine-privileges.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,7 +1,7 @@
-36.39. 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,
grantor, and grantee.
Table 36.37. routine_privileges Columns
Name
Data Type
Description
grantor
sql_identifier
Name of the role that granted the privilege
grantee
sql_identifier
Name of the role that the privilege was granted to
specific_catalog
sql_identifier
Name of the database containing the function (always the current database)
specific_schema
sql_identifier
Name of the schema containing the function
specific_name
sql_identifier
The “specific name” of the function. See Section 36.40 for more information.
-
routine_catalog
sql_identifier
Name of the database containing the function (always the current database)
routine_schema
sql_identifier
Name of the schema containing the function
routine_name
sql_identifier
Name of the function (might be duplicated in case of overloading)
privilege_type
character_data
Always EXECUTE (the only privilege type for functions)
is_grantable
yes_or_no
YES if the privilege is grantable, NO if not
\ No newline at end of file
+
routine_catalog
sql_identifier
Name of the database containing the function (always the current database)
routine_schema
sql_identifier
Name of the schema containing the function
routine_name
sql_identifier
Name of the function (might be duplicated in case of overloading)
privilege_type
character_data
Always EXECUTE (the only privilege type for functions)
is_grantable
yes_or_no
YES if the privilege is grantable, NO if not
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-routines.html postgresql-10-10.19/doc/src/sgml/html/infoschema-routines.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-routines.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-routines.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.40. routines
The view routines contains all functions in the
current database. Only those functions are shown that the current
user has access to (by way of being the owner or having some
privilege).
@@ -62,4 +62,4 @@
to_sql_specific_catalog
sql_identifier
Applies to a feature not available in PostgreSQL
to_sql_specific_schema
sql_identifier
Applies to a feature not available in PostgreSQL
to_sql_specific_name
sql_identifier
Applies to a feature not available in PostgreSQL
as_locator
yes_or_no
Applies to a feature not available in PostgreSQL
created
time_stamp
Applies to a feature not available in PostgreSQL
last_altered
time_stamp
Applies to a feature not available in PostgreSQL
new_savepoint_level
yes_or_no
Applies to a feature not available in PostgreSQL
is_udt_dependent
yes_or_no
Currently always NO. The alternative
YES applies to a feature not available in
PostgreSQL.
-
result_cast_from_data_type
character_data
Applies to a feature not available in PostgreSQL
result_cast_as_locator
yes_or_no
Applies to a feature not available in PostgreSQL
result_cast_char_max_length
cardinal_number
Applies to a feature not available in PostgreSQL
result_cast_char_octet_length
character_data
Applies to a feature not available in PostgreSQL
result_cast_char_set_catalog
sql_identifier
Applies to a feature not available in PostgreSQL
result_cast_char_set_schema
sql_identifier
Applies to a feature not available in PostgreSQL
result_cast_char_set_name
sql_identifier
Applies to a feature not available in PostgreSQL
result_cast_collation_catalog
sql_identifier
Applies to a feature not available in PostgreSQL
result_cast_collation_schema
sql_identifier
Applies to a feature not available in PostgreSQL
result_cast_collation_name
sql_identifier
Applies to a feature not available in PostgreSQL
result_cast_numeric_precision
cardinal_number
Applies to a feature not available in PostgreSQL
result_cast_numeric_precision_radix
cardinal_number
Applies to a feature not available in PostgreSQL
result_cast_numeric_scale
cardinal_number
Applies to a feature not available in PostgreSQL
result_cast_datetime_precision
character_data
Applies to a feature not available in PostgreSQL
result_cast_interval_type
character_data
Applies to a feature not available in PostgreSQL
result_cast_interval_precision
cardinal_number
Applies to a feature not available in PostgreSQL
result_cast_type_udt_catalog
sql_identifier
Applies to a feature not available in PostgreSQL
result_cast_type_udt_schema
sql_identifier
Applies to a feature not available in PostgreSQL
result_cast_type_udt_name
sql_identifier
Applies to a feature not available in PostgreSQL
result_cast_scope_catalog
sql_identifier
Applies to a feature not available in PostgreSQL
result_cast_scope_schema
sql_identifier
Applies to a feature not available in PostgreSQL
result_cast_scope_name
sql_identifier
Applies to a feature not available in PostgreSQL
result_cast_maximum_cardinality
cardinal_number
Applies to a feature not available in PostgreSQL
result_cast_dtd_identifier
sql_identifier
Applies to a feature not available in PostgreSQL
\ No newline at end of file
+
result_cast_from_data_type
character_data
Applies to a feature not available in PostgreSQL
result_cast_as_locator
yes_or_no
Applies to a feature not available in PostgreSQL
result_cast_char_max_length
cardinal_number
Applies to a feature not available in PostgreSQL
result_cast_char_octet_length
character_data
Applies to a feature not available in PostgreSQL
result_cast_char_set_catalog
sql_identifier
Applies to a feature not available in PostgreSQL
result_cast_char_set_schema
sql_identifier
Applies to a feature not available in PostgreSQL
result_cast_char_set_name
sql_identifier
Applies to a feature not available in PostgreSQL
result_cast_collation_catalog
sql_identifier
Applies to a feature not available in PostgreSQL
result_cast_collation_schema
sql_identifier
Applies to a feature not available in PostgreSQL
result_cast_collation_name
sql_identifier
Applies to a feature not available in PostgreSQL
result_cast_numeric_precision
cardinal_number
Applies to a feature not available in PostgreSQL
result_cast_numeric_precision_radix
cardinal_number
Applies to a feature not available in PostgreSQL
result_cast_numeric_scale
cardinal_number
Applies to a feature not available in PostgreSQL
result_cast_datetime_precision
character_data
Applies to a feature not available in PostgreSQL
result_cast_interval_type
character_data
Applies to a feature not available in PostgreSQL
result_cast_interval_precision
cardinal_number
Applies to a feature not available in PostgreSQL
result_cast_type_udt_catalog
sql_identifier
Applies to a feature not available in PostgreSQL
result_cast_type_udt_schema
sql_identifier
Applies to a feature not available in PostgreSQL
result_cast_type_udt_name
sql_identifier
Applies to a feature not available in PostgreSQL
result_cast_scope_catalog
sql_identifier
Applies to a feature not available in PostgreSQL
result_cast_scope_schema
sql_identifier
Applies to a feature not available in PostgreSQL
result_cast_scope_name
sql_identifier
Applies to a feature not available in PostgreSQL
result_cast_maximum_cardinality
cardinal_number
Applies to a feature not available in PostgreSQL
result_cast_dtd_identifier
sql_identifier
Applies to a feature not available in PostgreSQL
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-schema.html postgresql-10-10.19/doc/src/sgml/html/infoschema-schema.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-schema.html 2021-05-10 20:58:13.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-schema.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.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
database user in the cluster, and that user naturally has all the
@@ -11,4 +11,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 -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-schemata.html postgresql-10-10.19/doc/src/sgml/html/infoschema-schemata.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-schemata.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-schemata.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.41. 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).
-
Table 36.39. schemata Columns
Name
Data Type
Description
catalog_name
sql_identifier
Name of the database that the schema is contained in (always the current database)
schema_name
sql_identifier
Name of the schema
schema_owner
sql_identifier
Name of the owner of the schema
default_character_set_catalog
sql_identifier
Applies to a feature not available in PostgreSQL
default_character_set_schema
sql_identifier
Applies to a feature not available in PostgreSQL
default_character_set_name
sql_identifier
Applies to a feature not available in PostgreSQL
sql_path
character_data
Applies to a feature not available in PostgreSQL
\ No newline at end of file
+
Table 36.39. schemata Columns
Name
Data Type
Description
catalog_name
sql_identifier
Name of the database that the schema is contained in (always the current database)
schema_name
sql_identifier
Name of the schema
schema_owner
sql_identifier
Name of the owner of the schema
default_character_set_catalog
sql_identifier
Applies to a feature not available in PostgreSQL
default_character_set_schema
sql_identifier
Applies to a feature not available in PostgreSQL
default_character_set_name
sql_identifier
Applies to a feature not available in PostgreSQL
sql_path
character_data
Applies to a feature not available in PostgreSQL
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-sequences.html postgresql-10-10.19/doc/src/sgml/html/infoschema-sequences.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-sequences.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-sequences.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.42. 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
having some privilege).
@@ -21,4 +21,4 @@
numeric_precision_radix.
start_value
character_data
The start value of the sequence
minimum_value
character_data
The minimum value of the sequence
maximum_value
character_data
The maximum value of the sequence
increment
character_data
The increment of the sequence
cycle_option
yes_or_no
YES if the sequence cycles, else NO
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 -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-sql-features.html postgresql-10-10.19/doc/src/sgml/html/infoschema-sql-features.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-sql-features.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-sql-features.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.43. sql_features
The table sql_features contains information
about which formal features defined in the SQL standard are
supported by PostgreSQL. This is the
same information that is presented in Appendix D.
@@ -8,4 +8,4 @@
current version of PostgreSQL, NO if not
is_verified_by
character_data
Always null, since the PostgreSQL development group does not
perform formal testing of feature conformance
-
comments
character_data
Possibly a comment about the supported status of the feature
\ No newline at end of file
+
comments
character_data
Possibly a comment about the supported status of the feature
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-sql-implementation-info.html postgresql-10-10.19/doc/src/sgml/html/infoschema-sql-implementation-info.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-sql-implementation-info.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-sql-implementation-info.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.44. 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
primarily intended for use in the context of the ODBC interface;
@@ -13,4 +13,4 @@
character_value
character_data
Value of the implementation information item, or null if the
value is contained in the column
integer_value
-
comments
character_data
Possibly a comment pertaining to the implementation information item
\ No newline at end of file
+
comments
character_data
Possibly a comment pertaining to the implementation information item
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-sql-languages.html postgresql-10-10.19/doc/src/sgml/html/infoschema-sql-languages.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-sql-languages.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-sql-languages.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.45. sql_languages
The table sql_languages contains one row for
each SQL language binding that is supported by
PostgreSQL.
PostgreSQL supports direct SQL and
@@ -17,4 +17,4 @@
sql_language_programming_language
character_data
The programming language, if the binding style is
EMBEDDED, else null. PostgreSQL only
supports the language C.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-sql-packages.html postgresql-10-10.19/doc/src/sgml/html/infoschema-sql-packages.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-sql-packages.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-sql-packages.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,9 +1,9 @@
-36.46. sql_packages
The table sql_packages contains information
about which feature packages defined in the SQL standard are
supported by PostgreSQL. Refer to Appendix D for background information on feature packages.
Table 36.44. sql_packages Columns
Name
Data Type
Description
feature_id
character_data
Identifier string of the package
feature_name
character_data
Descriptive name of the package
is_supported
yes_or_no
YES if the package is fully supported by the
current version of PostgreSQL, NO if not
is_verified_by
character_data
Always null, since the PostgreSQL development group does not
perform formal testing of feature conformance
-
comments
character_data
Possibly a comment about the supported status of the package
\ No newline at end of file
+
comments
character_data
Possibly a comment about the supported status of the package
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-sql-parts.html postgresql-10-10.19/doc/src/sgml/html/infoschema-sql-parts.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-sql-parts.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-sql-parts.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.47. sql_parts
The table sql_sizing contains information about
various size limits and maximum values in
PostgreSQL. This information is
primarily intended for use in the context of the ODBC interface;
@@ -10,4 +10,4 @@
Table 36.46. sql_sizing Columns
Name
Data Type
Description
sizing_id
cardinal_number
Identifier of the sizing item
sizing_name
character_data
Descriptive name of the sizing item
supported_value
cardinal_number
Value of the sizing item, or 0 if the size is unlimited or
cannot be determined, or null if the features for which the
sizing item is applicable are not supported
-
comments
character_data
Possibly a comment pertaining to the sizing item
\ No newline at end of file
+
comments
character_data
Possibly a comment pertaining to the sizing item
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-sql-sizing-profiles.html postgresql-10-10.19/doc/src/sgml/html/infoschema-sql-sizing-profiles.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-sql-sizing-profiles.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-sql-sizing-profiles.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,5 +1,5 @@
-36.49. sql_sizing_profiles
The table sql_sizing_profiles contains
information about the sql_sizing values that are
required by various profiles of the SQL standard. PostgreSQL does
not track any SQL profiles, so this table is empty.
@@ -7,4 +7,4 @@
if the profile places no limit on the sizing item, or null if
the profile does not require any of the features for which the
sizing item is applicable
-
comments
character_data
Possibly a comment pertaining to the sizing item within the profile
\ No newline at end of file
+
comments
character_data
Possibly a comment pertaining to the sizing item within the profile
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-table-constraints.html postgresql-10-10.19/doc/src/sgml/html/infoschema-table-constraints.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-table-constraints.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-table-constraints.html 2021-11-08 22:24:56.000000000 +0000
@@ -1,8 +1,8 @@
-36.50. table_constraints
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
combination of table, grantor, and grantee.
@@ -13,4 +13,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 -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-tables.html postgresql-10-10.19/doc/src/sgml/html/infoschema-tables.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-tables.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-tables.html 2021-11-08 22:24:57.000000000 +0000
@@ -1,5 +1,5 @@
-36.52. 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
owner or having some privilege).
@@ -18,4 +18,4 @@
is_insertable_into
yes_or_no
YES if the table is insertable into,
NO if not (Base tables are always insertable
into, views not necessarily.)
-
is_typed
yes_or_no
YES if the table is a typed table, NO if not
commit_action
character_data
Not yet implemented
\ No newline at end of file
+
is_typed
yes_or_no
YES if the table is a typed table, NO if not
commit_action
character_data
Not yet implemented
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-transforms.html postgresql-10-10.19/doc/src/sgml/html/infoschema-transforms.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-transforms.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-transforms.html 2021-11-08 22:24:57.000000000 +0000
@@ -1,5 +1,5 @@
-36.53. 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”
or “to SQL” function).
@@ -9,4 +9,4 @@
Instead, transforms are specific to a language. As a compromise, this
field contains the language the transform is for.
transform_type
character_data
FROM SQL or TO SQL
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-triggered-update-columns.html postgresql-10-10.19/doc/src/sgml/html/infoschema-triggered-update-columns.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-triggered-update-columns.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-triggered-update-columns.html 2021-11-08 22:24:57.000000000 +0000
@@ -1,5 +1,5 @@
-36.54. 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
columns. Triggers that do not specify a column list are not
@@ -8,4 +8,4 @@
SELECT on.
Table 36.52. triggered_update_columns Columns
Name
Data Type
Description
trigger_catalog
sql_identifier
Name of the database that contains the trigger (always the current database)
trigger_schema
sql_identifier
Name of the schema that contains the trigger
trigger_name
sql_identifier
Name of the trigger
event_object_catalog
sql_identifier
Name of the database that contains the table that the trigger
is defined on (always the current database)
-
event_object_schema
sql_identifier
Name of the schema that contains the table that the trigger is defined on
event_object_table
sql_identifier
Name of the table that the trigger is defined on
event_object_column
sql_identifier
Name of the column that the trigger is defined on
\ No newline at end of file
+
event_object_schema
sql_identifier
Name of the schema that contains the table that the trigger is defined on
event_object_table
sql_identifier
Name of the table that the trigger is defined on
event_object_column
sql_identifier
Name of the column that the trigger is defined on
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-triggers.html postgresql-10-10.19/doc/src/sgml/html/infoschema-triggers.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-triggers.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-triggers.html 2021-11-08 22:24:57.000000000 +0000
@@ -1,5 +1,5 @@
-36.55. 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.
Table 36.53. triggers Columns
Name
Data Type
Description
trigger_catalog
sql_identifier
Name of the database that contains the trigger (always the current database)
trigger_schema
sql_identifier
Name of the schema that contains the trigger
trigger_name
sql_identifier
Name of the trigger
event_manipulation
character_data
Event that fires the trigger (INSERT,
@@ -55,4 +55,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 -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-udt-privileges.html postgresql-10-10.19/doc/src/sgml/html/infoschema-udt-privileges.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-udt-privileges.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-udt-privileges.html 2021-11-08 22:24:57.000000000 +0000
@@ -1,9 +1,9 @@
-36.56. 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
each combination of type, grantor, and grantee. This view shows only
composite types (see under Section 36.58
for why); see
Section 36.57 for domain privileges.
-
Table 36.54. udt_privileges Columns
Name
Data Type
Description
grantor
sql_identifier
Name of the role that granted the privilege
grantee
sql_identifier
Name of the role that the privilege was granted to
udt_catalog
sql_identifier
Name of the database containing the type (always the current database)
udt_schema
sql_identifier
Name of the schema containing the type
udt_name
sql_identifier
Name of the type
privilege_type
character_data
Always TYPE USAGE
is_grantable
yes_or_no
YES if the privilege is grantable, NO if not
\ No newline at end of file
+
Table 36.54. udt_privileges Columns
Name
Data Type
Description
grantor
sql_identifier
Name of the role that granted the privilege
grantee
sql_identifier
Name of the role that the privilege was granted to
udt_catalog
sql_identifier
Name of the database containing the type (always the current database)
udt_schema
sql_identifier
Name of the schema containing the type
udt_name
sql_identifier
Name of the type
privilege_type
character_data
Always TYPE USAGE
is_grantable
yes_or_no
YES if the privilege is grantable, NO if not
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-usage-privileges.html postgresql-10-10.19/doc/src/sgml/html/infoschema-usage-privileges.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-usage-privileges.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-usage-privileges.html 2021-11-08 22:24:57.000000000 +0000
@@ -1,5 +1,5 @@
-36.57. 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.
In PostgreSQL, this currently applies to
@@ -15,4 +15,4 @@
the USAGE privilege. These are nonstandard and therefore
not visible in the information schema.
Table 36.55. usage_privileges Columns
Name
Data Type
Description
grantor
sql_identifier
Name of the role that granted the privilege
grantee
sql_identifier
Name of the role that the privilege was granted to
object_catalog
sql_identifier
Name of the database containing the object (always the current database)
object_schema
sql_identifier
Name of the schema containing the object, if applicable,
- else an empty string
object_name
sql_identifier
Name of the object
object_type
character_data
COLLATION or DOMAIN or FOREIGN DATA WRAPPER or FOREIGN SERVER or SEQUENCE
privilege_type
character_data
Always USAGE
is_grantable
yes_or_no
YES if the privilege is grantable, NO if not
\ No newline at end of file
+ else an empty string
object_name
sql_identifier
Name of the object
object_type
character_data
COLLATION or DOMAIN or FOREIGN DATA WRAPPER or FOREIGN SERVER or SEQUENCE
privilege_type
character_data
Always USAGE
is_grantable
yes_or_no
YES if the privilege is grantable, NO if not
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-user-defined-types.html postgresql-10-10.19/doc/src/sgml/html/infoschema-user-defined-types.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-user-defined-types.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-user-defined-types.html 2021-11-08 22:24:57.000000000 +0000
@@ -1,5 +1,5 @@
-36.58. 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
of being the owner or having some privilege).
@@ -14,4 +14,4 @@
extensions, are not shown here. For domains,
see Section 36.22 instead.
Table 36.56. user_defined_types Columns
Name
Data Type
Description
user_defined_type_catalog
sql_identifier
Name of the database that contains the type (always the current database)
user_defined_type_schema
sql_identifier
Name of the schema that contains the type
user_defined_type_name
sql_identifier
Name of the type
user_defined_type_category
character_data
Currently always STRUCTURED
-
is_instantiable
yes_or_no
Applies to a feature not available in PostgreSQL
is_final
yes_or_no
Applies to a feature not available in PostgreSQL
ordering_form
character_data
Applies to a feature not available in PostgreSQL
ordering_category
character_data
Applies to a feature not available in PostgreSQL
ordering_routine_catalog
sql_identifier
Applies to a feature not available in PostgreSQL
ordering_routine_schema
sql_identifier
Applies to a feature not available in PostgreSQL
ordering_routine_name
sql_identifier
Applies to a feature not available in PostgreSQL
reference_type
character_data
Applies to a feature not available in PostgreSQL
data_type
character_data
Applies to a feature not available in PostgreSQL
character_maximum_length
cardinal_number
Applies to a feature not available in PostgreSQL
character_octet_length
cardinal_number
Applies to a feature not available in PostgreSQL
character_set_catalog
sql_identifier
Applies to a feature not available in PostgreSQL
character_set_schema
sql_identifier
Applies to a feature not available in PostgreSQL
character_set_name
sql_identifier
Applies to a feature not available in PostgreSQL
collation_catalog
sql_identifier
Applies to a feature not available in PostgreSQL
collation_schema
sql_identifier
Applies to a feature not available in PostgreSQL
collation_name
sql_identifier
Applies to a feature not available in PostgreSQL
numeric_precision
cardinal_number
Applies to a feature not available in PostgreSQL
numeric_precision_radix
cardinal_number
Applies to a feature not available in PostgreSQL
numeric_scale
cardinal_number
Applies to a feature not available in PostgreSQL
datetime_precision
cardinal_number
Applies to a feature not available in PostgreSQL
interval_type
character_data
Applies to a feature not available in PostgreSQL
interval_precision
cardinal_number
Applies to a feature not available in PostgreSQL
source_dtd_identifier
sql_identifier
Applies to a feature not available in PostgreSQL
ref_dtd_identifier
sql_identifier
Applies to a feature not available in PostgreSQL
\ No newline at end of file
+
is_instantiable
yes_or_no
Applies to a feature not available in PostgreSQL
is_final
yes_or_no
Applies to a feature not available in PostgreSQL
ordering_form
character_data
Applies to a feature not available in PostgreSQL
ordering_category
character_data
Applies to a feature not available in PostgreSQL
ordering_routine_catalog
sql_identifier
Applies to a feature not available in PostgreSQL
ordering_routine_schema
sql_identifier
Applies to a feature not available in PostgreSQL
ordering_routine_name
sql_identifier
Applies to a feature not available in PostgreSQL
reference_type
character_data
Applies to a feature not available in PostgreSQL
data_type
character_data
Applies to a feature not available in PostgreSQL
character_maximum_length
cardinal_number
Applies to a feature not available in PostgreSQL
character_octet_length
cardinal_number
Applies to a feature not available in PostgreSQL
character_set_catalog
sql_identifier
Applies to a feature not available in PostgreSQL
character_set_schema
sql_identifier
Applies to a feature not available in PostgreSQL
character_set_name
sql_identifier
Applies to a feature not available in PostgreSQL
collation_catalog
sql_identifier
Applies to a feature not available in PostgreSQL
collation_schema
sql_identifier
Applies to a feature not available in PostgreSQL
collation_name
sql_identifier
Applies to a feature not available in PostgreSQL
numeric_precision
cardinal_number
Applies to a feature not available in PostgreSQL
numeric_precision_radix
cardinal_number
Applies to a feature not available in PostgreSQL
numeric_scale
cardinal_number
Applies to a feature not available in PostgreSQL
datetime_precision
cardinal_number
Applies to a feature not available in PostgreSQL
interval_type
character_data
Applies to a feature not available in PostgreSQL
interval_precision
cardinal_number
Applies to a feature not available in PostgreSQL
source_dtd_identifier
sql_identifier
Applies to a feature not available in PostgreSQL
ref_dtd_identifier
sql_identifier
Applies to a feature not available in PostgreSQL
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-user-mapping-options.html postgresql-10-10.19/doc/src/sgml/html/infoschema-user-mapping-options.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-user-mapping-options.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-user-mapping-options.html 2021-11-08 22:24:57.000000000 +0000
@@ -1,5 +1,5 @@
-36.59. 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
the corresponding foreign server (by way of being the owner or
@@ -11,4 +11,4 @@
is for PUBLIC and the current user is the
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
+ option.
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-user-mappings.html postgresql-10-10.19/doc/src/sgml/html/infoschema-user-mappings.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-user-mappings.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-user-mappings.html 2021-11-08 22:24:57.000000000 +0000
@@ -1,9 +1,9 @@
-36.60. 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
foreign server (by way of being the owner or having some
privilege).
Table 36.58. user_mappings Columns
Name
Data Type
Description
authorization_identifier
sql_identifier
Name of the user being mapped,
or PUBLIC if the mapping is public
foreign_server_catalog
sql_identifier
Name of the database that the foreign server used by this
- mapping is defined in (always the current database)
foreign_server_name
sql_identifier
Name of the foreign server used by this mapping
\ No newline at end of file
+ mapping is defined in (always the current database)
foreign_server_name
sql_identifier
Name of the foreign server used by this mapping
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-view-column-usage.html postgresql-10-10.19/doc/src/sgml/html/infoschema-view-column-usage.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-view-column-usage.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-view-column-usage.html 2021-11-08 22:24:57.000000000 +0000
@@ -1,5 +1,5 @@
-36.61. 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
column is only included if the table that contains the column is
@@ -12,4 +12,4 @@
column that is used by the view
table_name
sql_identifier
Name of the table that contains the column that is used by the
view
-
column_name
sql_identifier
Name of the column that is used by the view
\ No newline at end of file
+
column_name
sql_identifier
Name of the column that is used by the view
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-view-routine-usage.html postgresql-10-10.19/doc/src/sgml/html/infoschema-view-routine-usage.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-view-routine-usage.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-view-routine-usage.html 2021-11-08 22:24:57.000000000 +0000
@@ -1,8 +1,8 @@
-36.62. 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
defines the view). A routine is only included if that routine is
owned by a currently enabled role.
Table 36.60. view_routine_usage Columns
Name
Data Type
Description
table_catalog
sql_identifier
Name of the database containing the view (always the current database)
table_schema
sql_identifier
Name of the schema containing the view
table_name
sql_identifier
Name of the view
specific_catalog
sql_identifier
Name of the database containing the function (always the current database)
specific_schema
sql_identifier
Name of the schema containing the function
specific_name
sql_identifier
The “specific name” of the function. See Section 36.40 for more information.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-views.html postgresql-10-10.19/doc/src/sgml/html/infoschema-views.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-views.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-views.html 2021-11-08 22:24:57.000000000 +0000
@@ -1,5 +1,5 @@
-36.64. 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).
Table 36.62. views Columns
Name
Data Type
Description
table_catalog
sql_identifier
Name of the database that contains the view (always the current database)
table_schema
sql_identifier
Name of the schema that contains the view
table_name
sql_identifier
Name of the view
view_definition
character_data
Query expression defining the view (null if the view is not
@@ -18,4 +18,4 @@
DELETE trigger defined on it, NO if not
is_trigger_insertable_into
yes_or_no
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 -Nru postgresql-10-10.17/doc/src/sgml/html/infoschema-view-table-usage.html postgresql-10-10.19/doc/src/sgml/html/infoschema-view-table-usage.html
--- postgresql-10-10.17/doc/src/sgml/html/infoschema-view-table-usage.html 2021-05-10 20:58:14.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/infoschema-view-table-usage.html 2021-11-08 22:24:57.000000000 +0000
@@ -1,5 +1,5 @@
-36.63. 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
table is only included if that table is owned by a currently
@@ -10,4 +10,4 @@
table_schema
sql_identifier
Name of the schema that contains the table that is used by the
view
table_name
sql_identifier
Name of the table that is used by the view
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/installation.html postgresql-10-10.19/doc/src/sgml/html/installation.html
--- postgresql-10-10.17/doc/src/sgml/html/installation.html 2021-05-10 20:58:10.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/installation.html 2021-11-08 22:24:52.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 16. Installation from Source Code
This
chapter describes the installation of
PostgreSQL using the source code
distribution. (If you are installing a pre-packaged distribution,
@@ -7,4 +7,4 @@
chapter
and read the packager's instructions instead.)
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/installation-platform-notes.html postgresql-10-10.19/doc/src/sgml/html/installation-platform-notes.html
--- postgresql-10-10.17/doc/src/sgml/html/installation-platform-notes.html 2021-05-10 20:58:10.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/installation-platform-notes.html 2021-11-08 22:24:52.000000000 +0000
@@ -1,5 +1,5 @@
-16.7. Platform-specific Notes
This section documents additional platform-specific issues
regarding the installation and setup of PostgreSQL. Be sure to
read the installation instructions, and in
particular Section 16.2 as well. Also,
@@ -387,4 +387,4 @@
make: *** [postgres] Error 1
your DTrace installation is too old to handle probes in static
functions. You need Solaris 10u4 or newer.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/install-getsource.html postgresql-10-10.19/doc/src/sgml/html/install-getsource.html
--- postgresql-10-10.17/doc/src/sgml/html/install-getsource.html 2021-05-10 20:58:10.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/install-getsource.html 2021-11-08 22:24:52.000000000 +0000
@@ -1,19 +1,19 @@
-16.3. Getting The Source
The PostgreSQL 10.19 sources can be obtained from the
download section of our
website: https://www.postgresql.org/download/. You
- should get a file named postgresql-10.17.tar.gz
- or postgresql-10.17.tar.bz2. After
+ should get a file named postgresql-10.19.tar.gz
+ or postgresql-10.19.tar.bz2. After
you have obtained the file, unpack it:
-
(Use bunzip2 instead of gunzip if you
have the .bz2 file.)
This will create a directory
- postgresql-10.17 under the current directory
+ postgresql-10.19 under the current directory
with the PostgreSQL sources.
Change into that directory for the rest
of the installation procedure.
You can also get the source directly from the version control repository, see
Appendix I.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/install-post.html postgresql-10-10.19/doc/src/sgml/html/install-post.html
--- postgresql-10-10.17/doc/src/sgml/html/install-post.html 2021-05-10 20:58:10.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/install-post.html 2021-11-08 22:24:52.000000000 +0000
@@ -1,5 +1,5 @@
-16.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
not necessary include
@@ -74,4 +74,4 @@
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 -Nru postgresql-10-10.17/doc/src/sgml/html/install-procedure.html postgresql-10-10.19/doc/src/sgml/html/install-procedure.html
--- postgresql-10-10.17/doc/src/sgml/html/install-procedure.html 2021-05-10 20:58:10.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/install-procedure.html 2021-11-08 22:24:52.000000000 +0000
@@ -1,5 +1,5 @@
-16.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
default installation simply enter:
@@ -517,6 +517,10 @@
make world
The last line displayed should be:
PostgreSQL, contrib, and documentation successfully made. Ready to install.
+
If you want to build everything that can be built, including the
+ additional modules (contrib), but without
+ the documentation, type instead:
+
make world-bin
Regression Tests
If you want to test the newly built server before you install it,
you can run the regression tests at this point. The regression
tests are a test suite to verify that PostgreSQL
@@ -546,6 +550,8 @@
If you built the world above, type instead:
make install-world
This also installs the documentation.
+
If you built the world without the documentation above, type instead:
+
make install-world-bin
You can use make install-strip instead of
make install to strip the executable files and
libraries as they are installed. This will save some space. If
@@ -588,4 +594,4 @@
idea to do make distclean before reconfiguring and
rebuilding. Without this, your changes in configuration choices
might not propagate everywhere they need to.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/install-requirements.html postgresql-10-10.19/doc/src/sgml/html/install-requirements.html
--- postgresql-10-10.17/doc/src/sgml/html/install-requirements.html 2021-05-10 20:58:10.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/install-requirements.html 2021-11-08 22:24:52.000000000 +0000
@@ -1,5 +1,5 @@
-16.2. Requirements
In general, a modern Unix-compatible platform should be able to run
PostgreSQL.
The platforms that had received specific testing at the
time of release are listed in Section 16.6
@@ -166,4 +166,4 @@
run the regression tests you will temporarily need up to an extra
150 MB. Use the df command to check free disk
space.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/install-short.html postgresql-10-10.19/doc/src/sgml/html/install-short.html
--- postgresql-10-10.17/doc/src/sgml/html/install-short.html 2021-05-10 20:58:10.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/install-short.html 2021-11-08 22:24:52.000000000 +0000
@@ -1,5 +1,5 @@
-16.1. Short Version
./configure
make
su
make install
@@ -14,4 +14,4 @@
The long version is the rest of this
chapter.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-10-10.17/doc/src/sgml/html/install-windows-full.html postgresql-10-10.19/doc/src/sgml/html/install-windows-full.html
--- postgresql-10-10.17/doc/src/sgml/html/install-windows-full.html 2021-05-10 20:58:10.000000000 +0000
+++ postgresql-10-10.19/doc/src/sgml/html/install-windows-full.html 2021-11-08 22:24:52.000000000 +0000
@@ -1,6 +1,6 @@
17.1. Building with Visual C++ or the Microsoft Windows SDK
17.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,
Visual Studio Express or some versions of the
@@ -248,4 +248,4 @@
builddoc.bat. Note that this will actually run the
build twice, in order to generate the indexes. The generated HTML files
will be in doc\src\sgml.
-