This is a list of acronyms commonly used in the PostgreSQL
documentation and in discussions about PostgreSQL.
@@ -137,7 +137,7 @@
Pluggable
Authentication Modules
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/admin.html postgresql-15-15.9/doc/src/sgml/html/admin.html
--- postgresql-15-15.8/doc/src/sgml/html/admin.html 2024-08-05 20:21:53.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/admin.html 2024-11-11 23:01:05.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
@@ -23,4 +23,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
@@ -86,4 +86,4 @@
directory. The log_filename parameter must have its
default setting (postgresql-%Y-%m-%d_%H%M%S.log) to use this
function.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/amcheck.html postgresql-15-15.9/doc/src/sgml/html/amcheck.html
--- postgresql-15-15.8/doc/src/sgml/html/amcheck.html 2024-08-05 20:22:11.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/amcheck.html 2024-11-11 23:01:22.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 relations.
@@ -374,4 +374,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-15-15.8/doc/src/sgml/html/app-clusterdb.html postgresql-15-15.9/doc/src/sgml/html/app-clusterdb.html
--- postgresql-15-15.8/doc/src/sgml/html/app-clusterdb.html 2024-08-05 20:22:03.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/app-clusterdb.html 2024-11-11 23:01:15.000000000 +0000
@@ -1,5 +1,5 @@
-clusterdb
createuser creates a
new PostgreSQL user (or more precisely, a role).
Only superusers and users with CREATEROLE privilege can create
@@ -187,4 +187,4 @@
In the above example, the new password isn't actually echoed when typed,
but we show what was typed for clarity. As you see, the password is
encrypted before it is sent to the client.
-
dropdb destroys an existing
PostgreSQL database.
The user who executes this command must be a database
@@ -108,4 +108,4 @@
Database "demo" will be permanently deleted.
Are you sure? (y/n) yDROP DATABASE demo;
-
dropuser removes an existing
PostgreSQL user.
Only superusers and users with the CREATEROLE privilege can
@@ -100,4 +100,4 @@
Role "joe" will be permanently removed.
Are you sure? (y/n) yDROP ROLE joe;
-
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
@@ -105,4 +105,4 @@
ecpg prog1.pgc
cc -I/usr/local/pgsql/include -c prog1.c
cc -o prog1 prog1.o -L/usr/local/pgsql/lib -lecpg
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/app-initdb.html postgresql-15-15.9/doc/src/sgml/html/app-initdb.html
--- postgresql-15-15.8/doc/src/sgml/html/app-initdb.html 2024-08-05 20:22:04.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/app-initdb.html 2024-11-11 23:01:16.000000000 +0000
@@ -1,5 +1,5 @@
-initdb
pg_dumpall — extract a PostgreSQL database cluster into a script file
Synopsis
pg_dumpall [connection-option...] [option...]
Description
pg_dumpall is a utility for writing out
(“dumping”) all PostgreSQL databases
of a cluster into one script file. The script file contains
@@ -361,4 +361,4 @@
See Also
Check pg_dump for details on possible
error conditions.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/app-pg-isready.html postgresql-15-15.9/doc/src/sgml/html/app-pg-isready.html
--- postgresql-15-15.8/doc/src/sgml/html/app-pg-isready.html 2024-08-05 20:22:04.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/app-pg-isready.html 2024-11-11 23:01:15.000000000 +0000
@@ -1,5 +1,5 @@
-pg_isready
pg_isready — check the connection status of a PostgreSQL server
Synopsis
pg_isready [connection-option...] [option...]
Description
pg_isready is a utility for checking the connection
status of a PostgreSQL database server. The exit
status specifies the result of the connection check.
@@ -76,4 +76,4 @@
$echo $?2
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/app-pgamcheck.html postgresql-15-15.9/doc/src/sgml/html/app-pgamcheck.html
--- postgresql-15-15.8/doc/src/sgml/html/app-pgamcheck.html 2024-08-05 20:22:03.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/app-pgamcheck.html 2024-11-11 23:01:15.000000000 +0000
@@ -1,5 +1,5 @@
-pg_amcheck
pg_basebackup — take a base backup of a PostgreSQL cluster
Synopsis
pg_basebackup [option...]
Description
pg_basebackup is used to take a base backup of
a running PostgreSQL database cluster. The backup
is taken without affecting other clients of the database, and can be used
@@ -548,4 +548,4 @@
directory backup:
pg_checksums checks, enables or disables data
checksums in a PostgreSQL cluster. The server
must be shut down cleanly before running
@@ -72,4 +72,4 @@
enabling or disabling checksums, the cluster's data checksum configuration
remains unchanged, and pg_checksums can be
re-run to perform the same operation.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/app-pgconfig.html postgresql-15-15.9/doc/src/sgml/html/app-pgconfig.html
--- postgresql-15-15.8/doc/src/sgml/html/app-pgconfig.html 2024-08-05 20:22:04.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/app-pgconfig.html 2024-11-11 23:01:15.000000000 +0000
@@ -1,5 +1,5 @@
-pg_config
pg_config — retrieve information about the installed version of PostgreSQL
Synopsis
pg_config [option...]
Description
The pg_config utility prints configuration parameters
of the currently installed version of PostgreSQL. It is
intended, for example, to be used by software packages that want to interface
@@ -107,4 +107,4 @@
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-15-15.8/doc/src/sgml/html/app-pgcontroldata.html postgresql-15-15.9/doc/src/sgml/html/app-pgcontroldata.html
--- postgresql-15-15.8/doc/src/sgml/html/app-pgcontroldata.html 2024-08-05 20:22:04.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/app-pgcontroldata.html 2024-11-11 23:01:16.000000000 +0000
@@ -1,5 +1,5 @@
-pg_controldata
pg_controldata prints information initialized during
initdb, such as the catalog version.
It also shows information about write-ahead logging and checkpoint
@@ -20,4 +20,4 @@
Specifies whether to use color in diagnostic messages. Possible values
are always, auto and
never.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/app-pgdump.html postgresql-15-15.9/doc/src/sgml/html/app-pgdump.html
--- postgresql-15-15.8/doc/src/sgml/html/app-pgdump.html 2024-08-05 20:22:04.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/app-pgdump.html 2024-11-11 23:01:15.000000000 +0000
@@ -1,5 +1,5 @@
-pg_dump
pg_receivewal — stream write-ahead logs from a PostgreSQL server
Synopsis
pg_receivewal [option...]
Description
pg_receivewal is used to stream the write-ahead log
from a running PostgreSQL cluster. The write-ahead
log is streamed using the streaming replication protocol, and is written
@@ -246,4 +246,4 @@
/usr/local/pgsql/archive:
pg_resetwal clears the write-ahead log (WAL) and
optionally resets some other control information stored in the
pg_control file. This function is sometimes needed
@@ -166,4 +166,4 @@
pg_resetwal works only with servers of the same
major version.
-
pg_rewind is a tool for synchronizing a PostgreSQL cluster
with another copy of the same cluster, after the clusters' timelines have
diverged. A typical scenario is to bring an old primary server back online
@@ -214,4 +214,4 @@
When starting the target, PostgreSQL replays
all the required WAL, resulting in a data directory in a consistent
state.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/app-pgverifybackup.html postgresql-15-15.9/doc/src/sgml/html/app-pgverifybackup.html
--- postgresql-15-15.8/doc/src/sgml/html/app-pgverifybackup.html 2024-08-05 20:22:04.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/app-pgverifybackup.html 2024-11-11 23:01:15.000000000 +0000
@@ -1,5 +1,5 @@
-pg_verifybackup
pg_verifybackup — verify the integrity of a base backup of a
PostgreSQL cluster
Synopsis
pg_verifybackup [option...]
Description
pg_verifybackup is used to check the
integrity of a database cluster backup taken using
@@ -141,4 +141,4 @@
$pg_basebackup -h mydbserver -D /usr/local/pgsql/data$edit /usr/local/pgsql/data/note.to.self$pg_verifybackup --ignore=note.to.self --skip-checksums /usr/local/pgsql/data
-
$ psql testdb
-psql (15.8)
+psql (15.9)
Type "help" for help.
testdb=>
@@ -2725,7 +2725,7 @@
by appending a dash and the PostgreSQL
major or minor release identifier to the file name,
for example ~/.psqlrc-15 or
- ~/.psqlrc-15.8.
+ ~/.psqlrc-15.9.
The most specific version-matching file will be read in preference
to a non-version-specific file.
These version suffixes are added after determining the file path
@@ -2956,4 +2956,4 @@
2 | 202 | 204 | 206 | 208
1 | 101 | 102 | 103 | 104
(4 rows)
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/app-reindexdb.html postgresql-15-15.9/doc/src/sgml/html/app-reindexdb.html
--- postgresql-15-15.8/doc/src/sgml/html/app-reindexdb.html 2024-08-05 20:22:04.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/app-reindexdb.html 2024-11-11 23:01:16.000000000 +0000
@@ -1,5 +1,5 @@
-reindexdb
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/appendix-obsolete.html postgresql-15-15.9/doc/src/sgml/html/appendix-obsolete.html
--- postgresql-15-15.8/doc/src/sgml/html/appendix-obsolete.html 2024-08-05 20:22:13.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/appendix-obsolete.html 2024-11-11 23:01:24.000000000 +0000
@@ -1,8 +1,8 @@
-Appendix O. Obsolete or Renamed Features
Functionality is sometimes removed from PostgreSQL, feature, setting
and file names sometimes change, or documentation moves to different
places. This section directs users coming from old versions of the
documentation or from external links to the appropriate new location
for the information they need.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/appendixes.html postgresql-15-15.9/doc/src/sgml/html/appendixes.html
--- postgresql-15-15.8/doc/src/sgml/html/appendixes.html 2024-08-05 20:22:13.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/appendixes.html 2024-11-11 23:01:24.000000000 +0000
@@ -1,2 +1,2 @@
-Part VIII. Appendixes
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/applevel-consistency.html postgresql-15-15.9/doc/src/sgml/html/applevel-consistency.html
--- postgresql-15-15.8/doc/src/sgml/html/applevel-consistency.html 2024-08-05 20:21:50.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/applevel-consistency.html 2024-11-11 23:01:02.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
@@ -111,4 +111,4 @@
UPDATE, DELETE, or
MERGE), so it is possible to obtain locks explicitly
before the snapshot is frozen.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/archive-module-callbacks.html postgresql-15-15.9/doc/src/sgml/html/archive-module-callbacks.html
--- postgresql-15-15.8/doc/src/sgml/html/archive-module-callbacks.html 2024-08-05 20:21:57.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/archive-module-callbacks.html 2024-11-11 23:01:09.000000000 +0000
@@ -1,5 +1,5 @@
-51.2. Archive Module Callbacks
An archive library is loaded by dynamically loading a shared library with the
archive_library's name as the library base name. The
normal library search path is used to locate the library. To provide the
@@ -21,4 +21,4 @@
Only the archive_file_cb callback is required. The
others are optional.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/archive-modules.html postgresql-15-15.9/doc/src/sgml/html/archive-modules.html
--- postgresql-15-15.8/doc/src/sgml/html/archive-modules.html 2024-08-05 20:21:57.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/archive-modules.html 2024-11-11 23:01:09.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 51. Archive Modules
PostgreSQL provides infrastructure to create custom modules for continuous
archiving (see Section 26.3). While archiving via
a shell command (i.e., archive_command) is much
@@ -21,4 +21,4 @@
The contrib/basic_archive module contains a working
example, which demonstrates some useful techniques.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/arrays.html postgresql-15-15.9/doc/src/sgml/html/arrays.html
--- postgresql-15-15.8/doc/src/sgml/html/arrays.html 2024-08-05 20:21:47.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/arrays.html 2024-11-11 23:00:59.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, composite type, range type,
@@ -644,4 +644,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-15-15.8/doc/src/sgml/html/auth-bsd.html postgresql-15-15.9/doc/src/sgml/html/auth-bsd.html
--- postgresql-15-15.8/doc/src/sgml/html/auth-bsd.html 2024-08-05 20:21:51.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/auth-bsd.html 2024-11-11 23:01:03.000000000 +0000
@@ -1,5 +1,5 @@
-21.14. BSD Authentication
This authentication method operates similarly to
password except that it uses BSD Authentication
to verify the password. BSD Authentication is used only
@@ -18,4 +18,4 @@
operating system user running the server) must first be added to
the auth group. The auth group
exists by default on OpenBSD systems.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/auth-cert.html postgresql-15-15.9/doc/src/sgml/html/auth-cert.html
--- postgresql-15-15.8/doc/src/sgml/html/auth-cert.html 2024-08-05 20:21:51.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/auth-cert.html 2024-11-11 23:01:03.000000000 +0000
@@ -1,5 +1,5 @@
-21.12. Certificate Authentication
This authentication method uses SSL client certificates to perform
authentication. It is therefore only available for SSL connections;
see Section 19.9.2 for SSL configuration instructions.
@@ -22,4 +22,4 @@
cert authentication because cert
authentication is effectively trust authentication
with clientcert=verify-full.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/auth-delay.html postgresql-15-15.9/doc/src/sgml/html/auth-delay.html
--- postgresql-15-15.8/doc/src/sgml/html/auth-delay.html 2024-08-05 20:22:11.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/auth-delay.html 2024-11-11 23:01:22.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
@@ -25,4 +25,4 @@
auth_delay.milliseconds = '500'
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/auth-ident.html postgresql-15-15.9/doc/src/sgml/html/auth-ident.html
--- postgresql-15-15.8/doc/src/sgml/html/auth-ident.html 2024-08-05 20:21:51.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/auth-ident.html 2024-11-11 23:01:03.000000000 +0000
@@ -1,5 +1,5 @@
-21.8. Ident Authentication
The ident authentication method works by obtaining the client's
operating system user name from an ident server and using it as
the allowed database user name (with an optional user name mapping).
@@ -49,4 +49,4 @@
used when using the ident server with PostgreSQL,
since PostgreSQL does not have any way to decrypt the
returned string to determine the actual user name.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/auth-ldap.html postgresql-15-15.9/doc/src/sgml/html/auth-ldap.html
--- postgresql-15-15.8/doc/src/sgml/html/auth-ldap.html 2024-08-05 20:21:51.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/auth-ldap.html 2024-11-11 23:01:03.000000000 +0000
@@ -1,5 +1,5 @@
-21.10. LDAP Authentication
This authentication method operates similarly to
password except that it uses LDAP
as the password verification method. LDAP is used only to validate
@@ -187,4 +187,4 @@
Since LDAP often uses commas and spaces to separate the different
parts of a DN, it is often necessary to use double-quoted parameter
values when configuring LDAP options, as shown in the examples.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/auth-methods.html postgresql-15-15.9/doc/src/sgml/html/auth-methods.html
--- postgresql-15-15.8/doc/src/sgml/html/auth-methods.html 2024-08-05 20:21:51.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/auth-methods.html 2024-11-11 23:01:03.000000000 +0000
@@ -1,5 +1,5 @@
-21.3. Authentication Methods
This authentication method operates similarly to
password except that it uses PAM (Pluggable
Authentication Modules) as the authentication mechanism. The
@@ -28,4 +28,4 @@
will fail because the PostgreSQL server is started by a non-root
user. However, this is not an issue when PAM is configured to use
LDAP or other authentication methods.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/auth-password.html postgresql-15-15.9/doc/src/sgml/html/auth-password.html
--- postgresql-15-15.8/doc/src/sgml/html/auth-password.html 2024-08-05 20:21:51.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/auth-password.html 2024-11-11 23:01:03.000000000 +0000
@@ -1,5 +1,5 @@
-21.5. Password Authentication
There are several password-based authentication methods. These methods
operate similarly but differ in how the users' passwords are stored on the
server and how the password provided by a client is sent across the
@@ -77,4 +77,4 @@
in postgresql.conf, make all users set new passwords,
and change the authentication method specifications
in pg_hba.conf to scram-sha-256.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/auth-peer.html postgresql-15-15.9/doc/src/sgml/html/auth-peer.html
--- postgresql-15-15.8/doc/src/sgml/html/auth-peer.html 2024-08-05 20:21:51.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/auth-peer.html 2024-11-11 23:01:03.000000000 +0000
@@ -1,5 +1,5 @@
-21.9. Peer Authentication
The peer authentication method works by obtaining the client's
operating system user name from the kernel and using it as the
allowed database user name (with optional user name mapping). This
@@ -18,4 +18,4 @@
most flavors of BSD including
macOS,
and Solaris.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/auth-pg-hba-conf.html postgresql-15-15.9/doc/src/sgml/html/auth-pg-hba-conf.html
--- postgresql-15-15.8/doc/src/sgml/html/auth-pg-hba-conf.html 2024-08-05 20:21:51.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/auth-pg-hba-conf.html 2024-11-11 23:01:03.000000000 +0000
@@ -1,5 +1,5 @@
-21.1. The pg_hba.conf File
Client authentication is controlled by a configuration file,
which traditionally is named
pg_hba.conf and is stored in the database
@@ -489,4 +489,4 @@
# The database column can also use lists and file names:
local db1,db2,@demodbs all md5
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/auth-radius.html postgresql-15-15.9/doc/src/sgml/html/auth-radius.html
--- postgresql-15-15.8/doc/src/sgml/html/auth-radius.html 2024-08-05 20:21:51.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/auth-radius.html 2024-11-11 23:01:03.000000000 +0000
@@ -1,5 +1,5 @@
-21.11. RADIUS Authentication
This authentication method operates similarly to
password except that it uses RADIUS
as the password verification method. RADIUS is used only to validate
@@ -62,4 +62,4 @@
When trust authentication is specified,
PostgreSQL assumes that anyone who can
connect to the server is authorized to access the database with
@@ -34,4 +34,4 @@
to the server by the pg_hba.conf lines that specify
trust. It is seldom reasonable to use trust
for any TCP/IP connections other than those from localhost (127.0.0.1).
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/auth-username-maps.html postgresql-15-15.9/doc/src/sgml/html/auth-username-maps.html
--- postgresql-15-15.8/doc/src/sgml/html/auth-username-maps.html 2024-08-05 20:21:51.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/auth-username-maps.html 2024-11-11 23:01:03.000000000 +0000
@@ -1,5 +1,5 @@
-21.2. User Name Maps
When using an external authentication system such as Ident or GSSAPI,
the name of the operating system user that initiated the connection
might not be the same as the database user (role) that is to be used.
@@ -99,4 +99,4 @@
omicron robert bob
# bryanh can also connect as guest1
omicron bryanh guest1
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/auto-explain.html postgresql-15-15.9/doc/src/sgml/html/auto-explain.html
--- postgresql-15-15.8/doc/src/sgml/html/auto-explain.html 2024-08-05 20:22:11.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/auto-explain.html 2024-11-11 23:01:22.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
@@ -186,4 +186,4 @@
Filter: indisunique
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/backup-dump.html postgresql-15-15.9/doc/src/sgml/html/backup-dump.html
--- postgresql-15-15.8/doc/src/sgml/html/backup-dump.html 2024-08-05 20:21:52.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/backup-dump.html 2024-11-11 23:01:04.000000000 +0000
@@ -1,5 +1,5 @@
-26.1. SQL Dump
The idea behind this dump method is to generate a file with SQL
commands that, when fed back to the server, will recreate the
database in the same state as it was at the time of the dump.
@@ -244,4 +244,4 @@
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-15-15.8/doc/src/sgml/html/backup-file.html postgresql-15-15.9/doc/src/sgml/html/backup-file.html
--- postgresql-15-15.8/doc/src/sgml/html/backup-file.html 2024-08-05 20:21:52.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/backup-file.html 2024-11-11 23:01:04.000000000 +0000
@@ -1,5 +1,5 @@
-26.2. File System Level Backup
An alternative backup strategy is to directly copy the files that
PostgreSQL uses to store the data in the database;
Section 19.2 explains where these files
@@ -88,4 +88,4 @@
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-15-15.8/doc/src/sgml/html/backup-manifest-files.html postgresql-15-15.9/doc/src/sgml/html/backup-manifest-files.html
--- postgresql-15-15.8/doc/src/sgml/html/backup-manifest-files.html 2024-08-05 20:22:08.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/backup-manifest-files.html 2024-11-11 23:01:19.000000000 +0000
@@ -1,5 +1,5 @@
-76.2. Backup Manifest File Object
The object which describes a single file contains either a
Path key or an Encoded-Path key.
Normally, the Path key will be present. The
@@ -36,4 +36,4 @@
Checksum
The checksum computed for this file, stored as a series of
hexadecimal characters, two for each byte of the checksum.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/backup-manifest-format.html postgresql-15-15.9/doc/src/sgml/html/backup-manifest-format.html
--- postgresql-15-15.8/doc/src/sgml/html/backup-manifest-format.html 2024-08-05 20:22:08.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/backup-manifest-format.html 2024-11-11 23:01:19.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 76. Backup Manifest Format
The backup manifest generated by pg_basebackup is
primarily intended to permit the backup to be verified using
pg_verifybackup. However, it is
@@ -13,4 +13,4 @@
supported server encoding. There is no similar exception for backup
manifests.) The JSON document is always an object; the keys that are present
in this object are described in the next section.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/backup-manifest-toplevel.html postgresql-15-15.9/doc/src/sgml/html/backup-manifest-toplevel.html
--- postgresql-15-15.8/doc/src/sgml/html/backup-manifest-toplevel.html 2024-08-05 20:22:08.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/backup-manifest-toplevel.html 2024-11-11 23:01:19.000000000 +0000
@@ -1,5 +1,5 @@
-76.1. Backup Manifest Top-level Object
The backup manifest JSON document contains the following keys.
PostgreSQL-Backup-Manifest-Version
The associated value is always the integer 1.
@@ -22,4 +22,4 @@
is significantly more expensive than a CRC32C checksum, the manifest
should normally be small enough that the extra computation won't matter
very much.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/backup-manifest-wal-ranges.html postgresql-15-15.9/doc/src/sgml/html/backup-manifest-wal-ranges.html
--- postgresql-15-15.8/doc/src/sgml/html/backup-manifest-wal-ranges.html 2024-08-05 20:22:08.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/backup-manifest-wal-ranges.html 2024-11-11 23:01:19.000000000 +0000
@@ -1,5 +1,5 @@
-76.3. Backup Manifest WAL Range Object
The object which describes a WAL range always has three keys:
Timeline
The timeline for this range of WAL records, as an integer.
@@ -19,4 +19,4 @@
upstream promotion, it is possible for multiple ranges to be present, each
with a different timeline. There will never be multiple WAL ranges present
for the same timeline.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/backup.html postgresql-15-15.9/doc/src/sgml/html/backup.html
--- postgresql-15-15.8/doc/src/sgml/html/backup.html 2024-08-05 20:21:52.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/backup.html 2024-11-11 23:01:04.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 26. Backup and Restore
As with everything that contains valuable data, PostgreSQL
databases should be backed up regularly. While the procedure is
essentially simple, it is important to have a clear understanding of
@@ -10,4 +10,4 @@
SQL dump
File system level backup
Continuous archiving
Each has its own strengths and weaknesses; each is discussed in turn
in the following sections.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/basebackup-to-shell.html postgresql-15-15.9/doc/src/sgml/html/basebackup-to-shell.html
--- postgresql-15-15.8/doc/src/sgml/html/basebackup-to-shell.html 2024-08-05 20:22:11.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/basebackup-to-shell.html 2024-11-11 23:01:22.000000000 +0000
@@ -1,5 +1,5 @@
-F.5. basebackup_to_shell
basebackup_to_shell adds a custom basebackup target
called shell. This makes it possible to run
pg_basebackup --target=shell or, depending on how this
@@ -40,4 +40,4 @@
the shell backup target.
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/basic-archive.html postgresql-15-15.9/doc/src/sgml/html/basic-archive.html
--- postgresql-15-15.8/doc/src/sgml/html/basic-archive.html 2024-08-05 20:22:11.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/basic-archive.html 2024-11-11 23:01:22.000000000 +0000
@@ -1,5 +1,5 @@
-F.6. basic_archive
basic_archive is an example of an archive module. This
module copies completed WAL segment files to the specified directory. This
may not be especially useful, but it can serve as a starting point for
@@ -35,4 +35,4 @@
doing so.
F.6.3. Author
Nathan Bossart
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/bgworker.html postgresql-15-15.9/doc/src/sgml/html/bgworker.html
--- postgresql-15-15.8/doc/src/sgml/html/bgworker.html 2024-08-05 20:21:57.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/bgworker.html 2024-11-11 23:01:09.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 48. Background Worker Processes
PostgreSQL can be extended to run user-supplied code in separate processes.
Such processes are started, stopped and monitored by postgres,
which permits them to have a lifetime closely linked to the server's status.
@@ -228,4 +228,4 @@
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-15-15.8/doc/src/sgml/html/biblio.html postgresql-15-15.9/doc/src/sgml/html/biblio.html
--- postgresql-15-15.8/doc/src/sgml/html/biblio.html 2024-08-05 20:22:13.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/biblio.html 2024-11-11 23:01:24.000000000 +0000
@@ -1,5 +1,5 @@
-Bibliography
[ston90a] “The
implementation of POSTGRES”. M.Stonebraker, L. A.Rowe, and M.Hirohama. Transactions on Knowledge and Data Engineering 2(1). IEEE. March 1990.
\ No newline at end of file
+ Rules, Procedures, Caching and Views in Database Systems”. M.Stonebraker, A.Jhingran, J.Goh, and S.Potamianos. ACM-SIGMOD Conference on Management of Data, June 1990.
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/bki-commands.html postgresql-15-15.9/doc/src/sgml/html/bki-commands.html
--- postgresql-15-15.8/doc/src/sgml/html/bki-commands.html 2024-08-05 20:22:08.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/bki-commands.html 2024-11-11 23:01:19.000000000 +0000
@@ -1,5 +1,5 @@
-74.4. BKI Commands
The following sequence of commands will create the table
test_table with OID 420, having three columns
oid, cola and colb
@@ -12,4 +12,4 @@
insert ( 422 2 _null_ )
close test_table
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/bki-format.html postgresql-15-15.9/doc/src/sgml/html/bki-format.html
--- postgresql-15-15.8/doc/src/sgml/html/bki-format.html 2024-08-05 20:22:08.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/bki-format.html 2024-11-11 23:01:19.000000000 +0000
@@ -1,5 +1,5 @@
-74.3. BKI File Format
This section describes how the PostgreSQL
backend interprets BKI files. This description
will be easier to understand if the postgres.bki
@@ -16,4 +16,4 @@
single-quoted strings. Everything is case sensitive.
Lines starting with # are ignored.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/bki-structure.html postgresql-15-15.9/doc/src/sgml/html/bki-structure.html
--- postgresql-15-15.8/doc/src/sgml/html/bki-structure.html 2024-08-05 20:22:08.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/bki-structure.html 2024-11-11 23:01:19.000000000 +0000
@@ -1,5 +1,5 @@
-74.5. Structure of the Bootstrap BKI File
The open command cannot be used until the tables it uses
exist and have entries for the table that is to be opened.
(These minimum tables are pg_class,
@@ -39,4 +39,4 @@
There are doubtless other, undocumented ordering dependencies.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/bki.html postgresql-15-15.9/doc/src/sgml/html/bki.html
--- postgresql-15-15.8/doc/src/sgml/html/bki.html 2024-08-05 20:22:08.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/bki.html 2024-11-11 23:01:19.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 74. System Catalog Declarations and Initial Contents
Chapter 74. System Catalog Declarations and Initial Contents
PostgreSQL uses many different system catalogs
to keep track of the existence and properties of database objects, such as
tables and functions. Physically there is no difference between a system
@@ -53,4 +53,4 @@
and/or initial data files. The rest of this chapter gives some
information about that, and for completeness describes
the BKI file format.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/bloom.html postgresql-15-15.9/doc/src/sgml/html/bloom.html
--- postgresql-15-15.8/doc/src/sgml/html/bloom.html 2024-08-05 20:22:11.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/bloom.html 2024-11-11 23:01:22.000000000 +0000
@@ -1,5 +1,5 @@
-F.7. bloom
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/bookindex.html postgresql-15-15.9/doc/src/sgml/html/bookindex.html
--- postgresql-15-15.8/doc/src/sgml/html/bookindex.html 2024-08-05 20:22:14.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/bookindex.html 2024-11-11 23:01:25.000000000 +0000
@@ -1,5 +1,5 @@
-Index
The core PostgreSQL distribution
includes the BRIN operator classes shown in
Table 71.1.
@@ -43,4 +43,4 @@
minmax indexes to summarize a block range. Each value may represent
either a point, or a boundary of an interval. Values must be between
8 and 256, and the default value is 32.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/brin-extensibility.html postgresql-15-15.9/doc/src/sgml/html/brin-extensibility.html
--- postgresql-15-15.8/doc/src/sgml/html/brin-extensibility.html 2024-08-05 20:22:08.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/brin-extensibility.html 2024-11-11 23:01:19.000000000 +0000
@@ -1,5 +1,5 @@
-71.3. Extensibility
The BRIN interface has a high level of abstraction,
requiring the access method implementer only to implement the semantics
of the data type being accessed. The BRIN layer
@@ -165,4 +165,4 @@
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-15-15.8/doc/src/sgml/html/brin-intro.html postgresql-15-15.9/doc/src/sgml/html/brin-intro.html
--- postgresql-15-15.8/doc/src/sgml/html/brin-intro.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/brin-intro.html 2024-11-11 23:01:19.000000000 +0000
@@ -1,5 +1,5 @@
-71.1. Introduction
BRIN stands for Block Range Index.
BRIN is designed for handling very large tables
in which certain columns have some natural correlation with their
@@ -96,4 +96,4 @@
which is useful when the index tuple is no longer a very good
representation because the existing values have changed.
See Section 9.27.8 for details.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/brin.html postgresql-15-15.9/doc/src/sgml/html/brin.html
--- postgresql-15-15.8/doc/src/sgml/html/brin.html 2024-08-05 20:22:08.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/brin.html 2024-11-11 23:01:19.000000000 +0000
@@ -1,2 +1,2 @@
-Chapter 71. BRIN Indexes
As shown in Table 38.3, a btree operator
class must provide five comparison operators,
<,
@@ -115,4 +115,4 @@
data types. The extensions to three or more data types within a family
are not strictly required by the btree index mechanism itself, but the
planner relies on them for optimization purposes.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/btree-gin.html postgresql-15-15.9/doc/src/sgml/html/btree-gin.html
--- postgresql-15-15.8/doc/src/sgml/html/btree-gin.html 2024-08-05 20:22:11.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/btree-gin.html 2024-11-11 23:01:22.000000000 +0000
@@ -1,5 +1,5 @@
-F.8. btree_gin
btree_gin provides sample GIN operator classes that
implement B-tree equivalent behavior for the data types
int2, int4, int8, float4,
@@ -35,4 +35,4 @@
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-15-15.8/doc/src/sgml/html/btree-gist.html postgresql-15-15.9/doc/src/sgml/html/btree-gist.html
--- postgresql-15-15.8/doc/src/sgml/html/btree-gist.html 2024-08-05 20:22:11.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/btree-gist.html 2024-11-11 23:01:22.000000000 +0000
@@ -1,5 +1,5 @@
-F.9. btree_gist
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/btree-implementation.html postgresql-15-15.9/doc/src/sgml/html/btree-implementation.html
--- postgresql-15-15.8/doc/src/sgml/html/btree-implementation.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/btree-implementation.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-67.4. Implementation
This section covers B-Tree index implementation details that may be
of use to advanced users. See
src/backend/access/nbtree/README in the source
@@ -251,4 +251,4 @@
INCLUDE indexes can never use deduplication.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/btree-intro.html postgresql-15-15.9/doc/src/sgml/html/btree-intro.html
--- postgresql-15-15.8/doc/src/sgml/html/btree-intro.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/btree-intro.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-67.1. Introduction
PostgreSQL includes an implementation of the
standard btree (multi-way balanced tree) index data
structure. Any data type that can be sorted into a well-defined linear
@@ -14,4 +14,4 @@
some features that go beyond what would be needed just to support btree
indexes, and parts of the system that are quite distant from the
btree AM make use of them.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/btree-support-funcs.html postgresql-15-15.9/doc/src/sgml/html/btree-support-funcs.html
--- postgresql-15-15.8/doc/src/sgml/html/btree-support-funcs.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/btree-support-funcs.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-67.3. B-Tree Support Functions
As shown in Table 38.9, btree defines
one required and four optional support functions. The five
user-defined methods are:
@@ -288,4 +288,4 @@
access method. Nevertheless, this support function was added to B-tree
for uniformity, and will probably find uses during further
evolution of B-tree in PostgreSQL.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/btree.html postgresql-15-15.9/doc/src/sgml/html/btree.html
--- postgresql-15-15.8/doc/src/sgml/html/btree.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/btree.html 2024-11-11 23:01:19.000000000 +0000
@@ -1,2 +1,2 @@
-Chapter 67. B-Tree Indexes
When you find a bug in PostgreSQL we want to
hear about it. Your bug reports play an important part in making
PostgreSQL more reliable because even the utmost
@@ -154,7 +154,7 @@
subversion the package might have. If you are talking about a Git
snapshot, mention that, including the commit hash.
- If your version is older than 15.8 we will almost certainly
+ If your version is older than 15.9 we will almost certainly
tell you to upgrade. There are many bug fixes and improvements
in each new release, so it is quite possible that a bug you have
encountered in an older release of PostgreSQL
@@ -245,4 +245,4 @@
will be some delay before the email is delivered. If you wish to subscribe
to the lists, please visit
https://lists.postgresql.org/ for instructions.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-aggregate.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-aggregate.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-aggregate.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-aggregate.html 2024-11-11 23:01:16.000000000 +0000
@@ -1,5 +1,5 @@
-53.2. pg_aggregate
The catalog pg_aggregate stores information about
aggregate functions. An aggregate function is a function that
operates on a set of values (typically one column from each row
@@ -167,4 +167,4 @@
command. See Section 38.12 for more information about
writing aggregate functions and the meaning of the transition
functions, etc.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-am.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-am.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-am.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-am.html 2024-11-11 23:01:16.000000000 +0000
@@ -1,5 +1,5 @@
-53.3. pg_am
The catalog pg_am stores information about
relation access methods. There is one row for each access method supported
by the system.
@@ -41,4 +41,4 @@
However, pg_index_column_has_property() and related
functions have been added to allow SQL queries to inspect index access
method properties; see Table 9.71.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-amop.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-amop.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-amop.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-amop.html 2024-11-11 23:01:16.000000000 +0000
@@ -1,5 +1,5 @@
-53.4. pg_amop
The catalog pg_amop stores information about
operators associated with access method operator families. There is one
row for each operator that is a member of an operator family. A family
@@ -101,4 +101,4 @@
amoplefttype and amoprighttype must match
the oprleft and oprright fields of the
referenced pg_operator entry.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-amproc.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-amproc.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-amproc.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-amproc.html 2024-11-11 23:01:16.000000000 +0000
@@ -1,5 +1,5 @@
-53.5. pg_amproc
The catalog pg_amproc stores information about
support functions associated with access method operator families. There
is one row for each support function belonging to an operator family.
@@ -52,4 +52,4 @@
an index, which are those with amproclefttype and
amprocrighttype both equal to the index operator class's
opcintype.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-attrdef.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-attrdef.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-attrdef.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-attrdef.html 2024-11-11 23:01:16.000000000 +0000
@@ -1,5 +1,5 @@
-53.6. pg_attrdef
The catalog pg_attrdef stores column default
values. The main information about columns is stored in
pg_attribute.
@@ -34,4 +34,4 @@
The column default value, in nodeToString()
representation. Use pg_get_expr(adbin, adrelid) to
convert it to an SQL expression.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-attribute.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-attribute.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-attribute.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-attribute.html 2024-11-11 23:01:16.000000000 +0000
@@ -1,5 +1,5 @@
-53.7. pg_attribute
The catalog pg_attribute stores information about
table columns. There will be exactly one
pg_attribute row for every column in every
@@ -208,4 +208,4 @@
later dropped, and so there is no pg_type row anymore.
attlen and the other fields can be used
to interpret the contents of a row of the table.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-auth-members.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-auth-members.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-auth-members.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-auth-members.html 2024-11-11 23:01:16.000000000 +0000
@@ -1,5 +1,5 @@
-53.9. pg_auth_members
The catalog pg_auth_members shows the membership
relations between roles. Any non-circular set of relationships is allowed.
@@ -37,4 +37,4 @@
True if member can grant membership in
roleid to others
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-authid.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-authid.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-authid.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-authid.html 2024-11-11 23:01:16.000000000 +0000
@@ -1,5 +1,5 @@
-53.8. pg_authid
The catalog pg_authid contains information about
database authorization identifiers (roles). A role subsumes the concepts
of “users” and “groups”. A user is essentially just a
@@ -110,4 +110,4 @@
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-15-15.8/doc/src/sgml/html/catalog-pg-cast.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-cast.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-cast.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-cast.html 2024-11-11 23:01:16.000000000 +0000
@@ -1,5 +1,5 @@
-53.10. pg_cast
The catalog pg_cast stores data type conversion
paths, both built-in and user-defined.
@@ -83,4 +83,4 @@
coercion in a single step. When no such entry is available, coercion
to a type that uses a type modifier involves two steps, one to
convert between data types and a second to apply the modifier.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-class.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-class.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-class.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-class.html 2024-11-11 23:01:16.000000000 +0000
@@ -1,5 +1,5 @@
-53.11. pg_class
The catalog pg_class describes tables and
other objects that have columns or are otherwise similar to a
table. This includes indexes (but see also pg_index),
@@ -264,4 +264,4 @@
DROP INDEX. Instead, VACUUM clears
relhasindex if it finds the table has no indexes. This
arrangement avoids race conditions and improves concurrency.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-collation.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-collation.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-collation.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-collation.html 2024-11-11 23:01:16.000000000 +0000
@@ -1,5 +1,5 @@
-53.12. pg_collation
The catalog pg_collation describes the
available collations, which are essentially mappings from an SQL
name to operating system locale categories.
@@ -90,4 +90,4 @@
collations whose encoding does not match the database encoding,
since they could match the encodings of databases later cloned from
template0. This would currently have to be done manually.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-constraint.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-constraint.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-constraint.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-constraint.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.13. pg_constraint
The catalog pg_constraint stores check, primary
key, unique, foreign key, and exclusion constraints on tables.
(Column constraints are not treated specially. Every column constraint is
@@ -203,4 +203,4 @@
pg_class.relchecks needs to agree with the
number of check-constraint entries found in this table for each
relation.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-conversion.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-conversion.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-conversion.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-conversion.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.14. pg_conversion
The catalog pg_conversion describes
encoding conversion functions. See CREATE CONVERSION
for more information.
@@ -53,4 +53,4 @@
True if this is the default conversion
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-database.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-database.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-database.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-database.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.15. pg_database
The catalog pg_database stores information about
the available databases. Databases are created with the CREATE DATABASE command.
Consult Chapter 23 for details about the meaning
@@ -121,4 +121,4 @@
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-db-role-setting.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-db-role-setting.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-db-role-setting.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-db-role-setting.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.16. pg_db_role_setting
The catalog pg_db_role_setting records the default
values that have been set for run-time configuration variables,
for each role and database combination.
@@ -30,4 +30,4 @@
Defaults for run-time configuration variables
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-default-acl.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-default-acl.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-default-acl.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-default-acl.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.17. pg_default_acl
The catalog pg_default_acl stores initial
privileges to be assigned to newly created objects.
Table 53.17. pg_default_acl Columns
@@ -55,4 +55,4 @@
not whatever might be in pg_default_acl
at the moment. pg_default_acl is only consulted during
object creation.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-depend.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-depend.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-depend.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-depend.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.18. pg_depend
The catalog pg_depend records the dependency
relationships between database objects. This information allows
DROP commands to find which other objects must be dropped
@@ -172,4 +172,4 @@
a NORMAL dependency on the numeric
data type, but no such entry actually appears
in pg_depend.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-description.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-description.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-description.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-description.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.19. pg_description
The catalog pg_description stores optional descriptions
(comments) for each database object. Descriptions can be manipulated
with the COMMENT command and viewed with
@@ -40,4 +40,4 @@
Arbitrary text that serves as the description of this object
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-enum.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-enum.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-enum.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-enum.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.20. pg_enum
The pg_enum catalog contains entries
showing the values and labels for each enum type. The
internal representation of a given enum value is actually the OID
@@ -46,4 +46,4 @@
negative or fractional values of enumsortorder.
The only requirement on these values is that they be correctly
ordered and unique within each enum type.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-event-trigger.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-event-trigger.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-event-trigger.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-event-trigger.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.21. pg_event_trigger
The catalog pg_extension stores information
about the installed extensions. See Section 38.17
for details about extensions.
@@ -62,4 +62,4 @@
objects. If extrelocatable is true, then
this schema must in fact contain all schema-qualifiable objects
belonging to the extension.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-foreign-data-wrapper.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-foreign-data-wrapper.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-foreign-data-wrapper.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-foreign-data-wrapper.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.23. pg_foreign_data_wrapper
The catalog pg_foreign_data_wrapper stores
foreign-data wrapper definitions. A foreign-data wrapper is the
mechanism by which external data, residing on foreign servers, is
@@ -53,4 +53,4 @@
Foreign-data wrapper specific options, as “keyword=value” strings
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-foreign-server.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-foreign-server.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-foreign-server.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-foreign-server.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.24. pg_foreign_server
The catalog pg_foreign_server stores
foreign server definitions. A foreign server describes a source
of external data, such as a remote server. Foreign
@@ -51,4 +51,4 @@
Foreign server specific options, as “keyword=value” strings
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-foreign-table.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-foreign-table.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-foreign-table.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-foreign-table.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.25. pg_foreign_table
The catalog pg_foreign_table contains
auxiliary information about foreign tables. A foreign table is
primarily represented by a
@@ -29,4 +29,4 @@
Foreign table options, as “keyword=value” strings
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-index.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-index.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-index.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-index.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.26. pg_index
The catalog pg_index contains part of the information
about indexes. The rest is mostly in
pg_class.
@@ -160,4 +160,4 @@
Expression tree (in nodeToString()
representation) for partial index predicate. Null if not a
partial index.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-inherits.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-inherits.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-inherits.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-inherits.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.27. pg_inherits
The catalog pg_inherits records information about
table and index inheritance hierarchies. There is one entry for each direct
parent-child table or index relationship in the database. (Indirect
@@ -38,4 +38,4 @@
true for a partition that is in the process of
being detached; false otherwise.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-init-privs.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-init-privs.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-init-privs.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-init-privs.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.28. pg_init_privs
The catalog pg_init_privs records information about
the initial privileges of objects in the system. There is one entry
for each object in the database which has a non-default (non-NULL)
@@ -58,4 +58,4 @@
The initial access privileges; see
Section 5.7 for details
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-language.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-language.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-language.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-language.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.29. pg_language
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-largeobject-metadata.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-largeobject-metadata.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-largeobject-metadata.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-largeobject-metadata.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.31. pg_largeobject_metadata
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-largeobject.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-largeobject.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-largeobject.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-largeobject.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.30. pg_largeobject
The catalog pg_largeobject holds the data making up
“large objects”. A large object is identified by an OID
assigned when it is created. Each large object is broken into
@@ -45,4 +45,4 @@
allows sparse storage: pages might be missing, and might be shorter than
LOBLKSIZE bytes even if they are not the last page of the object.
Missing regions within a large object read as zeroes.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-namespace.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-namespace.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-namespace.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-namespace.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.32. pg_namespace
The catalog pg_namespace stores namespaces.
A namespace is the structure underlying SQL schemas: each namespace
can have a separate collection of relations, types, etc. without name
@@ -30,4 +30,4 @@
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-opclass.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-opclass.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-opclass.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-opclass.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.33. pg_opclass
The catalog pg_opclass defines
index access method operator classes. Each operator class defines
semantics for index columns of a particular data type and a particular
@@ -72,4 +72,4 @@
Also, there must be no more than one pg_opclass
row having opcdefault true for any given combination of
opcmethod and opcintype.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-operator.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-operator.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-operator.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-operator.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.34. pg_operator
The catalog pg_operator stores information about operators.
See CREATE OPERATOR
and Section 38.14 for more information.
@@ -98,4 +98,4 @@
Join selectivity estimation function for this operator
(zero if none)
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-opfamily.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-opfamily.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-opfamily.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-opfamily.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.35. pg_opfamily
The catalog pg_opfamily defines operator families.
Each operator family is a collection of operators and associated
support routines that implement the semantics specified for a particular
@@ -50,4 +50,4 @@
pg_amproc,
and
pg_opclass.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-parameter-acl.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-parameter-acl.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-parameter-acl.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-parameter-acl.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.36. pg_parameter_acl
The catalog pg_parameter_acl records configuration
parameters for which privileges have been granted to one or more roles.
No entry is made for parameters that have default privileges.
@@ -28,4 +28,4 @@
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-partitioned-table.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-partitioned-table.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-partitioned-table.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-partitioned-table.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.37. pg_partitioned_table
The catalog pg_partitioned_table stores
information about how tables are partitioned.
Table 53.37. pg_partitioned_table Columns
@@ -68,4 +68,4 @@
references. This is a list with one element for each zero
entry in partattrs. Null if all partition key columns
are simple references.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-policy.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-policy.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-policy.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-policy.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.38. pg_policy
The catalog pg_policy stores row-level
security policies for tables. A policy includes the kind of
command that it applies to (possibly all commands), the roles that it
@@ -65,4 +65,4 @@
Policies stored in pg_policy are applied only when
pg_class.relrowsecurity is set for
their table.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-proc.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-proc.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-proc.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-proc.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.39. pg_proc
The catalog pg_proc stores information about
functions, procedures, aggregate functions, and window functions
(collectively also known as routines). See CREATE FUNCTION, CREATE PROCEDURE, and
@@ -253,4 +253,4 @@
text. probin is null except for
dynamically-loaded C functions, for which it gives the name of the
shared library file containing the function.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-publication-namespace.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-publication-namespace.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-publication-namespace.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-publication-namespace.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.41. pg_publication_namespace
The catalog pg_publication_namespace contains the
mapping between schemas and publications in the database. This is a
many-to-many mapping.
@@ -25,4 +25,4 @@
Reference to schema
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-publication-rel.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-publication-rel.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-publication-rel.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-publication-rel.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.42. pg_publication_rel
The catalog pg_publication_rel contains the
mapping between relations and publications in the database. This is a
many-to-many mapping. See also Section 54.17
@@ -40,4 +40,4 @@
part of the publication. For example, a value of 1 3
would mean that the first and the third table columns are published.
A null value indicates that all columns are published.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-publication.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-publication.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-publication.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-publication.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.40. pg_publication
The catalog pg_publication contains all
publications created in the database. For more on publications see
Section 31.1.
@@ -61,4 +61,4 @@
If true, operations on a leaf partition are replicated using the
identity and schema of its topmost partitioned ancestor mentioned in the
publication instead of its own.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-range.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-range.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-range.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-range.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.43. pg_range
The catalog pg_range stores information about
range types. This is in addition to the types' entries in
pg_type.
@@ -58,4 +58,4 @@
type. rngcanonical is used when the element type is
discrete. rngsubdiff is optional but should be supplied to
improve performance of GiST indexes on the range type.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-replication-origin.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-replication-origin.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-replication-origin.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-replication-origin.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.44. pg_replication_origin
The pg_replication_origin catalog contains
all replication origins created. For more on replication origins
see Chapter 50.
@@ -25,4 +25,4 @@
The external, user defined, name of a replication
origin.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-rewrite.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-rewrite.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-rewrite.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-rewrite.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.45. pg_rewrite
The catalog pg_seclabel stores security
labels on database objects. Security labels can be manipulated
with the SECURITY LABEL command. For an easier
@@ -43,4 +43,4 @@
The security label applied to this object.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-sequence.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-sequence.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-sequence.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-sequence.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.47. pg_sequence
The catalog pg_sequence contains information about
sequences. Some of the information about sequences, such as the name and
the schema, is in
@@ -51,4 +51,4 @@
Whether the sequence cycles
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-shdepend.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-shdepend.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-shdepend.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-shdepend.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.48. pg_shdepend
The catalog pg_shdepend records the
dependency relationships between database objects and shared objects,
such as roles. This information allows
@@ -95,4 +95,4 @@
considered “pinned”. No entries are made
in pg_shdepend that would have a pinned
object as either referenced or dependent object.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-shdescription.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-shdescription.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-shdescription.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-shdescription.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.49. pg_shdescription
The catalog pg_shdescription stores optional
descriptions (comments) for shared database objects. Descriptions can be
manipulated with the COMMENT command and viewed with
@@ -35,4 +35,4 @@
Arbitrary text that serves as the description of this object
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-shseclabel.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-shseclabel.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-shseclabel.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-shseclabel.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.50. pg_shseclabel
The catalog pg_shseclabel stores security
labels on shared database objects. Security labels can be manipulated
with the SECURITY LABEL command. For an easier
@@ -40,4 +40,4 @@
The security label applied to this object.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-statistic-ext-data.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-statistic-ext-data.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-statistic-ext-data.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-statistic-ext-data.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.53. pg_statistic_ext_data
The catalog pg_statistic_ext_data
holds data for extended planner statistics defined in
pg_statistic_ext.
@@ -67,4 +67,4 @@
Per-expression statistics, serialized as an array of
pg_statistic type
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-statistic-ext.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-statistic-ext.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-statistic-ext.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-statistic-ext.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.52. pg_statistic_ext
The catalog pg_statistic_ext
holds definitions of extended planner statistics.
Each row in this catalog corresponds to a statistics object
@@ -85,4 +85,4 @@
and populate an entry in the
pg_statistic_ext_data
catalog.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-statistic.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-statistic.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-statistic.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-statistic.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.51. pg_statistic
The catalog pg_statistic stores
statistical data about the contents of the database. Entries are
created by ANALYZE
@@ -131,4 +131,4 @@
values are actually of the specific column's data type, or a related
type such as an array's element type, so there is no way to define
these columns' type more specifically than anyarray.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-subscription-rel.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-subscription-rel.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-subscription-rel.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-subscription-rel.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.55. pg_subscription_rel
The catalog pg_subscription_rel contains the
state for each replicated relation in each subscription. This is a
many-to-many mapping.
@@ -42,4 +42,4 @@
Remote LSN of the state change used for synchronization coordination
when in s or r states,
otherwise null
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-subscription.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-subscription.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-subscription.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-subscription.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.54. pg_subscription
The catalog pg_subscription contains all existing
logical replication subscriptions. For more information about logical
replication see Chapter 31.
@@ -100,4 +100,4 @@
Array of subscribed publication names. These reference
publications defined in the upstream database. For more on publications
see Section 31.1.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-tablespace.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-tablespace.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-tablespace.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-tablespace.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.56. pg_tablespace
The catalog pg_tablespace stores information
about the available tablespaces. Tables can be placed in particular
tablespaces to aid administration of disk layout.
@@ -39,4 +39,4 @@
Tablespace-level options, as “keyword=value” strings
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-transform.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-transform.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-transform.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-transform.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.57. pg_transform
The catalog pg_transform stores information about
transforms, which are a mechanism to adapt data types to procedural
languages. See CREATE TRANSFORM for more information.
@@ -41,4 +41,4 @@
The OID of the function to use when converting output from the
procedural language (e.g., return values) to the data type. Zero is
stored if the default behavior should be used.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-trigger.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-trigger.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-trigger.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-trigger.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.58. pg_trigger
The catalog pg_trigger stores triggers on tables
and views.
See CREATE TRIGGER
@@ -145,4 +145,4 @@
Note
pg_class.relhastriggers
must be true if a relation has any triggers in this catalog.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-ts-config-map.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-ts-config-map.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-ts-config-map.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-ts-config-map.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.60. pg_ts_config_map
The pg_ts_config_map catalog contains entries
showing which text search dictionaries should be consulted, and in
what order, for each output token type of each text search configuration's
@@ -35,4 +35,4 @@
The OID of the text search dictionary to consult
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-ts-config.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-ts-config.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-ts-config.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-ts-config.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.59. pg_ts_config
The pg_ts_config catalog contains entries
representing text search configurations. A configuration specifies
a particular text search parser and a list of dictionaries to use
@@ -42,4 +42,4 @@
The OID of the text search parser for this configuration
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-ts-dict.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-ts-dict.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-ts-dict.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-ts-dict.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.61. pg_ts_dict
The pg_ts_dict catalog contains entries
defining text search dictionaries. A dictionary depends on a text
search template, which specifies all the implementation functions
@@ -49,4 +49,4 @@
Initialization option string for the template
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-ts-parser.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-ts-parser.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-ts-parser.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-ts-parser.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.62. pg_ts_parser
The pg_ts_parser catalog contains entries
defining text search parsers. A parser is responsible for splitting
input text into lexemes and assigning a token type to each lexeme.
@@ -59,4 +59,4 @@
OID of the parser's lextype function
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-ts-template.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-ts-template.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-ts-template.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-ts-template.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.63. pg_ts_template
The pg_ts_template catalog contains entries
defining text search templates. A template is the implementation
skeleton for a class of text search dictionaries.
@@ -41,4 +41,4 @@
OID of the template's lexize function
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-type.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-type.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-type.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-type.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.64. pg_type
The catalog pg_type stores information about data
types. Base types and enum types (scalar types) are created with
CREATE TYPE, and
@@ -307,4 +307,4 @@
of typcategory. Any future additions to this list will
also be upper-case ASCII letters. All other ASCII characters are reserved
for user-defined categories.
-
Table 53.65. typcategory Codes
Code
Category
A
Array types
B
Boolean types
C
Composite types
D
Date/time types
E
Enum types
G
Geometric types
I
Network address types
N
Numeric types
P
Pseudo-types
R
Range types
S
String types
T
Timespan types
U
User-defined types
V
Bit-string types
X
unknown type
Z
Internal-use types
\ No newline at end of file
+
Table 53.65. typcategory Codes
Code
Category
A
Array types
B
Boolean types
C
Composite types
D
Date/time types
E
Enum types
G
Geometric types
I
Network address types
N
Numeric types
P
Pseudo-types
R
Range types
S
String types
T
Timespan types
U
User-defined types
V
Bit-string types
X
unknown type
Z
Internal-use types
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalog-pg-user-mapping.html postgresql-15-15.9/doc/src/sgml/html/catalog-pg-user-mapping.html
--- postgresql-15-15.8/doc/src/sgml/html/catalog-pg-user-mapping.html 2024-08-05 20:22:06.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalog-pg-user-mapping.html 2024-11-11 23:01:17.000000000 +0000
@@ -1,5 +1,5 @@
-53.65. pg_user_mapping
The catalog pg_user_mapping stores
the mappings from local user to remote. Access to this catalog is
restricted from normal users, use the view
@@ -32,4 +32,4 @@
User mapping specific options, as “keyword=value” strings
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/catalogs-overview.html postgresql-15-15.9/doc/src/sgml/html/catalogs-overview.html
--- postgresql-15-15.8/doc/src/sgml/html/catalogs-overview.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/catalogs-overview.html 2024-11-11 23:01:16.000000000 +0000
@@ -1,5 +1,5 @@
-53.1. Overview
Table 53.1 lists the system catalogs.
More detailed documentation of each catalog follows below.
@@ -7,4 +7,4 @@
database creation and are thereafter database-specific. A few
catalogs are physically shared across all databases in a cluster;
these are noted in the descriptions of the individual catalogs.
-
The system catalogs are the place where a relational database
management system stores schema metadata, such as information about
tables and columns, and internal bookkeeping information.
@@ -14,4 +14,4 @@
particularly esoteric operations, but many of those have been made
available as SQL commands over time, and so the need for direct manipulation
of the system catalogs is ever decreasing.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/charset.html postgresql-15-15.9/doc/src/sgml/html/charset.html
--- postgresql-15-15.8/doc/src/sgml/html/charset.html 2024-08-05 20:21:52.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/charset.html 2024-11-11 23:01:04.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 24. Localization
This chapter describes the available localization features from the
point of view of the administrator.
PostgreSQL supports two localization
@@ -17,4 +17,4 @@
between client and server.
This is covered in Section 24.3.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/checksums.html postgresql-15-15.9/doc/src/sgml/html/checksums.html
--- postgresql-15-15.8/doc/src/sgml/html/checksums.html 2024-08-05 20:21:53.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/checksums.html 2024-11-11 23:01:04.000000000 +0000
@@ -1,5 +1,5 @@
-30.2. Data Checksums
By default, data pages are not protected by checksums, but this can
optionally be enabled for a cluster. When enabled, each data page includes
a checksum that is updated when the page is written and verified each time
@@ -22,4 +22,4 @@
The pg_checksums
application can be used to enable or disable data checksums, as well as
verify checksums, on an offline cluster.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/citext.html postgresql-15-15.9/doc/src/sgml/html/citext.html
--- postgresql-15-15.8/doc/src/sgml/html/citext.html 2024-08-05 20:22:11.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/citext.html 2024-11-11 23:01:22.000000000 +0000
@@ -1,5 +1,5 @@
-F.10. citext
The citext module provides a case-insensitive
character string type, citext. Essentially, it internally calls
lower when comparing values. Otherwise, it behaves almost
@@ -163,4 +163,4 @@
David E. Wheeler <david@kineticode.com>
Inspired by the original citext module by Donald Fraser.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/client-authentication-problems.html postgresql-15-15.9/doc/src/sgml/html/client-authentication-problems.html
--- postgresql-15-15.8/doc/src/sgml/html/client-authentication-problems.html 2024-08-05 20:21:51.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/client-authentication-problems.html 2024-11-11 23:01:03.000000000 +0000
@@ -1,5 +1,5 @@
-21.15. Authentication Problems
Authentication failures and related problems generally
manifest themselves through error messages like the following:
@@ -37,4 +37,4 @@
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-15-15.8/doc/src/sgml/html/client-authentication.html postgresql-15-15.9/doc/src/sgml/html/client-authentication.html
--- postgresql-15-15.8/doc/src/sgml/html/client-authentication.html 2024-08-05 20:21:51.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/client-authentication.html 2024-11-11 23:01:03.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 21. Client Authentication
When a client application connects to the database server, it
specifies which PostgreSQL database user name it
wants to connect as, much the same way one logs into a Unix computer
@@ -34,4 +34,4 @@
operating system
account, and in such cases there need be no connection between
database user names and OS user names.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/client-interfaces.html postgresql-15-15.9/doc/src/sgml/html/client-interfaces.html
--- postgresql-15-15.8/doc/src/sgml/html/client-interfaces.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/client-interfaces.html 2024-11-11 23:01:07.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
@@ -9,4 +9,4 @@
familiar with using SQL commands to manipulate
and query the database (see Part II) and of course
with the programming language that the interface uses.
-
The collation feature allows specifying the sort order and character
classification behavior of data per-column, or even per-operation.
This alleviates the restriction that the
@@ -414,4 +414,4 @@
normalize and is normalized to
preprocess or check the strings, instead of using nondeterministic
collations. There are different trade-offs for each approach.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/color-when.html postgresql-15-15.9/doc/src/sgml/html/color-when.html
--- postgresql-15-15.8/doc/src/sgml/html/color-when.html 2024-08-05 20:22:12.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/color-when.html 2024-11-11 23:01:24.000000000 +0000
@@ -1,5 +1,5 @@
-N.1. When Color is Used
To use colorized output, set the environment variable
PG_COLOR
as follows:
@@ -12,4 +12,4 @@
Otherwise, color is not used.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/color-which.html postgresql-15-15.9/doc/src/sgml/html/color-which.html
--- postgresql-15-15.8/doc/src/sgml/html/color-which.html 2024-08-05 20:22:12.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/color-which.html 2024-11-11 23:01:24.000000000 +0000
@@ -1,5 +1,5 @@
-N.2. Configuring the Colors
The actual colors to be used are configured using the environment variable
PG_COLORS
(note plural). The value is a colon-separated list of
@@ -23,4 +23,4 @@
This color specification format is also used by other software packages
such as GCC, GNU
coreutils, and GNU grep.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/color.html postgresql-15-15.9/doc/src/sgml/html/color.html
--- postgresql-15-15.8/doc/src/sgml/html/color.html 2024-08-05 20:22:12.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/color.html 2024-11-11 23:01:24.000000000 +0000
@@ -1,5 +1,5 @@
-Appendix N. Color Support
All parameter names are case-insensitive. Every parameter takes a
value of one of five types: boolean, string, integer, floating point,
or enumerated (enum). The type determines the syntax for setting the
@@ -333,4 +333,4 @@
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-15-15.8/doc/src/sgml/html/connect-estab.html postgresql-15-15.9/doc/src/sgml/html/connect-estab.html
--- postgresql-15-15.8/doc/src/sgml/html/connect-estab.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/connect-estab.html 2024-11-11 23:01:16.000000000 +0000
@@ -1,5 +1,5 @@
-52.2. How Connections Are Established
PostgreSQL implements a
“process per user” client/server model.
In this model, every
@@ -33,4 +33,4 @@
process parses the query, creates an execution plan,
executes the plan, and returns the retrieved rows to the client
by transmitting them over the established connection.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/continuous-archiving.html postgresql-15-15.9/doc/src/sgml/html/continuous-archiving.html
--- postgresql-15-15.8/doc/src/sgml/html/continuous-archiving.html 2024-08-05 20:21:52.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/continuous-archiving.html 2024-11-11 23:01:04.000000000 +0000
@@ -1,5 +1,5 @@
-26.3. Continuous Archiving and Point-in-Time Recovery (PITR)
26.3. Continuous Archiving and Point-in-Time Recovery (PITR)
At all times, PostgreSQL maintains a
write ahead log (WAL) in the pg_wal/
subdirectory of the cluster's data directory. The log records
@@ -754,4 +754,4 @@
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-15-15.8/doc/src/sgml/html/contrib-dblink-build-sql-delete.html postgresql-15-15.9/doc/src/sgml/html/contrib-dblink-build-sql-delete.html
--- postgresql-15-15.8/doc/src/sgml/html/contrib-dblink-build-sql-delete.html 2024-08-05 20:22:11.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/contrib-dblink-build-sql-delete.html 2024-11-11 23:01:22.000000000 +0000
@@ -1,5 +1,5 @@
-dblink_build_sql_delete
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
dblink_open(text cursorname, text sql [, bool fail_on_error]) returns text
dblink_open(text connname, text cursorname, text sql [, bool fail_on_error]) returns text
Description
@@ -45,4 +45,4 @@
-------------
OK
(1 row)
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/contrib-dblink-send-query.html postgresql-15-15.9/doc/src/sgml/html/contrib-dblink-send-query.html
--- postgresql-15-15.8/doc/src/sgml/html/contrib-dblink-send-query.html 2024-08-05 20:22:11.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/contrib-dblink-send-query.html 2024-11-11 23:01:22.000000000 +0000
@@ -1,5 +1,5 @@
-dblink_send_query
oid2name — resolve OIDs and file nodes in a PostgreSQL data directory
vacuumlo — remove orphaned large objects from a PostgreSQL database
This section covers PostgreSQL client
applications in contrib. They can be run from anywhere,
independent of where the database server resides. See
also PostgreSQL Client Applications for information about client
applications that are part of the core PostgreSQL
distribution.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/contrib-prog-server.html postgresql-15-15.9/doc/src/sgml/html/contrib-prog-server.html
--- postgresql-15-15.8/doc/src/sgml/html/contrib-prog-server.html 2024-08-05 20:22:12.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/contrib-prog-server.html 2024-11-11 23:01:23.000000000 +0000
@@ -1,7 +1,7 @@
-G.2. Server Applications
Some applications run on the PostgreSQL server
itself. Currently, no such applications are included in the
contrib directory. See also PostgreSQL Server Applications for information about server applications that
are part of the core PostgreSQL distribution.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/contrib-prog.html postgresql-15-15.9/doc/src/sgml/html/contrib-prog.html
--- postgresql-15-15.8/doc/src/sgml/html/contrib-prog.html 2024-08-05 20:22:12.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/contrib-prog.html 2024-11-11 23:01:23.000000000 +0000
@@ -1,5 +1,5 @@
-Appendix G. Additional Supplied Programs
This appendix and the previous one contain information regarding the modules that
can be found in the contrib directory of the
PostgreSQL distribution. See Appendix F for
@@ -12,4 +12,4 @@
the bin directory of the
PostgreSQL installation and can be used like any
other program.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/contrib-spi.html postgresql-15-15.9/doc/src/sgml/html/contrib-spi.html
--- postgresql-15-15.8/doc/src/sgml/html/contrib-spi.html 2024-08-05 20:22:12.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/contrib-spi.html 2024-11-11 23:01:23.000000000 +0000
@@ -1,5 +1,5 @@
-F.41. spi
The spi module provides several workable examples
of using the Server Programming Interface
(SPI) and triggers. While these functions are of
@@ -78,4 +78,4 @@
time zone.
There is an example in moddatetime.example.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/contrib.html postgresql-15-15.9/doc/src/sgml/html/contrib.html
--- postgresql-15-15.8/doc/src/sgml/html/contrib.html 2024-08-05 20:22:12.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/contrib.html 2024-11-11 23:01:23.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
@@ -84,4 +84,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-15-15.8/doc/src/sgml/html/creating-cluster.html postgresql-15-15.9/doc/src/sgml/html/creating-cluster.html
--- postgresql-15-15.8/doc/src/sgml/html/creating-cluster.html 2024-08-05 20:21:51.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/creating-cluster.html 2024-11-11 23:01:02.000000000 +0000
@@ -1,5 +1,5 @@
-19.2. Creating a Database Cluster
Before you can do anything, you must initialize a database storage
area on disk. We call this a database cluster.
(The SQL standard uses the term catalog cluster.) A
@@ -200,4 +200,4 @@
it. That approach might relieve the DBA from having to deal with some of
the idiosyncrasies of NFS, but of course the complexity of managing
remote storage then happens at other levels.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/cube.html postgresql-15-15.9/doc/src/sgml/html/cube.html
--- postgresql-15-15.8/doc/src/sgml/html/cube.html 2024-08-05 20:22:11.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/cube.html 2024-11-11 23:01:22.000000000 +0000
@@ -1,5 +1,5 @@
-F.11. cube
This module implements a data type cube for
representing multidimensional cubes.
@@ -388,4 +388,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-15-15.8/doc/src/sgml/html/custom-rmgr.html postgresql-15-15.9/doc/src/sgml/html/custom-rmgr.html
--- postgresql-15-15.8/doc/src/sgml/html/custom-rmgr.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/custom-rmgr.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 66. Custom WAL Resource Managers
This chapter explains the interface between the core
PostgreSQL system and custom WAL resource
managers, which enable extensions to integrate directly with the WAL.
@@ -78,4 +78,4 @@
custom WAL records may exist in the system. Otherwise
PostgreSQL will not be able to apply or decode
the custom WAL records, which may prevent the server from starting.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/custom-scan-execution.html postgresql-15-15.9/doc/src/sgml/html/custom-scan-execution.html
--- postgresql-15-15.8/doc/src/sgml/html/custom-scan-execution.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/custom-scan-execution.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-61.3. Executing Custom Scans
When a CustomScan is executed, its execution state is
represented by a CustomScanState, which is declared as
follows:
@@ -136,4 +136,4 @@
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-15-15.8/doc/src/sgml/html/custom-scan-path.html postgresql-15-15.9/doc/src/sgml/html/custom-scan-path.html
--- postgresql-15-15.8/doc/src/sgml/html/custom-scan-path.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/custom-scan-path.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-61.1. Creating Custom Scan Paths
A custom scan provider will typically add paths for a base relation by
setting the following hook, which is called after the core code has
generated all the access paths it can for the relation (except for
@@ -98,4 +98,4 @@
reparameterize_path_by_child,
adjust_appendrel_attrs or
adjust_appendrel_attrs_multilevel as required.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/custom-scan-plan.html postgresql-15-15.9/doc/src/sgml/html/custom-scan-plan.html
--- postgresql-15-15.8/doc/src/sgml/html/custom-scan-plan.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/custom-scan-plan.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-61.2. Creating Custom Scan Plans
A custom scan is represented in a finished plan tree using the following
structure:
@@ -64,4 +64,4 @@
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-15-15.8/doc/src/sgml/html/custom-scan.html postgresql-15-15.9/doc/src/sgml/html/custom-scan.html
--- postgresql-15-15.8/doc/src/sgml/html/custom-scan.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/custom-scan.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 61. Writing a Custom Scan Provider
PostgreSQL supports a set of experimental facilities which
are intended to allow extension modules to add new scan types to the system.
Unlike a foreign data wrapper, which is only
@@ -18,4 +18,4 @@
Finally, it must be possible to execute the plan and generate the same
results that would have been generated for any other access path targeting
the same relation.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/database-roles.html postgresql-15-15.9/doc/src/sgml/html/database-roles.html
--- postgresql-15-15.8/doc/src/sgml/html/database-roles.html 2024-08-05 20:21:51.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/database-roles.html 2024-11-11 23:01:03.000000000 +0000
@@ -1,5 +1,5 @@
-22.1. Database Roles
Database roles are conceptually completely separate from
operating system users. In practice it might be convenient to
maintain a correspondence, but this is not required. Database roles
@@ -67,4 +67,4 @@
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-15-15.8/doc/src/sgml/html/datatype-binary.html postgresql-15-15.9/doc/src/sgml/html/datatype-binary.html
--- postgresql-15-15.8/doc/src/sgml/html/datatype-binary.html 2024-08-05 20:21:47.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datatype-binary.html 2024-11-11 23:00:58.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
@@ -129,4 +129,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-15-15.8/doc/src/sgml/html/datatype-bit.html postgresql-15-15.9/doc/src/sgml/html/datatype-bit.html
--- postgresql-15-15.8/doc/src/sgml/html/datatype-bit.html 2024-08-05 20:21:47.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datatype-bit.html 2024-11-11 23:00:59.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
@@ -46,4 +46,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-15-15.8/doc/src/sgml/html/datatype-boolean.html postgresql-15-15.9/doc/src/sgml/html/datatype-boolean.html
--- postgresql-15-15.8/doc/src/sgml/html/datatype-boolean.html 2024-08-05 20:21:47.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datatype-boolean.html 2024-11-11 23:00:59.000000000 +0000
@@ -1,5 +1,5 @@
-8.6. Boolean Type
PostgreSQL provides the
standard SQL type boolean;
see Table 8.19.
@@ -55,4 +55,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-15-15.8/doc/src/sgml/html/datatype-character.html postgresql-15-15.9/doc/src/sgml/html/datatype-character.html
--- postgresql-15-15.8/doc/src/sgml/html/datatype-character.html 2024-08-05 20:21:47.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datatype-character.html 2024-11-11 23:00:58.000000000 +0000
@@ -1,5 +1,5 @@
-8.3. Character Types
Table 8.4 shows the
general-purpose character types available in
PostgreSQL.
@@ -139,4 +139,4 @@
only uses one byte of storage, and therefore can store only a single
ASCII character. It is used in the system
catalogs as a simplistic enumeration type.
-
Table 8.5. Special Character Types
Name
Storage Size
Description
"char"
1 byte
single-byte internal type
name
64 bytes
internal type for object names
\ No newline at end of file
+
Table 8.5. Special Character Types
Name
Storage Size
Description
"char"
1 byte
single-byte internal type
name
64 bytes
internal type for object names
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/datatype-datetime.html postgresql-15-15.9/doc/src/sgml/html/datatype-datetime.html
--- postgresql-15-15.8/doc/src/sgml/html/datatype-datetime.html 2024-08-05 20:21:47.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datatype-datetime.html 2024-11-11 23:00:59.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
@@ -554,4 +554,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-15-15.8/doc/src/sgml/html/datatype-enum.html postgresql-15-15.9/doc/src/sgml/html/datatype-enum.html
--- postgresql-15-15.8/doc/src/sgml/html/datatype-enum.html 2024-08-05 20:21:47.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datatype-enum.html 2024-11-11 23:00:59.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
@@ -112,4 +112,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-15-15.8/doc/src/sgml/html/datatype-geometric.html postgresql-15-15.9/doc/src/sgml/html/datatype-geometric.html
--- postgresql-15-15.8/doc/src/sgml/html/datatype-geometric.html 2024-08-05 20:21:47.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datatype-geometric.html 2024-11-11 23:00:59.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.
@@ -158,4 +158,4 @@
circle.
Circles are output using the first syntax.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/datatype-json.html postgresql-15-15.9/doc/src/sgml/html/datatype-json.html
--- postgresql-15-15.8/doc/src/sgml/html/datatype-json.html 2024-08-05 20:21:47.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datatype-json.html 2024-11-11 23:00:59.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
@@ -726,4 +726,4 @@
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-15-15.8/doc/src/sgml/html/datatype-money.html postgresql-15-15.9/doc/src/sgml/html/datatype-money.html
--- postgresql-15-15.8/doc/src/sgml/html/datatype-money.html 2024-08-05 20:21:47.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datatype-money.html 2024-11-11 23:00:58.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.
@@ -41,4 +41,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-15-15.8/doc/src/sgml/html/datatype-net-types.html postgresql-15-15.9/doc/src/sgml/html/datatype-net-types.html
--- postgresql-15-15.8/doc/src/sgml/html/datatype-net-types.html 2024-08-05 20:21:47.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datatype-net-types.html 2024-11-11 23:00:59.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
@@ -129,4 +129,4 @@
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/datatype-numeric.html postgresql-15-15.9/doc/src/sgml/html/datatype-numeric.html
--- postgresql-15-15.8/doc/src/sgml/html/datatype-numeric.html 2024-08-05 20:21:47.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datatype-numeric.html 2024-11-11 23:00:58.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
@@ -367,4 +367,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-15-15.8/doc/src/sgml/html/datatype-oid.html postgresql-15-15.9/doc/src/sgml/html/datatype-oid.html
--- postgresql-15-15.8/doc/src/sgml/html/datatype-oid.html 2024-08-05 20:21:47.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datatype-oid.html 2024-11-11 23:00:59.000000000 +0000
@@ -1,5 +1,5 @@
-8.19. Object Identifier Types
Object identifiers (OIDs) are used internally by
PostgreSQL as primary keys for various
system tables.
@@ -163,4 +163,4 @@
physical location of the row within its table.
(The system columns are further explained in Section 5.5.)
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/datatype-pg-lsn.html postgresql-15-15.9/doc/src/sgml/html/datatype-pg-lsn.html
--- postgresql-15-15.8/doc/src/sgml/html/datatype-pg-lsn.html 2024-08-05 20:21:47.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datatype-pg-lsn.html 2024-11-11 23:00:59.000000000 +0000
@@ -1,5 +1,5 @@
-8.20. pg_lsn Type
The pg_lsn data type can be used to store LSN (Log Sequence
Number) data which is a pointer to a location in the WAL. This type is a
representation of XLogRecPtr and an internal system type of
@@ -19,4 +19,4 @@
the calculated LSN should be in the range of pg_lsn type,
i.e., between 0/0 and
FFFFFFFF/FFFFFFFF.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/datatype-pseudo.html postgresql-15-15.9/doc/src/sgml/html/datatype-pseudo.html
--- postgresql-15-15.8/doc/src/sgml/html/datatype-pseudo.html 2024-08-05 20:21:47.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datatype-pseudo.html 2024-11-11 23:00:59.000000000 +0000
@@ -1,5 +1,5 @@
-8.21. Pseudo-Types
The PostgreSQL type system contains a
number of special-purpose entries that are collectively called
pseudo-types. A pseudo-type cannot be used as a
@@ -56,4 +56,4 @@
follow this coding rule: do not create any function that is
declared to return internal unless it has at least one
internal argument.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/datatype-textsearch.html postgresql-15-15.9/doc/src/sgml/html/datatype-textsearch.html
--- postgresql-15-15.8/doc/src/sgml/html/datatype-textsearch.html 2024-08-05 20:21:47.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datatype-textsearch.html 2024-11-11 23:00:59.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
@@ -193,4 +193,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-15-15.8/doc/src/sgml/html/datatype-uuid.html postgresql-15-15.9/doc/src/sgml/html/datatype-uuid.html
--- postgresql-15-15.8/doc/src/sgml/html/datatype-uuid.html 2024-08-05 20:21:47.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datatype-uuid.html 2024-11-11 23:00:59.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.
@@ -36,4 +36,4 @@
See Section 9.14 for how to generate a UUID in
PostgreSQL.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/datatype-xml.html postgresql-15-15.9/doc/src/sgml/html/datatype-xml.html
--- postgresql-15-15.8/doc/src/sgml/html/datatype-xml.html 2024-08-05 20:21:47.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datatype-xml.html 2024-11-11 23:00:59.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
@@ -148,4 +148,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-15-15.8/doc/src/sgml/html/datatype.html postgresql-15-15.9/doc/src/sgml/html/datatype.html
--- postgresql-15-15.8/doc/src/sgml/html/datatype.html 2024-08-05 20:21:47.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datatype.html 2024-11-11 23:00:59.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.
@@ -33,4 +33,4 @@
Some of the input and output functions are not invertible, i.e.,
the result of an output function might lose accuracy when compared to
the original input.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/datetime-appendix.html postgresql-15-15.9/doc/src/sgml/html/datetime-appendix.html
--- postgresql-15-15.8/doc/src/sgml/html/datetime-appendix.html 2024-08-05 20:22:08.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datetime-appendix.html 2024-11-11 23:01:20.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
@@ -12,4 +12,4 @@
This appendix includes information on the content of these
lookup tables and describes the steps used by the parser to decode
dates and times.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/datetime-config-files.html postgresql-15-15.9/doc/src/sgml/html/datetime-config-files.html
--- postgresql-15-15.8/doc/src/sgml/html/datetime-config-files.html 2024-08-05 20:22:08.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datetime-config-files.html 2024-11-11 23:01:20.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
@@ -95,4 +95,4 @@
If you modify files in .../share/timezonesets/,
it is up to you to make backups — a normal database dump
will not include this directory.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/datetime-input-rules.html postgresql-15-15.9/doc/src/sgml/html/datetime-input-rules.html
--- postgresql-15-15.8/doc/src/sgml/html/datetime-input-rules.html 2024-08-05 20:22:08.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datetime-input-rules.html 2024-11-11 23:01:20.000000000 +0000
@@ -1,5 +1,5 @@
-B.1. Date/Time Input Interpretation
Date/time input strings are decoded using the following procedure.
Break the input string into tokens and categorize each token as
@@ -71,4 +71,4 @@
Gregorian years AD 1–99 can be entered by using 4 digits with leading
zeros (e.g., 0099 is AD 99).
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/datetime-invalid-input.html postgresql-15-15.9/doc/src/sgml/html/datetime-invalid-input.html
--- postgresql-15-15.8/doc/src/sgml/html/datetime-invalid-input.html 2024-08-05 20:22:08.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datetime-invalid-input.html 2024-11-11 23:01:20.000000000 +0000
@@ -1,5 +1,5 @@
-B.2. Handling of Invalid or Ambiguous Timestamps
Ordinarily, if a date/time string is syntactically valid but contains
out-of-range field values, an error will be thrown. For example, input
specifying the 31st of February will be rejected.
@@ -59,4 +59,4 @@
abbreviation that corresponds to a fixed UTC offset. The rule just
given applies only when it is necessary to infer a UTC offset for a time
zone in which the offset varies.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/datetime-julian-dates.html postgresql-15-15.9/doc/src/sgml/html/datetime-julian-dates.html
--- postgresql-15-15.8/doc/src/sgml/html/datetime-julian-dates.html 2024-08-05 20:22:08.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datetime-julian-dates.html 2024-11-11 23:01:20.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
@@ -45,4 +45,4 @@
2459389
(1 row)
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/datetime-keywords.html postgresql-15-15.9/doc/src/sgml/html/datetime-keywords.html
--- postgresql-15-15.8/doc/src/sgml/html/datetime-keywords.html 2024-08-05 20:22:08.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datetime-keywords.html 2024-11-11 23:01:20.000000000 +0000
@@ -1,5 +1,5 @@
-B.3. Date/Time Key Words
Table B.1 shows the tokens that are
recognized as names of months.
Table B.1. Month Names
Month
Abbreviations
January
Jan
February
Feb
March
Mar
April
Apr
May
June
Jun
July
Jul
August
Aug
September
Sep, Sept
October
Oct
November
Nov
December
Dec
@@ -8,4 +8,4 @@
Table B.2. Day of the Week Names
Day
Abbreviations
Sunday
Sun
Monday
Mon
Tuesday
Tue, Tues
Wednesday
Wed, Weds
Thursday
Thu, Thur, Thurs
Friday
Fri
Saturday
Sat
Table B.3 shows the tokens that serve
various modifier purposes.
-
Table B.3. Date/Time Field Modifiers
Identifier
Description
AM
Time is before 12:00
AT
Ignored
JULIAN, JD, J
Next field is Julian Date
ON
Ignored
PM
Time is on or after 12:00
T
Next field is time
\ No newline at end of file
+
Table B.3. Date/Time Field Modifiers
Identifier
Description
AM
Time is before 12:00
AT
Ignored
JULIAN, JD, J
Next field is Julian Date
ON
Ignored
PM
Time is on or after 12:00
T
Next field is time
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/datetime-posix-timezone-specs.html postgresql-15-15.9/doc/src/sgml/html/datetime-posix-timezone-specs.html
--- postgresql-15-15.8/doc/src/sgml/html/datetime-posix-timezone-specs.html 2024-08-05 20:22:08.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datetime-posix-timezone-specs.html 2024-11-11 23:01:20.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
@@ -132,4 +132,4 @@
zone abbreviation(s). For example, SET TIMEZONE TO
FOOBAR0 will work, leaving the system effectively using a
rather peculiar abbreviation for UTC.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/datetime-units-history.html postgresql-15-15.9/doc/src/sgml/html/datetime-units-history.html
--- postgresql-15-15.8/doc/src/sgml/html/datetime-units-history.html 2024-08-05 20:22:08.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/datetime-units-history.html 2024-11-11 23:01:20.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
@@ -84,4 +84,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-15-15.8/doc/src/sgml/html/dblink.html postgresql-15-15.9/doc/src/sgml/html/dblink.html
--- postgresql-15-15.8/doc/src/sgml/html/dblink.html 2024-08-05 20:22:11.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/dblink.html 2024-11-11 23:01:22.000000000 +0000
@@ -1,5 +1,5 @@
-F.12. dblink
When you create a table and you realize that you made a mistake, or
the requirements of the application change, you can drop the
table and create it again. But this is not a convenient option if
@@ -153,4 +153,4 @@
ALTER TABLE products RENAME TO items;
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/ddl-basics.html postgresql-15-15.9/doc/src/sgml/html/ddl-basics.html
--- postgresql-15-15.8/doc/src/sgml/html/ddl-basics.html 2024-08-05 20:21:46.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ddl-basics.html 2024-11-11 23:00:58.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
@@ -98,4 +98,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-15-15.8/doc/src/sgml/html/ddl-constraints.html postgresql-15-15.9/doc/src/sgml/html/ddl-constraints.html
--- postgresql-15-15.8/doc/src/sgml/html/ddl-constraints.html 2024-08-05 20:21:46.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ddl-constraints.html 2024-11-11 23:00:58.000000000 +0000
@@ -1,5 +1,5 @@
-5.4. Constraints
Data types are a way to limit the kind of data that can be stored
in a table. For many applications, however, the constraint they
provide is too coarse. For example, a column containing a product
@@ -604,4 +604,4 @@
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-15-15.8/doc/src/sgml/html/ddl-default.html postgresql-15-15.9/doc/src/sgml/html/ddl-default.html
--- postgresql-15-15.8/doc/src/sgml/html/ddl-default.html 2024-08-05 20:21:46.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ddl-default.html 2024-11-11 23:00:58.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
@@ -46,4 +46,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-15-15.8/doc/src/sgml/html/ddl-depend.html postgresql-15-15.9/doc/src/sgml/html/ddl-depend.html
--- postgresql-15-15.8/doc/src/sgml/html/ddl-depend.html 2024-08-05 20:21:46.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ddl-depend.html 2024-11-11 23:00:58.000000000 +0000
@@ -1,5 +1,5 @@
-5.14. Dependency Tracking
When you create complex database structures involving many tables
with foreign key constraints, views, triggers, functions, etc. you
implicitly create a net of dependencies between the objects.
@@ -96,4 +96,4 @@
then the function's dependency on the my_colors
table will be known and enforced by DROP.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/ddl-foreign-data.html postgresql-15-15.9/doc/src/sgml/html/ddl-foreign-data.html
--- postgresql-15-15.8/doc/src/sgml/html/ddl-foreign-data.html 2024-08-05 20:21:46.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ddl-foreign-data.html 2024-11-11 23:00:58.000000000 +0000
@@ -1,5 +1,5 @@
-5.12. Foreign Data
PostgreSQL implements portions of the SQL/MED
specification, allowing you to access data that resides outside
PostgreSQL using regular SQL queries. Such data is referred to as
@@ -38,4 +38,4 @@
CREATE USER MAPPING,
CREATE FOREIGN TABLE, and
IMPORT FOREIGN SCHEMA.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/ddl-generated-columns.html postgresql-15-15.9/doc/src/sgml/html/ddl-generated-columns.html
--- postgresql-15-15.8/doc/src/sgml/html/ddl-generated-columns.html 2024-08-05 20:21:46.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ddl-generated-columns.html 2024-11-11 23:00:58.000000000 +0000
@@ -1,5 +1,5 @@
-5.3. Generated Columns
A generated column is a special column that is always computed from other
columns. Thus, it is for columns what a view is for tables. There are two
kinds of generated columns: stored and virtual. A stored generated column
@@ -85,4 +85,4 @@
Generated columns are skipped for logical replication and cannot be
specified in a CREATE PUBLICATION column list.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/ddl-inherit.html postgresql-15-15.9/doc/src/sgml/html/ddl-inherit.html
--- postgresql-15-15.8/doc/src/sgml/html/ddl-inherit.html 2024-08-05 20:21:46.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ddl-inherit.html 2024-11-11 23:00:58.000000000 +0000
@@ -1,5 +1,5 @@
-5.10. Inheritance
PostgreSQL implements table inheritance,
which can be a useful tool for database designers. (SQL:1999 and
later define a type inheritance feature, which differs in many
@@ -286,4 +286,4 @@
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-15-15.8/doc/src/sgml/html/ddl-others.html postgresql-15-15.9/doc/src/sgml/html/ddl-others.html
--- postgresql-15-15.8/doc/src/sgml/html/ddl-others.html 2024-08-05 20:21:46.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ddl-others.html 2024-11-11 23:00:58.000000000 +0000
@@ -1,5 +1,5 @@
-5.13. Other Database Objects
Tables are the central objects in a relational database structure,
because they hold your data. But they are not the only objects
that exist in a database. Many other kinds of objects can be
@@ -17,4 +17,4 @@
Detailed information on
these topics appears in Part V.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/ddl-partitioning.html postgresql-15-15.9/doc/src/sgml/html/ddl-partitioning.html
--- postgresql-15-15.8/doc/src/sgml/html/ddl-partitioning.html 2024-08-05 20:21:46.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ddl-partitioning.html 2024-11-11 23:00:58.000000000 +0000
@@ -1,5 +1,5 @@
-5.11. Table Partitioning
PostgreSQL supports basic table
partitioning. This section describes why and how to implement
partitioning as part of your database design.
@@ -991,4 +991,4 @@
painfully slow. Simulations of the intended workload are often beneficial
for optimizing the partitioning strategy. Never just assume that more
partitions are better than fewer partitions, nor vice-versa.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/ddl-priv.html postgresql-15-15.9/doc/src/sgml/html/ddl-priv.html
--- postgresql-15-15.8/doc/src/sgml/html/ddl-priv.html 2024-08-05 20:21:46.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ddl-priv.html 2024-11-11 23:00:58.000000000 +0000
@@ -1,5 +1,5 @@
-5.7. Privileges
When an object is created, it is assigned an owner. The
owner is normally the role that executed the creation statement.
For most kinds of objects, the initial state is that only the owner
@@ -311,4 +311,4 @@
Notice that the owner's implicit grant options are not marked in the
access privileges display. A * will appear only when
grant options have been explicitly granted to someone.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/ddl-rowsecurity.html postgresql-15-15.9/doc/src/sgml/html/ddl-rowsecurity.html
--- postgresql-15-15.8/doc/src/sgml/html/ddl-rowsecurity.html 2024-08-05 20:21:46.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ddl-rowsecurity.html 2024-11-11 23:00:58.000000000 +0000
@@ -1,5 +1,5 @@
-5.8. Row Security Policies
A PostgreSQL database cluster contains
one or more named databases. Roles and a few other object types are
shared across the entire cluster. A client connection to the server
@@ -326,4 +326,4 @@
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-15-15.8/doc/src/sgml/html/ddl-system-columns.html postgresql-15-15.9/doc/src/sgml/html/ddl-system-columns.html
--- postgresql-15-15.8/doc/src/sgml/html/ddl-system-columns.html 2024-08-05 20:21:46.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ddl-system-columns.html 2024-11-11 23:00:58.000000000 +0000
@@ -1,5 +1,5 @@
-5.5. System Columns
Every table has several system columns that are
implicitly defined by the system. Therefore, these names cannot be
used as names of user-defined columns. (Note that these
@@ -55,4 +55,4 @@
SQL commands, not the number of rows processed.
Also, only commands that actually modify the database contents will
consume a command identifier.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/ddl.html postgresql-15-15.9/doc/src/sgml/html/ddl.html
--- postgresql-15-15.8/doc/src/sgml/html/ddl.html 2024-08-05 20:21:46.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ddl.html 2024-11-11 23:00:58.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
@@ -10,4 +10,4 @@
we will briefly look at other features that affect the data storage,
such as inheritance, table partitioning, views, functions, and
triggers.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/default-roles.html postgresql-15-15.9/doc/src/sgml/html/default-roles.html
--- postgresql-15-15.8/doc/src/sgml/html/default-roles.html 2024-08-05 20:22:13.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/default-roles.html 2024-11-11 23:01:24.000000000 +0000
@@ -1,9 +1,9 @@
-O.2. Default Roles Renamed to Predefined Roles
PostgreSQL 13 and below used the term “Default Roles”. However, as these
roles are not able to actually be changed and are installed as part of the
system at initialization time, the more appropriate term to use is “Predefined Roles”.
See Section 22.5 for current documentation regarding
- Predefined Roles, and the release notes for
+ Predefined Roles, and the release notes for
PostgreSQL 14 for details on this change.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/dict-int.html postgresql-15-15.9/doc/src/sgml/html/dict-int.html
--- postgresql-15-15.8/doc/src/sgml/html/dict-int.html 2024-08-05 20:22:11.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/dict-int.html 2024-11-11 23:01:22.000000000 +0000
@@ -1,5 +1,5 @@
-F.13. dict_int
dict_int is an example of an add-on dictionary template
for full-text search. The motivation for this example dictionary is to
control the indexing of integers (signed and unsigned), allowing such
@@ -59,4 +59,4 @@
ALTER MAPPING FOR int, uint WITH intdict;
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/dict-xsyn.html postgresql-15-15.9/doc/src/sgml/html/dict-xsyn.html
--- postgresql-15-15.8/doc/src/sgml/html/dict-xsyn.html 2024-08-05 20:22:11.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/dict-xsyn.html 2024-11-11 23:01:22.000000000 +0000
@@ -1,5 +1,5 @@
-F.14. dict_xsyn
dict_xsyn (Extended Synonym Dictionary) is an example of an
add-on dictionary template for full-text search. This dictionary type
replaces words with groups of their synonyms, and so makes it possible to
@@ -94,4 +94,4 @@
ALTER MAPPING FOR word, asciiword WITH xsyn, english_stem;
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/different-replication-solutions.html postgresql-15-15.9/doc/src/sgml/html/different-replication-solutions.html
--- postgresql-15-15.8/doc/src/sgml/html/different-replication-solutions.html 2024-08-05 20:21:52.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/different-replication-solutions.html 2024-11-11 23:01:04.000000000 +0000
@@ -1,5 +1,5 @@
-27.1. Comparison of Different Solutions
Shared disk failover avoids synchronization overhead by having only one
copy of the database. It uses a single disk array that is shared by
multiple servers. If the main database server fails, the standby server
@@ -134,4 +134,4 @@
taken PostgreSQL and created commercial
closed-source solutions with unique failover, replication, and load
balancing capabilities. These are not discussed here.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/disk-full.html postgresql-15-15.9/doc/src/sgml/html/disk-full.html
--- postgresql-15-15.8/doc/src/sgml/html/disk-full.html 2024-08-05 20:21:53.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/disk-full.html 2024-11-11 23:01:04.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
@@ -17,4 +17,4 @@
will naturally be subject to whatever quota is placed on the user
the server runs as. Exceeding the quota will have the same bad
effects as running out of disk space entirely.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/disk-usage.html postgresql-15-15.9/doc/src/sgml/html/disk-usage.html
--- postgresql-15-15.8/doc/src/sgml/html/disk-usage.html 2024-08-05 20:21:53.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/disk-usage.html 2024-11-11 23:01:04.000000000 +0000
@@ -1,5 +1,5 @@
-29.1. Determining Disk Usage
Each table has a primary heap disk file where most of the data is
stored. If the table has any columns with potentially-wide values,
there also might be a TOAST file associated with the table,
@@ -80,4 +80,4 @@
bigtable | 3290
customer | 3144
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/diskusage.html postgresql-15-15.9/doc/src/sgml/html/diskusage.html
--- postgresql-15-15.8/doc/src/sgml/html/diskusage.html 2024-08-05 20:21:53.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/diskusage.html 2024-11-11 23:01:04.000000000 +0000
@@ -1,5 +1,5 @@
-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
@@ -25,4 +25,4 @@
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-15-15.8/doc/src/sgml/html/dml-insert.html postgresql-15-15.9/doc/src/sgml/html/dml-insert.html
--- postgresql-15-15.8/doc/src/sgml/html/dml-insert.html 2024-08-05 20:21:46.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/dml-insert.html 2024-11-11 23:00:58.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
inserted one row at a time. You can also insert more than one row
@@ -78,4 +78,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-15-15.8/doc/src/sgml/html/dml-returning.html postgresql-15-15.9/doc/src/sgml/html/dml-returning.html
--- postgresql-15-15.8/doc/src/sgml/html/dml-returning.html 2024-08-05 20:21:46.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/dml-returning.html 2024-11-11 23:00:58.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
@@ -50,4 +50,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-15-15.8/doc/src/sgml/html/dml-update.html postgresql-15-15.9/doc/src/sgml/html/dml-update.html
--- postgresql-15-15.8/doc/src/sgml/html/dml-update.html 2024-08-05 20:21:46.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/dml-update.html 2024-11-11 23:00:58.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
@@ -58,4 +58,4 @@
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-15-15.8/doc/src/sgml/html/dml.html postgresql-15-15.9/doc/src/sgml/html/dml.html
--- postgresql-15-15.8/doc/src/sgml/html/dml.html 2024-08-05 20:21:46.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/dml.html 2024-11-11 23:00:58.000000000 +0000
@@ -1,9 +1,9 @@
-Chapter 6. Data Manipulation
The previous chapter discussed how to create tables and other
structures to hold your data. Now it is time to fill the tables
with data. This chapter covers how to insert, update, and delete
table data. The chapter
after this will finally explain how to extract your long-lost data
from the database.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/docguide-authoring.html postgresql-15-15.9/doc/src/sgml/html/docguide-authoring.html
--- postgresql-15-15.8/doc/src/sgml/html/docguide-authoring.html 2024-08-05 20:22:12.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/docguide-authoring.html 2024-11-11 23:01:23.000000000 +0000
@@ -1,5 +1,5 @@
-J.4. Documentation Authoring
The documentation sources are most conveniently modified with an editor
that has a mode for editing XML, and even more so if it has some awareness
of XML schema languages so that it can know about
@@ -20,4 +20,4 @@
src/tools/editors/emacs.samples contains
recommended settings for this mode.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/docguide-build.html postgresql-15-15.9/doc/src/sgml/html/docguide-build.html
--- postgresql-15-15.8/doc/src/sgml/html/docguide-build.html 2024-08-05 20:22:12.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/docguide-build.html 2024-11-11 23:01:23.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
@@ -88,4 +88,4 @@
doc/src/sgml$ make check
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/docguide-docbook.html postgresql-15-15.9/doc/src/sgml/html/docguide-docbook.html
--- postgresql-15-15.8/doc/src/sgml/html/docguide-docbook.html 2024-08-05 20:22:12.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/docguide-docbook.html 2024-11-11 23:01:23.000000000 +0000
@@ -1,5 +1,5 @@
-J.1. DocBook
The documentation sources are written in
DocBook, which is a markup language
defined in XML. In what
@@ -20,4 +20,4 @@
FreeBSD Documentation Project also uses DocBook and has some good
information, including a number of style guidelines that might be
worth considering.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/docguide-style.html postgresql-15-15.9/doc/src/sgml/html/docguide-style.html
--- postgresql-15-15.8/doc/src/sgml/html/docguide-style.html 2024-08-05 20:22:12.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/docguide-style.html 2024-11-11 23:01:23.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.
@@ -86,4 +86,4 @@
database system it is compatible. The See Also section of SQL
commands should list SQL commands before cross-references to
programs.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/docguide-toolsets.html postgresql-15-15.9/doc/src/sgml/html/docguide-toolsets.html
--- postgresql-15-15.8/doc/src/sgml/html/docguide-toolsets.html 2024-08-05 20:22:12.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/docguide-toolsets.html 2024-11-11 23:01:23.000000000 +0000
@@ -1,5 +1,5 @@
-J.2. Tool Sets
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/docguide.html postgresql-15-15.9/doc/src/sgml/html/docguide.html
--- postgresql-15-15.8/doc/src/sgml/html/docguide.html 2024-08-05 20:22:12.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/docguide.html 2024-11-11 23:01:23.000000000 +0000
@@ -1,5 +1,5 @@
-Appendix J. Documentation
PostgreSQL has four primary documentation
formats:
@@ -21,4 +21,4 @@
standard distribution and are installed by default. PDF
format documentation is available separately for
download.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/domains.html postgresql-15-15.9/doc/src/sgml/html/domains.html
--- postgresql-15-15.8/doc/src/sgml/html/domains.html 2024-08-05 20:21:47.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/domains.html 2024-11-11 23:00:59.000000000 +0000
@@ -1,5 +1,5 @@
-8.18. Domain Types
A domain is a user-defined data type that is
based on another underlying type. Optionally,
it can have constraints that restrict its valid values to a subset of
@@ -31,4 +31,4 @@
domain's constraints will be checked.
PostgreSQL provides facilities to support
dynamic tracing of the database server. This allows an external
utility to be called at specific points in the code and thereby trace
@@ -298,4 +298,4 @@
Each trace macro has a corresponding ENABLED macro.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/earthdistance.html postgresql-15-15.9/doc/src/sgml/html/earthdistance.html
--- postgresql-15-15.8/doc/src/sgml/html/earthdistance.html 2024-08-05 20:22:11.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/earthdistance.html 2024-11-11 23:01:22.000000000 +0000
@@ -1,5 +1,5 @@
-F.15. earthdistance
The earthdistance module provides two different approaches to
calculating great circle distances on the surface of the Earth. The one
described first depends on the cube module.
@@ -155,4 +155,4 @@
you need to be careful about the edge conditions near the poles
and near +/- 180 degrees of longitude. The cube-based
representation avoids these discontinuities.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/ecpg-commands.html postgresql-15-15.9/doc/src/sgml/html/ecpg-commands.html
--- postgresql-15-15.8/doc/src/sgml/html/ecpg-commands.html 2024-08-05 20:21:54.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ecpg-commands.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-36.3. Running SQL Commands
An embedded SQL program consists of code written in an ordinary
programming language, in this case C, mixed with SQL commands in
specially marked sections. To build the program, the source code (*.pgc)
@@ -49,4 +49,4 @@
Of course, the C part of the program follows C quoting rules.
The following sections explain all the embedded SQL statements.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/ecpg-connect.html postgresql-15-15.9/doc/src/sgml/html/ecpg-connect.html
--- postgresql-15-15.8/doc/src/sgml/html/ecpg-connect.html 2024-08-05 20:21:54.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ecpg-connect.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-36.2. Managing Database Connections
ECPG has some limited support for C++ applications. This section
describes some caveats.
@@ -225,4 +225,4 @@
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-15-15.8/doc/src/sgml/html/ecpg-descriptors.html postgresql-15-15.9/doc/src/sgml/html/ecpg-descriptors.html
--- postgresql-15-15.8/doc/src/sgml/html/ecpg-descriptors.html 2024-08-05 20:21:54.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ecpg-descriptors.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-36.7. Using Descriptor Areas
An SQL descriptor area is a more sophisticated method for processing
the result of a SELECT, FETCH or
a DESCRIBE statement. An SQL descriptor area groups
@@ -707,4 +707,4 @@
tup_inserted = 0 (type: 9)
tup_updated = 0 (type: 9)
tup_deleted = 0 (type: 9)
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/ecpg-develop.html postgresql-15-15.9/doc/src/sgml/html/ecpg-develop.html
--- postgresql-15-15.8/doc/src/sgml/html/ecpg-develop.html 2024-08-05 20:21:54.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ecpg-develop.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-36.17. Internals
This section explains how ECPG works
internally. This information can occasionally be useful to help
users understand how to use ECPG.
@@ -121,4 +121,4 @@
(The indentation here is added for readability and not
something the preprocessor does.)
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/ecpg-dynamic.html postgresql-15-15.9/doc/src/sgml/html/ecpg-dynamic.html
--- postgresql-15-15.8/doc/src/sgml/html/ecpg-dynamic.html 2024-08-05 20:21:54.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ecpg-dynamic.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-36.5. Dynamic SQL
In many cases, the particular SQL statements that an application
has to execute are known at the time the application is written.
In some cases, however, the SQL statements are composed at run time
@@ -100,4 +100,4 @@
EXEC SQL COMMIT;
EXEC SQL DISCONNECT ALL;
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/ecpg-errors.html postgresql-15-15.9/doc/src/sgml/html/ecpg-errors.html
--- postgresql-15-15.8/doc/src/sgml/html/ecpg-errors.html 2024-08-05 20:21:54.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ecpg-errors.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-36.8. Error Handling
This section describes how you can handle exceptional conditions
and warnings in an embedded SQL program. There are two
nonexclusive facilities for this.
@@ -438,4 +438,4 @@
-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-15-15.8/doc/src/sgml/html/ecpg-informix-compat.html postgresql-15-15.9/doc/src/sgml/html/ecpg-informix-compat.html
--- postgresql-15-15.8/doc/src/sgml/html/ecpg-informix-compat.html 2024-08-05 20:21:54.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ecpg-informix-compat.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-36.15. Informix Compatibility Mode
ecpg can be run in a so-called Informix compatibility mode. If
this mode is active, it tries to behave as if it were the Informix
precompiler for Informix E/SQL. Generally spoken this will allow you to use
@@ -889,4 +889,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-15-15.8/doc/src/sgml/html/ecpg-library.html postgresql-15-15.9/doc/src/sgml/html/ecpg-library.html
--- postgresql-15-15.8/doc/src/sgml/html/ecpg-library.html 2024-08-05 20:21:54.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ecpg-library.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-36.11. Library Functions
The libecpg library primarily contains
“hidden” functions that are used to implement the
functionality expressed by the embedded SQL commands. But there
@@ -43,4 +43,4 @@
returns true if you are connected to a database and false if not.
connection_name can be NULL
if a single connection is being used.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/ecpg-lo.html postgresql-15-15.9/doc/src/sgml/html/ecpg-lo.html
--- postgresql-15-15.8/doc/src/sgml/html/ecpg-lo.html 2024-08-05 20:21:54.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ecpg-lo.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-36.12. Large Objects
Large objects are not directly supported by ECPG, but ECPG
application can manipulate large objects through the libpq large
object functions, obtaining the necessary PGconn
@@ -97,4 +97,4 @@
EXEC SQL DISCONNECT ALL;
return 0;
}
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/ecpg-oracle-compat.html postgresql-15-15.9/doc/src/sgml/html/ecpg-oracle-compat.html
--- postgresql-15-15.8/doc/src/sgml/html/ecpg-oracle-compat.html 2024-08-05 20:21:54.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ecpg-oracle-compat.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-36.16. Oracle Compatibility Mode
ecpg can be run in a so-called Oracle
compatibility mode. If this mode is active, it tries to
behave as if it were Oracle Pro*C.
@@ -16,4 +16,4 @@
Set the null indicator to -1 when character
arrays receive empty character string types
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/ecpg-pgtypes.html postgresql-15-15.9/doc/src/sgml/html/ecpg-pgtypes.html
--- postgresql-15-15.8/doc/src/sgml/html/ecpg-pgtypes.html 2024-08-05 20:21:54.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ecpg-pgtypes.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-36.6. pgtypes Library
The pgtypes library maps PostgreSQL database
types to C equivalents that can be used in C programs. It also offers
functions to do basic calculations with those types within C, i.e., without
@@ -762,4 +762,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-15-15.8/doc/src/sgml/html/ecpg-preproc.html postgresql-15-15.9/doc/src/sgml/html/ecpg-preproc.html
--- postgresql-15-15.8/doc/src/sgml/html/ecpg-preproc.html 2024-08-05 20:21:54.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ecpg-preproc.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-36.9. Preprocessor Directives
Several preprocessor directives are available that modify how
the ecpg preprocessor parses and processes a
file.
@@ -132,4 +132,4 @@
EXEC SQL SET TIMEZONE TO 'GMT';
EXEC SQL endif;
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/ecpg-process.html postgresql-15-15.9/doc/src/sgml/html/ecpg-process.html
--- postgresql-15-15.8/doc/src/sgml/html/ecpg-process.html 2024-08-05 20:21:54.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ecpg-process.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-36.10. Processing Embedded SQL Programs
Now that you have an idea how to form embedded SQL C programs, you
probably want to know how to compile them. Before compiling you
run the file through the embedded SQL
@@ -65,4 +65,4 @@
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-15-15.8/doc/src/sgml/html/ecpg-sql-allocate-descriptor.html postgresql-15-15.9/doc/src/sgml/html/ecpg-sql-allocate-descriptor.html
--- postgresql-15-15.8/doc/src/sgml/html/ecpg-sql-allocate-descriptor.html 2024-08-05 20:21:54.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ecpg-sql-allocate-descriptor.html 2024-11-11 23:01:06.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-15-15.8/doc/src/sgml/html/ecpg-sql-connect.html postgresql-15-15.9/doc/src/sgml/html/ecpg-sql-connect.html
--- postgresql-15-15.8/doc/src/sgml/html/ecpg-sql-connect.html 2024-08-05 20:21:54.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ecpg-sql-connect.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-CONNECT
CONNECT TO connection_target [ AS connection_name ] [ USER connection_user ]
CONNECT TO DEFAULT
CONNECT connection_user
@@ -106,4 +106,4 @@
CONNECT is specified in the SQL standard, but
the format of the connection parameters is
implementation-specific.
-
OPEN cursor_name
OPEN cursor_name USING value [, ... ]
OPEN cursor_name USING SQL DESCRIPTOR descriptor_name
@@ -28,4 +28,4 @@
EXEC SQL OPEN :curname1;
In Section 36.3 you saw how you can execute SQL
statements from an embedded SQL program. Some of those statements
only used fixed values and did not provide a way to insert
@@ -878,4 +878,4 @@
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-15-15.8/doc/src/sgml/html/ecpg.html postgresql-15-15.9/doc/src/sgml/html/ecpg.html
--- postgresql-15-15.8/doc/src/sgml/html/ecpg.html 2024-08-05 20:21:54.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/ecpg.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 36. ECPG — Embedded SQL in C
This chapter describes the embedded SQL package
for PostgreSQL. It was written by
Linus Tolke (<linus@epact.se>) and Michael Meskes
@@ -10,4 +10,4 @@
This documentation is quite incomplete. But since this
interface is standardized, additional information can be found in
many resources about SQL.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/encryption-options.html postgresql-15-15.9/doc/src/sgml/html/encryption-options.html
--- postgresql-15-15.8/doc/src/sgml/html/encryption-options.html 2024-08-05 20:21:51.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/encryption-options.html 2024-11-11 23:01:02.000000000 +0000
@@ -1,5 +1,5 @@
-19.8. Encryption Options
PostgreSQL offers encryption at several
levels, and provides flexibility in protecting data from disclosure
due to database server theft, unscrupulous administrators, and
@@ -81,4 +81,4 @@
never appears on the database server. Data is encrypted on the
client before being sent to the server, and database results have
to be decrypted on the client before being used.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/errcodes-appendix.html postgresql-15-15.9/doc/src/sgml/html/errcodes-appendix.html
--- postgresql-15-15.8/doc/src/sgml/html/errcodes-appendix.html 2024-08-05 20:22:08.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/errcodes-appendix.html 2024-11-11 23:01:20.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
@@ -20,7 +20,7 @@
what to do from the error class.
Table A.1 lists all the error codes defined in
- PostgreSQL 15.8. (Some are not actually
+ PostgreSQL 15.9. (Some are not actually
used at present, but are defined by the SQL standard.)
The error classes are also shown. For each error class there is a
“standard” error code having the last three characters
@@ -42,4 +42,4 @@
As of PostgreSQL 9.3, complete coverage for this feature
exists only for errors in SQLSTATE class 23 (integrity constraint
violation), but this is likely to be expanded in future.
-
Table A.1. PostgreSQL Error Codes
Error Code
Condition Name
Class 00 — Successful Completion
00000
successful_completion
Class 01 — Warning
01000
warning
0100C
dynamic_result_sets_returned
01008
implicit_zero_bit_padding
01003
null_value_eliminated_in_set_function
01007
privilege_not_granted
01006
privilege_not_revoked
01004
string_data_right_truncation
01P01
deprecated_feature
Class 02 — No Data (this is also a warning class per the SQL standard)
Class 2B — Dependent Privilege Descriptors Still Exist
2B000
dependent_privilege_descriptors_still_exist
2BP01
dependent_objects_still_exist
Class 2D — Invalid Transaction Termination
2D000
invalid_transaction_termination
Class 2F — SQL Routine Exception
2F000
sql_routine_exception
2F005
function_executed_no_return_statement
2F002
modifying_sql_data_not_permitted
2F003
prohibited_sql_statement_attempted
2F004
reading_sql_data_not_permitted
Class 34 — Invalid Cursor Name
34000
invalid_cursor_name
Class 38 — External Routine Exception
38000
external_routine_exception
38001
containing_sql_not_permitted
38002
modifying_sql_data_not_permitted
38003
prohibited_sql_statement_attempted
38004
reading_sql_data_not_permitted
Class 39 — External Routine Invocation Exception
39000
external_routine_invocation_exception
39001
invalid_sqlstate_returned
39004
null_value_not_allowed
39P01
trigger_protocol_violated
39P02
srf_protocol_violated
39P03
event_trigger_protocol_violated
Class 3B — Savepoint Exception
3B000
savepoint_exception
3B001
invalid_savepoint_specification
Class 3D — Invalid Catalog Name
3D000
invalid_catalog_name
Class 3F — Invalid Schema Name
3F000
invalid_schema_name
Class 40 — Transaction Rollback
40000
transaction_rollback
40002
transaction_integrity_constraint_violation
40001
serialization_failure
40003
statement_completion_unknown
40P01
deadlock_detected
Class 42 — Syntax Error or Access Rule Violation
42000
syntax_error_or_access_rule_violation
42601
syntax_error
42501
insufficient_privilege
42846
cannot_coerce
42803
grouping_error
42P20
windowing_error
42P19
invalid_recursion
42830
invalid_foreign_key
42602
invalid_name
42622
name_too_long
42939
reserved_name
42804
datatype_mismatch
42P18
indeterminate_datatype
42P21
collation_mismatch
42P22
indeterminate_collation
42809
wrong_object_type
428C9
generated_always
42703
undefined_column
42883
undefined_function
42P01
undefined_table
42P02
undefined_parameter
42704
undefined_object
42701
duplicate_column
42P03
duplicate_cursor
42P04
duplicate_database
42723
duplicate_function
42P05
duplicate_prepared_statement
42P06
duplicate_schema
42P07
duplicate_table
42712
duplicate_alias
42710
duplicate_object
42702
ambiguous_column
42725
ambiguous_function
42P08
ambiguous_parameter
42P09
ambiguous_alias
42P10
invalid_column_reference
42611
invalid_column_definition
42P11
invalid_cursor_definition
42P12
invalid_database_definition
42P13
invalid_function_definition
42P14
invalid_prepared_statement_definition
42P15
invalid_schema_definition
42P16
invalid_table_definition
42P17
invalid_object_definition
Class 44 — WITH CHECK OPTION Violation
44000
with_check_option_violation
Class 53 — Insufficient Resources
53000
insufficient_resources
53100
disk_full
53200
out_of_memory
53300
too_many_connections
53400
configuration_limit_exceeded
Class 54 — Program Limit Exceeded
54000
program_limit_exceeded
54001
statement_too_complex
54011
too_many_columns
54023
too_many_arguments
Class 55 — Object Not In Prerequisite State
55000
object_not_in_prerequisite_state
55006
object_in_use
55P02
cant_change_runtime_param
55P03
lock_not_available
55P04
unsafe_new_enum_value_usage
Class 57 — Operator Intervention
57000
operator_intervention
57014
query_canceled
57P01
admin_shutdown
57P02
crash_shutdown
57P03
cannot_connect_now
57P04
database_dropped
57P05
idle_session_timeout
Class 58 — System Error (errors external to PostgreSQL itself)
58000
system_error
58030
io_error
58P01
undefined_file
58P02
duplicate_file
Class 72 — Snapshot Failure
72000
snapshot_too_old
Class F0 — Configuration File Error
F0000
config_file_error
F0001
lock_file_exists
Class HV — Foreign Data Wrapper Error (SQL/MED)
HV000
fdw_error
HV005
fdw_column_name_not_found
HV002
fdw_dynamic_parameter_value_needed
HV010
fdw_function_sequence_error
HV021
fdw_inconsistent_descriptor_information
HV024
fdw_invalid_attribute_value
HV007
fdw_invalid_column_name
HV008
fdw_invalid_column_number
HV004
fdw_invalid_data_type
HV006
fdw_invalid_data_type_descriptors
HV091
fdw_invalid_descriptor_field_identifier
HV00B
fdw_invalid_handle
HV00C
fdw_invalid_option_index
HV00D
fdw_invalid_option_name
HV090
fdw_invalid_string_length_or_buffer_length
HV00A
fdw_invalid_string_format
HV009
fdw_invalid_use_of_null_pointer
HV014
fdw_too_many_handles
HV001
fdw_out_of_memory
HV00P
fdw_no_schemas
HV00J
fdw_option_name_not_found
HV00K
fdw_reply_handle
HV00Q
fdw_schema_not_found
HV00R
fdw_table_not_found
HV00L
fdw_unable_to_create_execution
HV00M
fdw_unable_to_create_reply
HV00N
fdw_unable_to_establish_connection
Class P0 — PL/pgSQL Error
P0000
plpgsql_error
P0001
raise_exception
P0002
no_data_found
P0003
too_many_rows
P0004
assert_failure
Class XX — Internal Error
XX000
internal_error
XX001
data_corrupted
XX002
index_corrupted
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/error-message-reporting.html postgresql-15-15.9/doc/src/sgml/html/error-message-reporting.html
--- postgresql-15-15.8/doc/src/sgml/html/error-message-reporting.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/error-message-reporting.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-56.2. Reporting Errors Within the Server
Error, warning, and log messages generated within the server code
should be created using ereport, or its older cousin
elog. The use of this function is complex enough to
@@ -247,4 +247,4 @@
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-15-15.8/doc/src/sgml/html/error-style-guide.html postgresql-15-15.9/doc/src/sgml/html/error-style-guide.html
--- postgresql-15-15.8/doc/src/sgml/html/error-style-guide.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/error-style-guide.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-56.3. Error Message Style Guide
This style guide is offered in the hope of maintaining a consistent,
user-friendly style throughout all the messages generated by
PostgreSQL.
@@ -247,4 +247,4 @@
Keep in mind that error message texts need to be translated into other
languages. Follow the guidelines in Section 57.2.2
to avoid making life difficult for translators.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/event-log-registration.html postgresql-15-15.9/doc/src/sgml/html/event-log-registration.html
--- postgresql-15-15.8/doc/src/sgml/html/event-log-registration.html 2024-08-05 20:21:51.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/event-log-registration.html 2024-11-11 23:01:02.000000000 +0000
@@ -1,5 +1,5 @@
-19.12. Registering Event Log on Windows
To register a Windowsevent log library with the operating system,
issue this command:
@@ -25,4 +25,4 @@
To enable event logging in the database server, modify
log_destination to include
eventlog in postgresql.conf.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/event-trigger-definition.html postgresql-15-15.9/doc/src/sgml/html/event-trigger-definition.html
--- postgresql-15-15.8/doc/src/sgml/html/event-trigger-definition.html 2024-08-05 20:21:56.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/event-trigger-definition.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-40.1. Overview of Event Trigger Behavior
An event trigger fires whenever the event with which it is associated
occurs in the database in which it is defined. Currently, the only
supported events are
@@ -47,6 +47,11 @@
control statements are available to rewrite a table,
like CLUSTER and VACUUM,
the table_rewrite event is not triggered by them.
+ To find the OID of the table that was rewritten, use the function
+ pg_event_trigger_table_rewrite_oid() (see
+ Section 9.29). To discover the reason(s)
+ for the rewrite, use the function
+ pg_event_trigger_table_rewrite_reason().
Event triggers (like other functions) cannot be executed in an aborted
transaction. Thus, if a DDL command fails with an error, any associated
@@ -75,4 +80,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-15-15.8/doc/src/sgml/html/event-trigger-example.html postgresql-15-15.9/doc/src/sgml/html/event-trigger-example.html
--- postgresql-15-15.8/doc/src/sgml/html/event-trigger-example.html 2024-08-05 20:21:56.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/event-trigger-example.html 2024-11-11 23:01:08.000000000 +0000
@@ -1,5 +1,5 @@
-40.4. A Complete Event Trigger Example
Here is a very simple example of an event trigger function written in C.
(Examples of triggers written in procedural languages can be found in
the documentation of the procedural languages.)
@@ -75,4 +75,4 @@
(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-15-15.8/doc/src/sgml/html/event-trigger-interface.html postgresql-15-15.9/doc/src/sgml/html/event-trigger-interface.html
--- postgresql-15-15.8/doc/src/sgml/html/event-trigger-interface.html 2024-08-05 20:21:56.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/event-trigger-interface.html 2024-11-11 23:01:08.000000000 +0000
@@ -1,5 +1,5 @@
-40.3. Writing Event Trigger Functions in C
This section describes the low-level details of the interface to an
event trigger function. This information is only needed when writing
event trigger functions in C. If you are using a higher-level language
@@ -65,4 +65,4 @@
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-15-15.8/doc/src/sgml/html/event-trigger-matrix.html postgresql-15-15.9/doc/src/sgml/html/event-trigger-matrix.html
--- postgresql-15-15.8/doc/src/sgml/html/event-trigger-matrix.html 2024-08-05 20:21:56.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/event-trigger-matrix.html 2024-11-11 23:01:08.000000000 +0000
@@ -1,5 +1,5 @@
-40.2. Event Trigger Firing Matrix
To supplement the trigger mechanism discussed in Chapter 39,
PostgreSQL also provides event triggers. Unlike regular
triggers, which are attached to a single table and capture only DML events,
@@ -9,4 +9,4 @@
Like regular triggers, event triggers can be written in any procedural
language that includes event trigger support, or in C, but not in plain
SQL.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/executor.html postgresql-15-15.9/doc/src/sgml/html/executor.html
--- postgresql-15-15.8/doc/src/sgml/html/executor.html 2024-08-05 20:22:05.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/executor.html 2024-11-11 23:01:16.000000000 +0000
@@ -1,5 +1,5 @@
-52.6. Executor
The executor takes the plan created by the
planner/optimizer and recursively processes it to extract the required set
of rows. This is essentially a demand-pull pipeline mechanism.
@@ -75,4 +75,4 @@
trivial plan tree consisting of a single Result
node, which computes just one result row, feeding that up
to ModifyTable to perform the insertion.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/explicit-joins.html postgresql-15-15.9/doc/src/sgml/html/explicit-joins.html
--- postgresql-15-15.8/doc/src/sgml/html/explicit-joins.html 2024-08-05 20:21:50.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/explicit-joins.html 2024-11-11 23:01:02.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.
@@ -141,4 +141,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-15-15.8/doc/src/sgml/html/explicit-locking.html postgresql-15-15.9/doc/src/sgml/html/explicit-locking.html
--- postgresql-15-15.8/doc/src/sgml/html/explicit-locking.html 2024-08-05 20:21:50.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/explicit-locking.html 2024-11-11 23:01:02.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
@@ -393,4 +393,4 @@
The functions provided to manipulate advisory locks are described in
Section 9.27.10.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/extend-extensions.html postgresql-15-15.9/doc/src/sgml/html/extend-extensions.html
--- postgresql-15-15.8/doc/src/sgml/html/extend-extensions.html 2024-08-05 20:21:56.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/extend-extensions.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-38.17. Packaging Related Objects into an Extension
38.17. Packaging Related Objects into an Extension
A useful extension to PostgreSQL typically includes
multiple SQL objects; for example, a new data type will require new
functions, new operators, and probably new index operator classes.
@@ -623,4 +623,4 @@
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-15-15.8/doc/src/sgml/html/extend-how.html postgresql-15-15.9/doc/src/sgml/html/extend-how.html
--- postgresql-15-15.8/doc/src/sgml/html/extend-how.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/extend-how.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-38.1. How Extensibility Works
PostgreSQL is extensible because its operation is
catalog-driven. If you are familiar with standard
relational database systems, you know that they store information
@@ -30,4 +30,4 @@
fly” makes PostgreSQL uniquely
suited for rapid prototyping of new applications and storage
structures.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/extend-pgxs.html postgresql-15-15.9/doc/src/sgml/html/extend-pgxs.html
--- postgresql-15-15.8/doc/src/sgml/html/extend-pgxs.html 2024-08-05 20:21:56.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/extend-pgxs.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-38.18. Extension Building Infrastructure
If you are thinking about distributing your
PostgreSQL extension modules, setting up a
portable build system for them can be fairly difficult. Therefore
@@ -227,4 +227,4 @@
output_iso/results/ directory (for tests in
ISOLATION), then copy them to
expected/ if they match what you expect from the test.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/extend-type-system.html postgresql-15-15.9/doc/src/sgml/html/extend-type-system.html
--- postgresql-15-15.8/doc/src/sgml/html/extend-type-system.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/extend-type-system.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-38.2. The PostgreSQL Type System
In the sections that follow, we will discuss how you
can extend the PostgreSQL
SQL query language by adding:
@@ -17,4 +17,4 @@
packages of related objects (starting in Section 38.17)
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/external-admin-tools.html postgresql-15-15.9/doc/src/sgml/html/external-admin-tools.html
--- postgresql-15-15.8/doc/src/sgml/html/external-admin-tools.html 2024-08-05 20:22:12.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/external-admin-tools.html 2024-11-11 23:01:23.000000000 +0000
@@ -1,7 +1,7 @@
-H.2. Administration Tools
There are several administration tools available for
PostgreSQL. The most popular is
pgAdmin,
and there are several commercially available ones as well.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/external-extensions.html postgresql-15-15.9/doc/src/sgml/html/external-extensions.html
--- postgresql-15-15.8/doc/src/sgml/html/external-extensions.html 2024-08-05 20:22:12.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/external-extensions.html 2024-11-11 23:01:23.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
@@ -11,4 +11,4 @@
externally. For example, Slony-I is a popular
primary/standby replication solution that is developed independently
from the core project.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/external-interfaces.html postgresql-15-15.9/doc/src/sgml/html/external-interfaces.html
--- postgresql-15-15.8/doc/src/sgml/html/external-interfaces.html 2024-08-05 20:22:12.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/external-interfaces.html 2024-11-11 23:01:23.000000000 +0000
@@ -1,5 +1,5 @@
-H.1. Client Interfaces
PostgreSQL includes several procedural
languages with the base distribution: PL/pgSQL, PL/Tcl,
PL/Perl, and PL/Python.
@@ -15,4 +15,4 @@
and documentation.
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-15-15.8/doc/src/sgml/html/fdw-callbacks.html postgresql-15-15.9/doc/src/sgml/html/fdw-callbacks.html
--- postgresql-15-15.8/doc/src/sgml/html/fdw-callbacks.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/fdw-callbacks.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-59.2. Foreign Data Wrapper Callback Routines
The FDW handler function returns a palloc'd FdwRoutine
struct containing pointers to the callback functions described below.
The scan-related functions are required, the rest are optional.
@@ -1254,4 +1254,4 @@
callback may use reparameterize_path_by_child,
adjust_appendrel_attrs or
adjust_appendrel_attrs_multilevel as required.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/fdw-functions.html postgresql-15-15.9/doc/src/sgml/html/fdw-functions.html
--- postgresql-15-15.8/doc/src/sgml/html/fdw-functions.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/fdw-functions.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-59.1. Foreign Data Wrapper Functions
The FDW author needs to implement a handler function, and optionally
a validator function. Both functions must be written in a compiled
language such as C, using the version-1 interface.
@@ -30,4 +30,4 @@
AttributeRelationId
ForeignDataWrapperRelationId
ForeignServerRelationId
ForeignTableRelationId
UserMappingRelationId
If no validator function is supplied, options are not checked at object
creation time or object alteration time.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/fdw-helpers.html postgresql-15-15.9/doc/src/sgml/html/fdw-helpers.html
--- postgresql-15-15.8/doc/src/sgml/html/fdw-helpers.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/fdw-helpers.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-59.3. Foreign Data Wrapper Helper Functions
Several helper functions are exported from the core server so that
authors of foreign data wrappers can get easy access to attributes of
FDW-related objects, such as FDW options.
@@ -111,4 +111,4 @@
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-15-15.8/doc/src/sgml/html/fdw-planning.html postgresql-15-15.9/doc/src/sgml/html/fdw-planning.html
--- postgresql-15-15.8/doc/src/sgml/html/fdw-planning.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/fdw-planning.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-59.4. Foreign Data Wrapper Query Planning
The FDW callback functions GetForeignRelSize,
GetForeignPaths, GetForeignPlan,
PlanForeignModify, GetForeignJoinPaths,
@@ -188,4 +188,4 @@
exclusion constraints on remote tables are not locally known. This
in turn implies that ON CONFLICT DO UPDATE is not supported,
since the specification is mandatory there.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/fdw-row-locking.html postgresql-15-15.9/doc/src/sgml/html/fdw-row-locking.html
--- postgresql-15-15.8/doc/src/sgml/html/fdw-row-locking.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/fdw-row-locking.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-59.5. Row Locking in Foreign Data Wrappers
If an FDW's underlying storage mechanism has a concept of locking
individual rows to prevent concurrent updates of those rows, it is
usually worthwhile for the FDW to perform row-level locking with as
@@ -90,4 +90,4 @@
in src/include/nodes/plannodes.h, and the comments for
ExecRowMark in src/include/nodes/execnodes.h for
additional information.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/fdwhandler.html postgresql-15-15.9/doc/src/sgml/html/fdwhandler.html
--- postgresql-15-15.8/doc/src/sgml/html/fdwhandler.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/fdwhandler.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 59. Writing a Foreign Data Wrapper
All operations on a foreign table are handled through its foreign data
wrapper, which consists of a set of functions that the core server
calls. The foreign data wrapper is responsible for fetching
@@ -18,4 +18,4 @@
However, PostgreSQL does not implement that API, because the effort to
accommodate it into PostgreSQL would be large, and the standard API hasn't
gained wide adoption anyway.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/features-sql-standard.html postgresql-15-15.9/doc/src/sgml/html/features-sql-standard.html
--- postgresql-15-15.8/doc/src/sgml/html/features-sql-standard.html 2024-08-05 20:22:10.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/features-sql-standard.html 2024-11-11 23:01:21.000000000 +0000
@@ -1,4 +1,4 @@
-D.1. Supported Features
This section attempts to outline to what extent
PostgreSQL conforms to the current SQL
standard. The following information is not a full statement of
@@ -70,4 +70,4 @@
Feature codes containing a hyphen are subfeatures. Therefore, if a
particular subfeature is not supported, the main feature is listed
as unsupported even if some other subfeatures are supported.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/file-fdw.html postgresql-15-15.9/doc/src/sgml/html/file-fdw.html
--- postgresql-15-15.8/doc/src/sgml/html/file-fdw.html 2024-08-05 20:22:11.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/file-fdw.html 2024-11-11 23:01:22.000000000 +0000
@@ -1,5 +1,5 @@
-F.16. file_fdw
The file_fdw module provides the foreign-data wrapper
file_fdw, which can be used to access data
files in the server's file system, or to execute programs on the server
@@ -142,4 +142,4 @@
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-15-15.8/doc/src/sgml/html/functions-admin.html postgresql-15-15.9/doc/src/sgml/html/functions-admin.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-admin.html 2024-08-05 20:21:49.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-admin.html 2024-11-11 23:01:01.000000000 +0000
@@ -1,5 +1,5 @@
-9.27. System Administration Functions
The functions described in this section are used to control and
monitor a PostgreSQL installation.
9.27.1. Configuration Settings Functions
@@ -1645,4 +1645,4 @@
This will either obtain the lock immediately and
return true, or return false
without waiting if the lock cannot be acquired immediately.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/functions-aggregate.html postgresql-15-15.9/doc/src/sgml/html/functions-aggregate.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-aggregate.html 2024-08-05 20:21:49.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-aggregate.html 2024-11-11 23:01:00.000000000 +0000
@@ -1,5 +1,5 @@
-9.21. Aggregate Functions
Aggregate functions compute a single result
from a set of input values. The built-in general-purpose aggregate
functions are listed in Table 9.58
@@ -726,4 +726,4 @@
neither make nor model was grouped
by in the last row (which therefore is an aggregate over all the input
rows).
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/functions-array.html postgresql-15-15.9/doc/src/sgml/html/functions-array.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-array.html 2024-08-05 20:21:48.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-array.html 2024-11-11 23:01:00.000000000 +0000
@@ -1,5 +1,5 @@
-9.19. Array Functions and Operators
Table 9.52 shows the specialized operators
available for array types.
In addition to those, the usual comparison operators shown in Table 9.1 are available for
@@ -382,4 +382,4 @@
See also Section 9.21 about the aggregate
function array_agg for use with arrays.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/functions-binarystring.html postgresql-15-15.9/doc/src/sgml/html/functions-binarystring.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-binarystring.html 2024-08-05 20:21:48.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-binarystring.html 2024-11-11 23:00:59.000000000 +0000
@@ -1,5 +1,5 @@
-9.5. Binary String Functions and Operators
This section describes functions and operators for examining and
manipulating binary strings, that is values of type bytea.
Many of these are equivalent, in purpose and syntax, to the
@@ -507,4 +507,4 @@
See also the aggregate function string_agg in
Section 9.21 and the large object functions
in Section 35.4.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/functions-bitstring.html postgresql-15-15.9/doc/src/sgml/html/functions-bitstring.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-bitstring.html 2024-08-05 20:21:48.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-bitstring.html 2024-11-11 23:00:59.000000000 +0000
@@ -1,5 +1,5 @@
-9.6. Bit String Functions and Operators
This section describes functions and operators for examining and
manipulating bit strings, that is values of the types
bit and bit varying. (While only
@@ -232,4 +232,4 @@
Note that casting to just “bit” means casting to
bit(1), and so will deliver only the least significant
bit of the integer.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/functions-comparison.html postgresql-15-15.9/doc/src/sgml/html/functions-comparison.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-comparison.html 2024-08-05 20:21:47.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-comparison.html 2024-11-11 23:00:59.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,
@@ -212,4 +212,4 @@
for materialized views and might be useful for other specialized
purposes such as replication and B-Tree deduplication (see Section 67.4.3). They are not intended to be
generally useful for writing queries, though.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/functions-conditional.html postgresql-15-15.9/doc/src/sgml/html/functions-conditional.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-conditional.html 2024-08-05 20:21:48.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-conditional.html 2024-11-11 23:01:00.000000000 +0000
@@ -1,5 +1,5 @@
-9.18. Conditional Expressions
This section describes the SQL-compliant conditional expressions
available in PostgreSQL.
Tip
@@ -184,4 +184,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-15-15.8/doc/src/sgml/html/functions-datetime.html postgresql-15-15.9/doc/src/sgml/html/functions-datetime.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-datetime.html 2024-08-05 20:21:48.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-datetime.html 2024-11-11 23:01:00.000000000 +0000
@@ -1,5 +1,5 @@
-9.9. Date/Time Functions and Operators
Table 9.33 shows the available
functions for date/time value processing, with details appearing in
the following subsections. Table 9.32 illustrates the behaviors of
@@ -1312,4 +1312,4 @@
when calling pg_sleep or its variants. Otherwise
other sessions might have to wait for your sleeping process, slowing down
the entire system.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/functions-enum.html postgresql-15-15.9/doc/src/sgml/html/functions-enum.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-enum.html 2024-08-05 20:21:48.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-enum.html 2024-11-11 23:01:00.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.
@@ -81,4 +81,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 used in the examples.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/functions-event-triggers.html postgresql-15-15.9/doc/src/sgml/html/functions-event-triggers.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-event-triggers.html 2024-08-05 20:21:49.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-event-triggers.html 2024-11-11 23:01:01.000000000 +0000
@@ -1,5 +1,5 @@
-9.29. Event Trigger Functions
PostgreSQL provides these helper functions
to retrieve information from event triggers.
@@ -110,8 +110,12 @@
→ integer
- Returns a code explaining the reason(s) for rewriting. The exact
- meaning of the codes is release dependent.
+ Returns a code explaining the reason(s) for rewriting. The value is
+ a bitmap built from the following values: 1
+ (the table has changed its persistence), 2
+ (default value of a column has changed), 4
+ (a column has a new data type) and 8
+ (the table access method has changed).
These functions can be used in an event trigger like this:
@@ -130,4 +134,4 @@
ON table_rewrite
EXECUTE FUNCTION test_event_trigger_table_rewrite_oid();
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/functions-formatting.html postgresql-15-15.9/doc/src/sgml/html/functions-formatting.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-formatting.html 2024-08-05 20:21:48.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-formatting.html 2024-11-11 23:00:59.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
@@ -407,4 +407,4 @@
Table 9.30. Template Pattern Modifiers for Numeric Formatting
Modifier
Description
Example
FM prefix
fill mode (suppress trailing zeroes and padding blanks)
FM99.99
TH suffix
upper case ordinal number suffix
999TH
th suffix
lower case ordinal number suffix
999th
Table 9.31 shows some
examples of the use of the to_char function.
-
The geometric types point, box,
lseg, line, path,
polygon, and circle have a large set of
@@ -883,4 +883,4 @@
UPDATE t SET p[1] = ... changes the Y coordinate.
In the same way, a value of type box or lseg can be treated
as an array of two point values.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/functions-info.html postgresql-15-15.9/doc/src/sgml/html/functions-info.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-info.html 2024-08-05 20:21:49.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-info.html 2024-11-11 23:01:01.000000000 +0000
@@ -1,5 +1,5 @@
-9.26. System Information Functions and Operators
Table 9.66 shows several
functions that extract session and system information.
@@ -562,6 +562,10 @@
the role (that is, the right to do SET ROLE), while
USAGE denotes whether the privileges of the role
are immediately available without doing SET ROLE.
+ WITH ADMIN OPTION or WITH GRANT
+ OPTION can be added to either of these privilege types to
+ test whether the ADMIN privilege is held (all
+ four spellings test the same thing).
This function does not allow the special case of
setting user to public,
because the PUBLIC pseudo-role can never be a member of real roles.
@@ -1771,4 +1775,4 @@
Returns information about recovery state, as shown in
Table 9.86.
-
Table 9.83. pg_control_checkpoint Output Columns
Column Name
Data Type
checkpoint_lsn
pg_lsn
redo_lsn
pg_lsn
redo_wal_file
text
timeline_id
integer
prev_timeline_id
integer
full_page_writes
boolean
next_xid
text
next_oid
oid
next_multixact_id
xid
next_multi_offset
xid
oldest_xid
xid
oldest_xid_dbid
oid
oldest_active_xid
xid
oldest_multi_xid
xid
oldest_multi_dbid
oid
oldest_commit_ts_xid
xid
newest_commit_ts_xid
xid
checkpoint_time
timestamp with time zone
Table 9.84. pg_control_system Output Columns
Column Name
Data Type
pg_control_version
integer
catalog_version_no
integer
system_identifier
bigint
pg_control_last_modified
timestamp with time zone
Table 9.85. pg_control_init Output Columns
Column Name
Data Type
max_data_alignment
integer
database_block_size
integer
blocks_per_segment
integer
wal_block_size
integer
bytes_per_wal_segment
integer
max_identifier_length
integer
max_index_columns
integer
max_toast_chunk_size
integer
large_object_chunk_size
integer
float8_pass_by_value
boolean
data_page_checksum_version
integer
Table 9.86. pg_control_recovery Output Columns
Column Name
Data Type
min_recovery_end_lsn
pg_lsn
min_recovery_end_timeline
integer
backup_start_lsn
pg_lsn
backup_end_lsn
pg_lsn
end_of_backup_record_required
boolean
\ No newline at end of file
+
Table 9.83. pg_control_checkpoint Output Columns
Column Name
Data Type
checkpoint_lsn
pg_lsn
redo_lsn
pg_lsn
redo_wal_file
text
timeline_id
integer
prev_timeline_id
integer
full_page_writes
boolean
next_xid
text
next_oid
oid
next_multixact_id
xid
next_multi_offset
xid
oldest_xid
xid
oldest_xid_dbid
oid
oldest_active_xid
xid
oldest_multi_xid
xid
oldest_multi_dbid
oid
oldest_commit_ts_xid
xid
newest_commit_ts_xid
xid
checkpoint_time
timestamp with time zone
Table 9.84. pg_control_system Output Columns
Column Name
Data Type
pg_control_version
integer
catalog_version_no
integer
system_identifier
bigint
pg_control_last_modified
timestamp with time zone
Table 9.85. pg_control_init Output Columns
Column Name
Data Type
max_data_alignment
integer
database_block_size
integer
blocks_per_segment
integer
wal_block_size
integer
bytes_per_wal_segment
integer
max_identifier_length
integer
max_index_columns
integer
max_toast_chunk_size
integer
large_object_chunk_size
integer
float8_pass_by_value
boolean
data_page_checksum_version
integer
Table 9.86. pg_control_recovery Output Columns
Column Name
Data Type
min_recovery_end_lsn
pg_lsn
min_recovery_end_timeline
integer
backup_start_lsn
pg_lsn
backup_end_lsn
pg_lsn
end_of_backup_record_required
boolean
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/functions-json.html postgresql-15-15.9/doc/src/sgml/html/functions-json.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-json.html 2024-08-05 20:21:48.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-json.html 2024-11-11 23:01:00.000000000 +0000
@@ -1,5 +1,5 @@
-9.16. JSON Functions and Operators
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/functions-logical.html postgresql-15-15.9/doc/src/sgml/html/functions-logical.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-logical.html 2024-08-05 20:21:47.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-logical.html 2024-11-11 23:00:59.000000000 +0000
@@ -1,5 +1,5 @@
-9.1. Logical Operators
The usual logical operators are available:
@@ -33,4 +33,4 @@
without affecting the result. (However, it is not guaranteed that
the left operand is evaluated before the right operand. See Section 4.2.14 for more information about the
order of evaluation of subexpressions.)
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/functions-matching.html postgresql-15-15.9/doc/src/sgml/html/functions-matching.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-matching.html 2024-08-05 20:21:48.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-matching.html 2024-11-11 23:00:59.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
@@ -1412,4 +1412,4 @@
backslash.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/functions-math.html postgresql-15-15.9/doc/src/sgml/html/functions-math.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-math.html 2024-08-05 20:21:47.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-math.html 2024-11-11 23:00:59.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
@@ -998,4 +998,4 @@
atanh(0.5)
→ 0.5493061443340548
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/functions-net.html postgresql-15-15.9/doc/src/sgml/html/functions-net.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-net.html 2024-08-05 20:21:48.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-net.html 2024-11-11 23:01:00.000000000 +0000
@@ -1,5 +1,5 @@
-9.12. Network Address Functions and Operators
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/functions-range.html postgresql-15-15.9/doc/src/sgml/html/functions-range.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-range.html 2024-08-05 20:21:49.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-range.html 2024-11-11 23:01:00.000000000 +0000
@@ -1,5 +1,5 @@
-9.20. Range/Multirange Functions and Operators
Table 9.54 shows the specialized operators
@@ -704,4 +704,4 @@
The lower_inc, upper_inc,
lower_inf, and upper_inf
functions all return false for an empty range or multirange.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/functions-sequence.html postgresql-15-15.9/doc/src/sgml/html/functions-sequence.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-sequence.html 2024-08-05 20:21:48.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-sequence.html 2024-11-11 23:01:00.000000000 +0000
@@ -1,5 +1,5 @@
-9.17. Sequence Manipulation Functions
This section describes functions for operating on sequence
objects, also called sequence generators or just sequences.
Sequence objects are special single-row tables created with CREATE SEQUENCE.
@@ -136,4 +136,4 @@
OID by hand, however, since the regclass data type's input
converter will do the work for you. See Section 8.19
for details.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/functions-srf.html postgresql-15-15.9/doc/src/sgml/html/functions-srf.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-srf.html 2024-08-05 20:21:49.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-srf.html 2024-11-11 23:01:00.000000000 +0000
@@ -1,5 +1,5 @@
-9.25. Set Returning Functions
This section describes functions that possibly return more than one row.
The most widely used functions in this class are series generating
functions, as detailed in Table 9.64 and
@@ -215,4 +215,4 @@
pg_subtrans | 19
(19 rows)
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/functions-statistics.html postgresql-15-15.9/doc/src/sgml/html/functions-statistics.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-statistics.html 2024-08-05 20:21:49.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-statistics.html 2024-11-11 23:01:01.000000000 +0000
@@ -1,5 +1,5 @@
-9.30. Statistics Information Functions
This section describes functions and operators for examining and
manipulating string values. Strings in this context include values
of the types character, character varying,
@@ -1205,4 +1205,4 @@
The %I and %L format specifiers are particularly
useful for safely constructing dynamic SQL statements. See
Example 43.1.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/functions-subquery.html postgresql-15-15.9/doc/src/sgml/html/functions-subquery.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-subquery.html 2024-08-05 20:21:49.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-subquery.html 2024-11-11 23:01:00.000000000 +0000
@@ -1,5 +1,5 @@
-9.23. Subquery Expressions
This section describes the SQL-compliant subquery
expressions available in PostgreSQL.
All of the expression forms documented in this section return
@@ -210,4 +210,4 @@
See Section 9.24.5 for details about the meaning
of a row constructor comparison.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/functions-textsearch.html postgresql-15-15.9/doc/src/sgml/html/functions-textsearch.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-textsearch.html 2024-08-05 20:21:48.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-textsearch.html 2024-11-11 23:01:00.000000000 +0000
@@ -1,5 +1,5 @@
-9.13. Text Search Functions and Operators
ts_stat('SELECT vector FROM apod')
→ (foo,10,15) ...
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/functions-trigger.html postgresql-15-15.9/doc/src/sgml/html/functions-trigger.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-trigger.html 2024-08-05 20:21:49.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-trigger.html 2024-11-11 23:01:01.000000000 +0000
@@ -1,5 +1,5 @@
-9.28. Trigger Functions
While many uses of triggers involve user-written trigger functions,
PostgreSQL provides a few built-in trigger
functions that can be used directly in user-defined triggers. These
@@ -90,4 +90,4 @@
choose a trigger name that comes after the name of any other trigger
you might have on the table. (Hence the “z” prefix in the
example.)
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/functions-uuid.html postgresql-15-15.9/doc/src/sgml/html/functions-uuid.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-uuid.html 2024-08-05 20:21:48.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-uuid.html 2024-11-11 23:01:00.000000000 +0000
@@ -1,5 +1,5 @@
-9.14. UUID Functions
Window functions provide the ability to perform
calculations across sets of rows that are related to the current query
row. See Section 3.5 for an introduction to this
@@ -179,4 +179,4 @@
default FROM FIRST behavior is supported. (You can achieve
the result of FROM LAST by reversing the ORDER BY
ordering.)
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/functions-xml.html postgresql-15-15.9/doc/src/sgml/html/functions-xml.html
--- postgresql-15-15.8/doc/src/sgml/html/functions-xml.html 2024-08-05 20:21:48.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions-xml.html 2024-11-11 23:01:00.000000000 +0000
@@ -1,5 +1,5 @@
-9.15. XML Functions
The functions and function-like expressions described in this
section operate on values of type xml. See Section 8.13 for information about the xml
type. The function-like expressions xmlparse
@@ -909,4 +909,4 @@
will be put into content form with each such disallowed node replaced by
its string value, as defined for the XPath 1.0
string function.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/functions.html postgresql-15-15.9/doc/src/sgml/html/functions.html
--- postgresql-15-15.8/doc/src/sgml/html/functions.html 2024-08-05 20:21:49.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/functions.html 2024-11-11 23:01:01.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. This chapter
describes most of them, although additional special-purpose functions
@@ -30,4 +30,4 @@
is present in other SQL database management
systems, and in many cases this functionality is compatible and
consistent between the various implementations.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/fuzzystrmatch.html postgresql-15-15.9/doc/src/sgml/html/fuzzystrmatch.html
--- postgresql-15-15.8/doc/src/sgml/html/fuzzystrmatch.html 2024-08-05 20:22:11.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/fuzzystrmatch.html 2024-11-11 23:01:22.000000000 +0000
@@ -1,5 +1,5 @@
-F.17. 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
@@ -99,4 +99,4 @@
comparison. This is not very compact for the case of moving data
within a page, and might be improved in the future.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/geqo-biblio.html postgresql-15-15.9/doc/src/sgml/html/geqo-biblio.html
--- postgresql-15-15.8/doc/src/sgml/html/geqo-biblio.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/geqo-biblio.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-62.4. Further Reading
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/geqo-intro.html postgresql-15-15.9/doc/src/sgml/html/geqo-intro.html
--- postgresql-15-15.8/doc/src/sgml/html/geqo-intro.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/geqo-intro.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-62.1. Query Handling as a Complex Optimization Problem
62.1. Query Handling as a Complex Optimization Problem
62.1. Query Handling as a Complex Optimization Problem
Among all relational operators the most difficult one to process
and optimize is the join. The number of
possible query plans grows exponentially with the
@@ -33,4 +33,4 @@
genetic algorithm to solve the join
ordering problem in a manner that is efficient for queries
involving large numbers of joins.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/geqo-intro2.html postgresql-15-15.9/doc/src/sgml/html/geqo-intro2.html
--- postgresql-15-15.8/doc/src/sgml/html/geqo-intro2.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/geqo-intro2.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-62.2. Genetic Algorithms
The genetic algorithm (GA) is a heuristic optimization method which
operates through randomized search. The set of possible solutions for the
optimization problem is considered as a
@@ -24,4 +24,4 @@
strongly that a GA is not a pure random search for a solution to a
problem. A GA uses stochastic processes, but the result is distinctly
non-random (better than random).
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/geqo-pg-intro.html postgresql-15-15.9/doc/src/sgml/html/geqo-pg-intro.html
--- postgresql-15-15.8/doc/src/sgml/html/geqo-pg-intro.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/geqo-pg-intro.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-62.3. Genetic Query Optimization (GEQO) in PostgreSQL
62.3. Genetic Query Optimization (GEQO) in PostgreSQL
The GEQO module approaches the query
optimization problem as though it were the well-known traveling salesman
@@ -104,4 +104,4 @@
of the rest of the tour, but this is certainly not true for query
optimization. Thus it is questionable whether edge recombination
crossover is the most effective mutation procedure.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/geqo.html postgresql-15-15.9/doc/src/sgml/html/geqo.html
--- postgresql-15-15.8/doc/src/sgml/html/geqo.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/geqo.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,8 +1,8 @@
-Chapter 62. Genetic Query Optimizer
Written by Martin Utesch (<utesch@aut.tu-freiberg.de>)
for the Institute of Automatic Control at the University of Mining and Technology in Freiberg, Germany.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/gin-builtin-opclasses.html postgresql-15-15.9/doc/src/sgml/html/gin-builtin-opclasses.html
--- postgresql-15-15.8/doc/src/sgml/html/gin-builtin-opclasses.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/gin-builtin-opclasses.html 2024-11-11 23:01:19.000000000 +0000
@@ -1,5 +1,5 @@
-70.2. Built-in Operator Classes
The core PostgreSQL distribution
includes the GIN operator classes shown in
Table 70.1.
@@ -10,4 +10,4 @@
is the default. jsonb_path_ops supports fewer operators but
offers better performance for those operators.
See Section 8.14.4 for details.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/gin-examples.html postgresql-15-15.9/doc/src/sgml/html/gin-examples.html
--- postgresql-15-15.8/doc/src/sgml/html/gin-examples.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/gin-examples.html 2024-11-11 23:01:19.000000000 +0000
@@ -1,5 +1,5 @@
-70.7. Examples
The GIN interface has a high level of abstraction,
requiring the access method implementer only to implement the semantics of
the data type being accessed. The GIN layer itself
@@ -234,4 +234,4 @@
recommended that the SQL declarations of these three support functions use
the opclass's indexed data type for the query argument, even
though the actual type might be something else depending on the operator.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/gin-implementation.html postgresql-15-15.9/doc/src/sgml/html/gin-implementation.html
--- postgresql-15-15.8/doc/src/sgml/html/gin-implementation.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/gin-implementation.html 2024-11-11 23:01:19.000000000 +0000
@@ -1,5 +1,5 @@
-70.4. Implementation
Internally, a GIN index contains a B-tree index
constructed over keys, where each key is an element of one or more indexed
items (a member of an array, for example) and where each tuple in a leaf
@@ -61,4 +61,4 @@
index key, less than zero for a non-match that is still within the range
to be searched, or greater than zero if the index key is past the range
that could match.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/gin-intro.html postgresql-15-15.9/doc/src/sgml/html/gin-intro.html
--- postgresql-15-15.8/doc/src/sgml/html/gin-intro.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/gin-intro.html 2024-11-11 23:01:19.000000000 +0000
@@ -1,5 +1,5 @@
-70.1. Introduction
GIN stands for Generalized Inverted Index.
GIN is designed for handling cases where the items
to be indexed are composite values, and the queries to be handled by
@@ -37,4 +37,4 @@
maintained by Teodor Sigaev and Oleg Bartunov. There is more
information about GIN on their
website.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/gin-limit.html postgresql-15-15.9/doc/src/sgml/html/gin-limit.html
--- postgresql-15-15.8/doc/src/sgml/html/gin-limit.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/gin-limit.html 2024-11-11 23:01:19.000000000 +0000
@@ -1,5 +1,5 @@
-70.6. Limitations
GIN assumes that indexable operators are strict. This
means that extractValue will not be called at all on a null
item value (instead, a placeholder index entry is created automatically),
@@ -7,4 +7,4 @@
value either (instead, the query is presumed to be unsatisfiable). Note
however that null key values contained within a non-null composite item
or query value are supported.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/gin-tips.html postgresql-15-15.9/doc/src/sgml/html/gin-tips.html
--- postgresql-15-15.8/doc/src/sgml/html/gin-tips.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/gin-tips.html 2024-11-11 23:01:19.000000000 +0000
@@ -1,5 +1,5 @@
-70.5. GIN Tips and Tricks
Insertion into a GIN index can be slow
due to the likelihood of many keys being inserted for each item.
So, for bulk insertions into a table it is advisable to drop the GIN
@@ -55,4 +55,4 @@
From experience, values in the thousands (e.g., 5000 — 20000)
work well.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/gin.html postgresql-15-15.9/doc/src/sgml/html/gin.html
--- postgresql-15-15.8/doc/src/sgml/html/gin.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/gin.html 2024-11-11 23:01:19.000000000 +0000
@@ -1,2 +1,2 @@
-Chapter 70. GIN Indexes
The PostgreSQL source distribution includes
several examples of index methods implemented using
GiST. The core system currently provides text search
@@ -10,4 +10,4 @@
operator classes:
btree_gist
B-tree equivalent functionality for several data types
cube
Indexing for multidimensional cubes
hstore
Module for storing (key, value) pairs
intarray
RD-Tree for one-dimensional array of int4 values
ltree
Indexing for tree-like structures
pg_trgm
Text similarity using trigram matching
seg
Indexing for “float ranges”
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/gist-extensibility.html postgresql-15-15.9/doc/src/sgml/html/gist-extensibility.html
--- postgresql-15-15.8/doc/src/sgml/html/gist-extensibility.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/gist-extensibility.html 2024-11-11 23:01:19.000000000 +0000
@@ -1,5 +1,5 @@
-68.3. Extensibility
Traditionally, implementing a new index access method meant a lot of
difficult work. It was necessary to understand the inner workings of the
database, such as the lock manager and Write-Ahead Log. The
@@ -810,4 +810,4 @@
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-15-15.8/doc/src/sgml/html/gist-implementation.html postgresql-15-15.9/doc/src/sgml/html/gist-implementation.html
--- postgresql-15-15.8/doc/src/sgml/html/gist-implementation.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/gist-implementation.html 2024-11-11 23:01:19.000000000 +0000
@@ -1,5 +1,5 @@
-68.4. Implementation
The simplest way to build a GiST index is just to insert all the entries,
one by one. This tends to be slow for large indexes, because if the
index tuples are scattered across the index and the index is large enough
@@ -35,4 +35,4 @@
CREATE INDEX command. The default behavior is good for most cases, but
turning buffering off might speed up the build somewhat if the input data
is ordered.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/gist-intro.html postgresql-15-15.9/doc/src/sgml/html/gist-intro.html
--- postgresql-15-15.8/doc/src/sgml/html/gist-intro.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/gist-intro.html 2024-11-11 23:01:19.000000000 +0000
@@ -1,5 +1,5 @@
-68.1. Introduction
GiST stands for Generalized Search Tree. It is a
balanced, tree-structured access method, that acts as a base template in
which to implement arbitrary indexing schemes. B-trees, R-trees and many
@@ -20,4 +20,4 @@
maintained by Teodor Sigaev and Oleg Bartunov, and there is more
information on their
web site.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/gist.html postgresql-15-15.9/doc/src/sgml/html/gist.html
--- postgresql-15-15.8/doc/src/sgml/html/gist.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/gist.html 2024-11-11 23:01:19.000000000 +0000
@@ -1,2 +1,2 @@
-Chapter 68. GiST Indexes
With Git you will make a copy of the entire code repository
on your local machine, so you will have access to all history and branches
offline. This is the fastest and most flexible way to develop or test
@@ -39,4 +39,4 @@
Git 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-15-15.8/doc/src/sgml/html/glossary.html postgresql-15-15.9/doc/src/sgml/html/glossary.html
--- postgresql-15-15.8/doc/src/sgml/html/glossary.html 2024-08-05 20:22:12.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/glossary.html 2024-11-11 23:01:24.000000000 +0000
@@ -1,5 +1,5 @@
-Appendix M. Glossary
This is a list of terms and their meaning in the context of
PostgreSQL and relational database
systems in general.
@@ -1068,4 +1068,4 @@
It comprises many individual
WAL records written
sequentially to WAL files.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/gssapi-auth.html postgresql-15-15.9/doc/src/sgml/html/gssapi-auth.html
--- postgresql-15-15.8/doc/src/sgml/html/gssapi-auth.html 2024-08-05 20:21:51.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/gssapi-auth.html 2024-11-11 23:01:03.000000000 +0000
@@ -1,5 +1,5 @@
-21.6. GSSAPI Authentication
GSSAPI is an industry-standard protocol
for secure authentication defined in
RFC 2743.
@@ -115,4 +115,4 @@
parameter. If that is set to true, client principals are matched to
user map entries case-insensitively. krb_realm, if
set, is also matched case-insensitively.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/gssapi-enc.html postgresql-15-15.9/doc/src/sgml/html/gssapi-enc.html
--- postgresql-15-15.8/doc/src/sgml/html/gssapi-enc.html 2024-08-05 20:21:51.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/gssapi-enc.html 2024-11-11 23:01:02.000000000 +0000
@@ -1,5 +1,5 @@
-19.10. Secure TCP/IP Connections with GSSAPI Encryption
19.10. Secure TCP/IP Connections with GSSAPI Encryption
PostgreSQL also has native support for
using GSSAPI to encrypt client/server communications for
increased security. Support requires that a GSSAPI
@@ -28,4 +28,4 @@
behavior, GSSAPI encryption requires no setup beyond
that which is necessary for GSSAPI authentication. (For more information
on configuring that, see Section 21.6.)
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/hash-implementation.html postgresql-15-15.9/doc/src/sgml/html/hash-implementation.html
--- postgresql-15-15.8/doc/src/sgml/html/hash-implementation.html 2024-08-05 20:22:08.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/hash-implementation.html 2024-11-11 23:01:19.000000000 +0000
@@ -1,5 +1,5 @@
-72.2. Implementation
There are four kinds of pages in a hash index: the meta page (page zero),
which contains statically allocated control information; primary bucket
pages; overflow pages; and bitmap pages, which keep track of overflow
@@ -33,4 +33,4 @@
src/backend/access/hash/README.
The split algorithm is crash safe and can be restarted if not completed
successfully.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/hash-index.html postgresql-15-15.9/doc/src/sgml/html/hash-index.html
--- postgresql-15-15.8/doc/src/sgml/html/hash-index.html 2024-08-05 20:22:08.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/hash-index.html 2024-11-11 23:01:19.000000000 +0000
@@ -1,2 +1,2 @@
-Chapter 72. 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
@@ -74,4 +74,4 @@
The expansion occurs in the foreground, which could increase execution
time for user inserts. Thus, hash indexes may not be suitable for tables
with rapidly increasing number of rows.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/high-availability.html postgresql-15-15.9/doc/src/sgml/html/high-availability.html
--- postgresql-15-15.8/doc/src/sgml/html/high-availability.html 2024-08-05 20:21:52.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/high-availability.html 2024-11-11 23:01:04.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 27. High Availability, Load Balancing, and Replication
Chapter 27. High Availability, Load Balancing, and Replication
Database servers can work together to allow a second server to
take over quickly if the primary server fails (high
availability), or to allow several computers to serve the same
@@ -54,4 +54,4 @@
The remainder of this section outlines various failover, replication,
and load balancing solutions.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/history.html postgresql-15-15.9/doc/src/sgml/html/history.html
--- postgresql-15-15.8/doc/src/sgml/html/history.html 2024-08-05 20:21:46.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/history.html 2024-11-11 23:00:57.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
@@ -137,4 +137,4 @@
Details about what has happened in PostgreSQL since
then can be found in Appendix E.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/hot-standby.html postgresql-15-15.9/doc/src/sgml/html/hot-standby.html
--- postgresql-15-15.8/doc/src/sgml/html/hot-standby.html 2024-08-05 20:21:52.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/hot-standby.html 2024-11-11 23:01:04.000000000 +0000
@@ -1,5 +1,5 @@
-27.4. Hot Standby
Hot standby is the term used to describe the ability to connect to
the server and run read-only queries while the server is in archive
recovery or standby mode. This
@@ -572,4 +572,4 @@
hot standby mode will generate an error.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/how-parallel-query-works.html postgresql-15-15.9/doc/src/sgml/html/how-parallel-query-works.html
--- postgresql-15-15.8/doc/src/sgml/html/how-parallel-query-works.html 2024-08-05 20:21:50.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/how-parallel-query-works.html 2024-11-11 23:01:02.000000000 +0000
@@ -1,5 +1,5 @@
-15.1. How Parallel Query Works
When the optimizer determines that parallel query is the fastest execution
strategy for a particular query, it will create a query plan that includes
a Gather or Gather Merge
@@ -68,4 +68,4 @@
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-15-15.8/doc/src/sgml/html/hstore.html postgresql-15-15.9/doc/src/sgml/html/hstore.html
--- postgresql-15-15.8/doc/src/sgml/html/hstore.html 2024-08-05 20:22:11.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/hstore.html 2024-11-11 23:01:22.000000000 +0000
@@ -1,5 +1,5 @@
-F.18. hstore
This module implements the hstore data type for storing sets of
key/value pairs within a single PostgreSQL value.
This can be useful in various scenarios, such as rows with many attributes
@@ -696,4 +696,4 @@
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/index-api.html postgresql-15-15.9/doc/src/sgml/html/index-api.html
--- postgresql-15-15.8/doc/src/sgml/html/index-api.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/index-api.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-64.1. Basic API Structure for Indexes
Each index access method is described by a row in the
pg_am
system catalog. The pg_am entry
@@ -177,4 +177,4 @@
sensible: it means that there can only be one key column, but there can
also be included column(s). Also, included columns must be allowed to be
null, independently of amoptionalkey.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/index-cost-estimation.html postgresql-15-15.9/doc/src/sgml/html/index-cost-estimation.html
--- postgresql-15-15.8/doc/src/sgml/html/index-cost-estimation.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/index-cost-estimation.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-64.6. Index Cost Estimation Functions
The amcostestimate function is given information describing
a possible index scan, including lists of WHERE and ORDER BY clauses that
have been determined to be usable with the index. It must return estimates
@@ -139,4 +139,4 @@
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-15-15.8/doc/src/sgml/html/index-functions.html postgresql-15-15.9/doc/src/sgml/html/index-functions.html
--- postgresql-15-15.8/doc/src/sgml/html/index-functions.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/index-functions.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-64.2. Index Access Method Functions
The index construction and maintenance functions that an index access
method must provide in IndexAmRoutine are:
@@ -484,4 +484,4 @@
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-15-15.8/doc/src/sgml/html/index-locking.html postgresql-15-15.9/doc/src/sgml/html/index-locking.html
--- postgresql-15-15.8/doc/src/sgml/html/index-locking.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/index-locking.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-64.4. Index Locking Considerations
Index access methods must handle concurrent updates
of the index by multiple processes.
The core PostgreSQL system obtains
@@ -88,4 +88,4 @@
integrity. When the flag is set, it indicates that the index access
method implements finer-grained predicate locking, which will tend to
reduce the frequency of such transaction cancellations.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/index-scanning.html postgresql-15-15.9/doc/src/sgml/html/index-scanning.html
--- postgresql-15-15.8/doc/src/sgml/html/index-scanning.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/index-scanning.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-64.3. Index Scanning
In an index scan, the index access method is responsible for regurgitating
the TIDs of all the tuples it has been told about that match the
scan keys. The access method is not involved in
@@ -120,4 +120,4 @@
Note that it is permitted for an access method to implement only
amgetbitmap and not amgettuple, or vice versa,
if its internal implementation is unsuited to one API or the other.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/index-unique-checks.html postgresql-15-15.9/doc/src/sgml/html/index-unique-checks.html
--- postgresql-15-15.8/doc/src/sgml/html/index-unique-checks.html 2024-08-05 20:22:07.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/index-unique-checks.html 2024-11-11 23:01:18.000000000 +0000
@@ -1,5 +1,5 @@
-64.5. Index Uniqueness Checks
PostgreSQL enforces SQL uniqueness constraints
using unique indexes, which are indexes that disallow
multiple entries with identical keys. An access method that supports this
@@ -106,4 +106,4 @@
target row is found in the recheck verifies that we are scanning
for the same tuple values as were used in the original insertion.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/index.html postgresql-15-15.9/doc/src/sgml/html/index.html
--- postgresql-15-15.8/doc/src/sgml/html/index.html 2024-08-05 20:22:14.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/index.html 2024-11-11 23:01:25.000000000 +0000
@@ -1,2 +1,2 @@
-PostgreSQL 15.8 Documentation
This chapter defines the interface between the core
PostgreSQL system and index access
methods, which manage individual index types. The core system
@@ -32,4 +32,4 @@
statement; but indexes do not deal with those, either.) Index entries for
dead tuples are reclaimed (by vacuuming) when the dead tuples themselves
are reclaimed.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/indexes-bitmap-scans.html postgresql-15-15.9/doc/src/sgml/html/indexes-bitmap-scans.html
--- postgresql-15-15.8/doc/src/sgml/html/indexes-bitmap-scans.html 2024-08-05 20:21:49.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/indexes-bitmap-scans.html 2024-11-11 23:01:01.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)
@@ -58,4 +58,4 @@
common. If one of the types of query is much less common than the
others, you'd probably settle for creating just the two indexes that
best match the common types.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/indexes-collations.html postgresql-15-15.9/doc/src/sgml/html/indexes-collations.html
--- postgresql-15-15.8/doc/src/sgml/html/indexes-collations.html 2024-08-05 20:21:50.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/indexes-collations.html 2024-11-11 23:01:01.000000000 +0000
@@ -1,5 +1,5 @@
-11.11. 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.
@@ -79,4 +79,4 @@
appropriate, then you might have to resort to forcing index usage
explicitly. You might also want to contact the
PostgreSQL developers to examine the issue.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/indexes-expressional.html postgresql-15-15.9/doc/src/sgml/html/indexes-expressional.html
--- postgresql-15-15.8/doc/src/sgml/html/indexes-expressional.html 2024-08-05 20:21:50.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/indexes-expressional.html 2024-11-11 23:01:01.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
@@ -46,4 +46,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-15-15.8/doc/src/sgml/html/indexes-index-only-scans.html postgresql-15-15.9/doc/src/sgml/html/indexes-index-only-scans.html
--- postgresql-15-15.8/doc/src/sgml/html/indexes-index-only-scans.html 2024-08-05 20:21:50.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/indexes-index-only-scans.html 2024-11-11 23:01:01.000000000 +0000
@@ -1,5 +1,5 @@
-11.9. Index-Only Scans and Covering Indexes
All indexes in PostgreSQL
are secondary indexes, meaning that each index is
stored separately from the table's main data area (which is called the
@@ -206,4 +206,4 @@
checked in the plan. PostgreSQL versions 9.6
and later will recognize such cases and allow index-only scans to be
generated, but older versions will not.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/indexes-intro.html postgresql-15-15.9/doc/src/sgml/html/indexes-intro.html
--- postgresql-15-15.8/doc/src/sgml/html/indexes-intro.html 2024-08-05 20:21:49.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/indexes-intro.html 2024-11-11 23:01:01.000000000 +0000
@@ -1,5 +1,5 @@
-11.1. Introduction
An index definition can specify an operator
class for each column of an index.
@@ -104,4 +104,4 @@
commands \dAc, \dAf,
and \dAo, which provide slightly more sophisticated
versions of these queries.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/indexes-ordering.html postgresql-15-15.9/doc/src/sgml/html/indexes-ordering.html
--- postgresql-15-15.8/doc/src/sgml/html/indexes-ordering.html 2024-08-05 20:21:49.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/indexes-ordering.html 2024-11-11 23:01:01.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
@@ -61,4 +61,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-15-15.8/doc/src/sgml/html/indexes-partial.html postgresql-15-15.9/doc/src/sgml/html/indexes-partial.html
--- postgresql-15-15.8/doc/src/sgml/html/indexes-partial.html 2024-08-05 20:21:50.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/indexes-partial.html 2024-11-11 23:01:01.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
@@ -209,4 +209,4 @@
far better performance is possible.
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/indexes-types.html postgresql-15-15.9/doc/src/sgml/html/indexes-types.html
--- postgresql-15-15.8/doc/src/sgml/html/indexes-types.html 2024-08-05 20:21:49.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/indexes-types.html 2024-11-11 23:01:01.000000000 +0000
@@ -1,5 +1,5 @@
-11.2. Index Types
PostgreSQL provides several index types:
B-tree, Hash, GiST, SP-GiST, GIN, BRIN, and the extension bloom.
Each index type uses a different
@@ -159,4 +159,4 @@
The BRIN operator classes included in the standard distribution are
documented in Table 71.1.
For more information see Chapter 71.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/indexes-unique.html postgresql-15-15.9/doc/src/sgml/html/indexes-unique.html
--- postgresql-15-15.8/doc/src/sgml/html/indexes-unique.html 2024-08-05 20:21:50.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/indexes-unique.html 2024-11-11 23:01:01.000000000 +0000
@@ -1,5 +1,5 @@
-11.6. Unique Indexes
Indexes can also be used to enforce uniqueness of a column's value,
or the uniqueness of the combined values of more than one column.
@@ -23,4 +23,4 @@
There's no need to manually
create indexes on unique columns; doing so would just duplicate
the automatically-created index.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/indexes.html postgresql-15-15.9/doc/src/sgml/html/indexes.html
--- postgresql-15-15.8/doc/src/sgml/html/indexes.html 2024-08-05 20:21:50.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/indexes.html 2024-11-11 23:01:01.000000000 +0000
@@ -1,8 +1,8 @@
-Chapter 11. Indexes
Indexes are a common way to enhance database performance. An index
allows the database server to find and retrieve specific rows much
faster than it could do without an index. But indexes also add
overhead to the database system as a whole, so they should be used
sensibly.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/information-schema.html postgresql-15-15.9/doc/src/sgml/html/information-schema.html
--- postgresql-15-15.8/doc/src/sgml/html/information-schema.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/information-schema.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 37. The Information Schema
The information schema consists of a set of views that contain
information about the objects defined in the current database. The
information schema is defined in the SQL standard and can therefore
@@ -28,4 +28,4 @@
issues but contain the table name to help distinguish duplicate
rows, e.g., constraint_column_usage,
constraint_table_usage, table_constraints.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-administrable-role-authorizations.html postgresql-15-15.9/doc/src/sgml/html/infoschema-administrable-role-authorizations.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-administrable-role-authorizations.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-administrable-role-authorizations.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.4. administrable_role_authorizations
The view administrable_role_authorizations
identifies all roles that the current user has the admin option
for.
@@ -25,4 +25,4 @@
Always YES
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-applicable-roles.html postgresql-15-15.9/doc/src/sgml/html/infoschema-applicable-roles.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-applicable-roles.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-applicable-roles.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.5. applicable_roles
The view applicable_roles identifies all roles
whose privileges the current user can use. This means there is
some chain of role grants from the current user to the role in
@@ -30,4 +30,4 @@
YES if the grantee has the admin option on
the role, NO if not
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-attributes.html postgresql-15-15.9/doc/src/sgml/html/infoschema-attributes.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-attributes.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-attributes.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.6. attributes
The view attributes contains information about
the attributes of composite data types defined in the database.
(Note that the view does not give information about table columns,
@@ -223,4 +223,4 @@
See also under Section 37.17, a similarly
structured view, for further information on some of the columns.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-character-sets.html postgresql-15-15.9/doc/src/sgml/html/infoschema-character-sets.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-character-sets.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-character-sets.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.7. character_sets
The view character_sets identifies the character
sets available in the current database. Since PostgreSQL does not
support multiple character sets within one database, this view only
@@ -83,4 +83,4 @@
settings of the current database. If there is no such
collation, then this column and the associated schema and
catalog columns are null.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-check-constraint-routine-usage.html postgresql-15-15.9/doc/src/sgml/html/infoschema-check-constraint-routine-usage.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-check-constraint-routine-usage.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-check-constraint-routine-usage.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.8. check_constraint_routine_usage
The view check_constraint_routine_usage
identifies routines (functions and procedures) that are used by a
check constraint. Only those routines are shown that are owned by
@@ -39,4 +39,4 @@
The “specific name” of the function. See Section 37.45 for more information.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-check-constraints.html postgresql-15-15.9/doc/src/sgml/html/infoschema-check-constraints.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-check-constraints.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-check-constraints.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.9. check_constraints
The view check_constraints contains all check
constraints, either defined on a table or on a domain, that are
owned by a currently enabled role. (The owner of the table or
@@ -29,4 +29,4 @@
The check expression of the check constraint
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-collation-character-set-applicab.html postgresql-15-15.9/doc/src/sgml/html/infoschema-collation-character-set-applicab.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-collation-character-set-applicab.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-collation-character-set-applicab.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.11. collation_character_set_applicability
The view collation_character_set_applicability
identifies which character set the available collations are
applicable to. In PostgreSQL, there is only one character set per
@@ -41,4 +41,4 @@
Name of the character set
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-collations.html postgresql-15-15.9/doc/src/sgml/html/infoschema-collations.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-collations.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-collations.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.10. collations
The view column_column_usage identifies all generated
columns that depend on another base column in the same table. Only tables
owned by a currently enabled role are included.
@@ -33,4 +33,4 @@
Name of the generated column
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-column-domain-usage.html postgresql-15-15.9/doc/src/sgml/html/infoschema-column-domain-usage.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-column-domain-usage.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-column-domain-usage.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.13. column_domain_usage
The view column_domain_usage identifies all
columns (of a table or a view) that make use of some domain defined
in the current database and owned by a currently enabled role.
@@ -43,4 +43,4 @@
Name of the column
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-column-options.html postgresql-15-15.9/doc/src/sgml/html/infoschema-column-options.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-column-options.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-column-options.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.14. column_options
The view column_options contains all the
options defined for foreign table columns in the current database. Only
those foreign table columns are shown that the current user has access to
@@ -39,4 +39,4 @@
Value of the option
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-column-privileges.html postgresql-15-15.9/doc/src/sgml/html/infoschema-column-privileges.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-column-privileges.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-column-privileges.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.15. column_privileges
The view column_privileges identifies all
privileges granted on columns to a currently enabled role or by a
currently enabled role. There is one row for each combination of
@@ -57,4 +57,4 @@
YES if the privilege is grantable, NO if not
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-column-udt-usage.html postgresql-15-15.9/doc/src/sgml/html/infoschema-column-udt-usage.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-column-udt-usage.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-column-udt-usage.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.16. column_udt_usage
The view column_udt_usage identifies all columns
that use data types owned by a currently enabled role. Note that in
PostgreSQL, built-in data types behave
@@ -49,4 +49,4 @@
Name of the column
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-columns.html postgresql-15-15.9/doc/src/sgml/html/infoschema-columns.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-columns.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-columns.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.17. columns
The view columns contains information about all
table columns (or view columns) in the database. System columns
(ctid, etc.) are not included. Only those columns are
@@ -334,4 +334,4 @@
columns with their associated data types and treat domains as
separate types, you could write coalesce(domain_name,
udt_name), etc.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-constraint-column-usage.html postgresql-15-15.9/doc/src/sgml/html/infoschema-constraint-column-usage.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-constraint-column-usage.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-constraint-column-usage.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.18. constraint_column_usage
The view constraint_column_usage identifies all
columns in the current database that are used by some constraint.
Only those columns are shown that are contained in a table owned by
@@ -52,4 +52,4 @@
Name of the constraint
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-constraint-table-usage.html postgresql-15-15.9/doc/src/sgml/html/infoschema-constraint-table-usage.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-constraint-table-usage.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-constraint-table-usage.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.19. constraint_table_usage
The view constraint_table_usage identifies all
tables in the current database that are used by some constraint and
are owned by a currently enabled role. (This is different from the
@@ -47,4 +47,4 @@
Name of the constraint
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-data-type-privileges.html postgresql-15-15.9/doc/src/sgml/html/infoschema-data-type-privileges.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-data-type-privileges.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-data-type-privileges.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.20. data_type_privileges
The view data_type_privileges identifies all
data type descriptors that the current user has access to, by way
of being the owner of the described object or having some privilege
@@ -49,4 +49,4 @@
The identifier of the data type descriptor, which is unique
among the data type descriptors for that same object.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-datatypes.html postgresql-15-15.9/doc/src/sgml/html/infoschema-datatypes.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-datatypes.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-datatypes.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.2. Data Types
The columns of the information schema views use special data types
that are defined in the information schema. These are defined as
simple domains over ordinary built-in types. You should not use
@@ -30,4 +30,4 @@
Every column in the information schema has one of these five types.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-domain-constraints.html postgresql-15-15.9/doc/src/sgml/html/infoschema-domain-constraints.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-domain-constraints.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-domain-constraints.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.21. domain_constraints
The view domain_constraints contains all constraints
belonging to domains defined in the current database. Only those domains
are shown that the current user has access to (by way of being the owner or
@@ -49,4 +49,4 @@
YES if the constraint is deferrable and initially deferred, NO if not
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-domain-udt-usage.html postgresql-15-15.9/doc/src/sgml/html/infoschema-domain-udt-usage.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-domain-udt-usage.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-domain-udt-usage.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.22. domain_udt_usage
The view domain_udt_usage identifies all domains
that are based on data types owned by a currently enabled role.
Note that in PostgreSQL, built-in data
@@ -40,4 +40,4 @@
Name of the domain
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-domains.html postgresql-15-15.9/doc/src/sgml/html/infoschema-domains.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-domains.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-domains.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.23. domains
The view domains contains all
domains defined in the
current database. Only those domains are shown that the current user has
@@ -194,4 +194,4 @@
instances of such identifiers. (The specific format of the
identifier is not defined and not guaranteed to remain the same
in future versions.)
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-element-types.html postgresql-15-15.9/doc/src/sgml/html/infoschema-element-types.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-element-types.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-element-types.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.24. element_types
The view element_types contains the data type
descriptors of the elements of arrays. When a table column, composite-type attribute,
domain, function parameter, or function return value is defined to
@@ -191,4 +191,4 @@
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-15-15.8/doc/src/sgml/html/infoschema-enabled-roles.html postgresql-15-15.9/doc/src/sgml/html/infoschema-enabled-roles.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-enabled-roles.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-enabled-roles.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.25. enabled_roles
The view enabled_roles identifies the currently
“enabled roles”. The enabled roles are recursively
defined as the current user together with all roles that have been
@@ -25,4 +25,4 @@
Name of a role
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-foreign-data-wrapper-options.html postgresql-15-15.9/doc/src/sgml/html/infoschema-foreign-data-wrapper-options.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-foreign-data-wrapper-options.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-foreign-data-wrapper-options.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.26. foreign_data_wrapper_options
The view foreign_data_wrapper_options contains
all the options defined for foreign-data wrappers in the current
database. Only those foreign-data wrappers are shown that the
@@ -30,4 +30,4 @@
Value of the option
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-foreign-data-wrappers.html postgresql-15-15.9/doc/src/sgml/html/infoschema-foreign-data-wrappers.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-foreign-data-wrappers.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-foreign-data-wrappers.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.27. foreign_data_wrappers
The view foreign_data_wrappers contains all
foreign-data wrappers defined in the current database. Only those
foreign-data wrappers are shown that the current user has access to
@@ -35,4 +35,4 @@
Language used to implement this foreign-data wrapper
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-foreign-server-options.html postgresql-15-15.9/doc/src/sgml/html/infoschema-foreign-server-options.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-foreign-server-options.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-foreign-server-options.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.28. foreign_server_options
The view foreign_server_options contains all the
options defined for foreign servers in the current database. Only
those foreign servers are shown that the current user has access to
@@ -29,4 +29,4 @@
Value of the option
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-foreign-servers.html postgresql-15-15.9/doc/src/sgml/html/infoschema-foreign-servers.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-foreign-servers.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-foreign-servers.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.29. foreign_servers
The view foreign_servers contains all foreign
servers defined in the current database. Only those foreign
servers are shown that the current user has access to (by way of
@@ -45,4 +45,4 @@
Name of the owner of the foreign server
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-foreign-table-options.html postgresql-15-15.9/doc/src/sgml/html/infoschema-foreign-table-options.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-foreign-table-options.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-foreign-table-options.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.30. foreign_table_options
The view foreign_table_options contains all the
options defined for foreign tables in the current database. Only
those foreign tables are shown that the current user has access to
@@ -34,4 +34,4 @@
Value of the option
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-foreign-tables.html postgresql-15-15.9/doc/src/sgml/html/infoschema-foreign-tables.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-foreign-tables.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-foreign-tables.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.31. foreign_tables
The view foreign_tables contains all foreign
tables defined in the current database. Only those foreign
tables are shown that the current user has access to (by way of
@@ -34,4 +34,4 @@
Name of the foreign server
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-information-schema-catalog-name.html postgresql-15-15.9/doc/src/sgml/html/infoschema-information-schema-catalog-name.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-information-schema-catalog-name.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-information-schema-catalog-name.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.3. information_schema_catalog_name
information_schema_catalog_name is a table that
always contains one row and one column containing the name of the
current database (current catalog, in SQL terminology).
@@ -13,4 +13,4 @@
Name of the database that contains this information schema
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-key-column-usage.html postgresql-15-15.9/doc/src/sgml/html/infoschema-key-column-usage.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-key-column-usage.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-key-column-usage.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.32. key_column_usage
The view key_column_usage identifies all columns
in the current database that are restricted by some unique, primary
key, or foreign key constraint. Check constraints are not included
@@ -62,4 +62,4 @@
For a foreign-key constraint, ordinal position of the referenced
column within its unique constraint (count starts at 1);
otherwise null
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-parameters.html postgresql-15-15.9/doc/src/sgml/html/infoschema-parameters.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-parameters.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-parameters.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.33. parameters
The view parameters contains information about
the parameters (arguments) of all functions in the current database.
Only those functions are shown that the current user has access to
@@ -185,4 +185,4 @@
The default expression of the parameter, or null if none or if the
function is not owned by a currently enabled role.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-referential-constraints.html postgresql-15-15.9/doc/src/sgml/html/infoschema-referential-constraints.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-referential-constraints.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-referential-constraints.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.34. referential_constraints
The view referential_constraints contains all
referential (foreign key) constraints in the current database.
Only those constraints are shown for which the current user has
@@ -67,4 +67,4 @@
CASCADE, SET NULL,
SET DEFAULT, RESTRICT, or
NO ACTION.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-role-column-grants.html postgresql-15-15.9/doc/src/sgml/html/infoschema-role-column-grants.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-role-column-grants.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-role-column-grants.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.35. role_column_grants
The view role_column_grants identifies all
privileges granted on columns where the grantor or grantee is a
currently enabled role. Further information can be found under
@@ -55,4 +55,4 @@
YES if the privilege is grantable, NO if not
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-role-routine-grants.html postgresql-15-15.9/doc/src/sgml/html/infoschema-role-routine-grants.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-role-routine-grants.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-role-routine-grants.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.36. role_routine_grants
The view role_routine_grants identifies all
privileges granted on functions where the grantor or grantee is a
currently enabled role. Further information can be found under
@@ -63,4 +63,4 @@
YES if the privilege is grantable, NO if not
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-role-table-grants.html postgresql-15-15.9/doc/src/sgml/html/infoschema-role-table-grants.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-role-table-grants.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-role-table-grants.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.37. role_table_grants
The view role_table_grants identifies all
privileges granted on tables or views where the grantor or grantee
is a currently enabled role. Further information can be found
@@ -61,4 +61,4 @@
in the SELECT privilege, so this column
shows YES if the privilege
is SELECT, else NO.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-role-udt-grants.html postgresql-15-15.9/doc/src/sgml/html/infoschema-role-udt-grants.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-role-udt-grants.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-role-udt-grants.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.38. role_udt_grants
The view role_udt_grants is intended to identify
USAGE privileges granted on user-defined types
where the grantor or grantee is a currently enabled role. Further
@@ -50,4 +50,4 @@
YES if the privilege is grantable, NO if not
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-role-usage-grants.html postgresql-15-15.9/doc/src/sgml/html/infoschema-role-usage-grants.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-role-usage-grants.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-role-usage-grants.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.39. role_usage_grants
The view role_usage_grants identifies
USAGE privileges granted on various kinds of
objects where the grantor or grantee is a currently enabled role.
@@ -54,4 +54,4 @@
YES if the privilege is grantable, NO if not
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-routine-column-usage.html postgresql-15-15.9/doc/src/sgml/html/infoschema-routine-column-usage.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-routine-column-usage.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-routine-column-usage.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.40. routine_column_usage
The view routine_column_usage identifies all columns
that are used by a function or procedure, either in the SQL body or in
parameter default expressions. (This only works for unquoted SQL bodies,
@@ -61,4 +61,4 @@
Name of the column that is used by the function
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-routine-privileges.html postgresql-15-15.9/doc/src/sgml/html/infoschema-routine-privileges.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-routine-privileges.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-routine-privileges.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.41. routine_privileges
The view routine_privileges identifies all
privileges granted on functions to a currently enabled role or by a
currently enabled role. There is one row for each combination of function,
@@ -59,4 +59,4 @@
YES if the privilege is grantable, NO if not
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-routine-routine-usage.html postgresql-15-15.9/doc/src/sgml/html/infoschema-routine-routine-usage.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-routine-routine-usage.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-routine-routine-usage.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.42. routine_routine_usage
The view routine_routine_usage identifies all functions
or procedures that are used by another (or the same) function or procedure,
either in the SQL body or in parameter default expressions. (This only
@@ -52,4 +52,4 @@
The “specific name” of the function that is used by the
first function.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-routine-sequence-usage.html postgresql-15-15.9/doc/src/sgml/html/infoschema-routine-sequence-usage.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-routine-sequence-usage.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-routine-sequence-usage.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.43. routine_sequence_usage
The view routine_sequence_usage identifies all sequences
that are used by a function or procedure, either in the SQL body or in
parameter default expressions. (This only works for unquoted SQL bodies,
@@ -56,4 +56,4 @@
Name of the sequence that is used by the function
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-routine-table-usage.html postgresql-15-15.9/doc/src/sgml/html/infoschema-routine-table-usage.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-routine-table-usage.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-routine-table-usage.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.44. routine_table_usage
The view routine_table_usage is meant to identify all
tables that are used by a function or procedure. This information is
currently not tracked by PostgreSQL.
@@ -54,4 +54,4 @@
Name of the table that is used by the function
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-routines.html postgresql-15-15.9/doc/src/sgml/html/infoschema-routines.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-routines.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-routines.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.45. routines
The view routines contains all functions and procedures in the
current database. Only those functions and procedures are shown that the current
user has access to (by way of being the owner or having some
@@ -461,4 +461,4 @@
Applies to a feature not available in PostgreSQL
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-schema.html postgresql-15-15.9/doc/src/sgml/html/infoschema-schema.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-schema.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-schema.html 2024-11-11 23:01:06.000000000 +0000
@@ -1,5 +1,5 @@
-37.1. The Schema
The information schema itself is a schema named
information_schema. This schema automatically
exists in all databases. The owner of this schema is the initial
@@ -13,4 +13,4 @@
schema are generic names that might occur in user applications, you
should be careful if you want to put the information schema in the
path.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-schemata.html postgresql-15-15.9/doc/src/sgml/html/infoschema-schemata.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-schemata.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-schemata.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-37.46. schemata
The view schemata contains all schemas in the current
database that the current user has access to (by way of being the owner or
having some privilege).
@@ -43,4 +43,4 @@
Applies to a feature not available in PostgreSQL
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-sequences.html postgresql-15-15.9/doc/src/sgml/html/infoschema-sequences.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-sequences.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-sequences.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-37.47. sequences
The view sequences contains all sequences
defined in the current database. Only those sequences are shown
that the current user has access to (by way of being the owner or
@@ -84,4 +84,4 @@
Note that in accordance with the SQL standard, the start, minimum,
maximum, and increment values are returned as character strings.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-sql-features.html postgresql-15-15.9/doc/src/sgml/html/infoschema-sql-features.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-sql-features.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-sql-features.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-37.48. sql_features
The table sql_features contains information
about which formal features defined in the SQL standard are
supported by PostgreSQL. This is the
@@ -47,4 +47,4 @@
Possibly a comment about the supported status of the feature
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-sql-implementation-info.html postgresql-15-15.9/doc/src/sgml/html/infoschema-sql-implementation-info.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-sql-implementation-info.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-sql-implementation-info.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-37.49. sql_implementation_info
The table sql_implementation_info contains
information about various aspects that are left
implementation-defined by the SQL standard. This information is
@@ -42,4 +42,4 @@
Possibly a comment pertaining to the implementation information item
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-sql-parts.html postgresql-15-15.9/doc/src/sgml/html/infoschema-sql-parts.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-sql-parts.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-sql-parts.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-37.50. sql_parts
The table sql_parts contains information about
which of the several parts of the SQL standard are supported by
PostgreSQL.
@@ -36,4 +36,4 @@
Possibly a comment about the supported status of the part
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-sql-sizing.html postgresql-15-15.9/doc/src/sgml/html/infoschema-sql-sizing.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-sql-sizing.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-sql-sizing.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-37.51. sql_sizing
The table sql_sizing contains information about
various size limits and maximum values in
PostgreSQL. This information is
@@ -35,4 +35,4 @@
Possibly a comment pertaining to the sizing item
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-table-constraints.html postgresql-15-15.9/doc/src/sgml/html/infoschema-table-constraints.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-table-constraints.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-table-constraints.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-37.52. table_constraints
The view table_constraints contains all
constraints belonging to tables that the current user owns or has
some privilege other than SELECT on.
@@ -70,4 +70,4 @@
if the constraint treats nulls as distinct or NO if
it treats nulls as not distinct, otherwise null for other types of
constraints.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-table-privileges.html postgresql-15-15.9/doc/src/sgml/html/infoschema-table-privileges.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-table-privileges.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-table-privileges.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-37.53. table_privileges
The view table_privileges identifies all
privileges granted on tables or views to a currently enabled role
or by a currently enabled role. There is one row for each
@@ -57,4 +57,4 @@
in the SELECT privilege, so this column
shows YES if the privilege
is SELECT, else NO.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-tables.html postgresql-15-15.9/doc/src/sgml/html/infoschema-tables.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-tables.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-tables.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-37.54. tables
The view tables contains all tables and views
defined in the current database. Only those tables and views are
shown that the current user has access to (by way of being the
@@ -79,4 +79,4 @@
Not yet implemented
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-transforms.html postgresql-15-15.9/doc/src/sgml/html/infoschema-transforms.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-transforms.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-transforms.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-37.55. transforms
The view transforms contains information about the
transforms defined in the current database. More precisely, it contains a
row for each function contained in a transform (the “from SQL”
@@ -52,4 +52,4 @@
FROM SQL or TO SQL
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-triggered-update-columns.html postgresql-15-15.9/doc/src/sgml/html/infoschema-triggered-update-columns.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-triggered-update-columns.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-triggered-update-columns.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-37.56. triggered_update_columns
For triggers in the current database that specify a column list
(like UPDATE OF column1, column2), the
view triggered_update_columns identifies these
@@ -48,4 +48,4 @@
Name of the column that the trigger is defined on
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-triggers.html postgresql-15-15.9/doc/src/sgml/html/infoschema-triggers.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-triggers.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-triggers.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-37.57. triggers
The view triggers contains all triggers defined
in the current database on tables and views that the current user owns
or has some privilege other than SELECT on.
@@ -147,4 +147,4 @@
respectively.
That was how they were named in the SQL:1999 standard.
The new naming conforms to SQL:2003 and later.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-udt-privileges.html postgresql-15-15.9/doc/src/sgml/html/infoschema-udt-privileges.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-udt-privileges.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-udt-privileges.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-37.58. udt_privileges
The view udt_privileges identifies
USAGE privileges granted on user-defined types to a
currently enabled role or by a currently enabled role. There is one row for
@@ -47,4 +47,4 @@
YES if the privilege is grantable, NO if not
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-usage-privileges.html postgresql-15-15.9/doc/src/sgml/html/infoschema-usage-privileges.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-usage-privileges.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-usage-privileges.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-37.59. usage_privileges
The view usage_privileges identifies
USAGE privileges granted on various kinds of
objects to a currently enabled role or by a currently enabled role.
@@ -63,4 +63,4 @@
YES if the privilege is grantable, NO if not
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-user-defined-types.html postgresql-15-15.9/doc/src/sgml/html/infoschema-user-defined-types.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-user-defined-types.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-user-defined-types.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-37.60. user_defined_types
The view user_defined_types currently contains
all composite types defined in the current database.
Only those types are shown that the current user has access to (by way
@@ -165,4 +165,4 @@
Applies to a feature not available in PostgreSQL
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-user-mapping-options.html postgresql-15-15.9/doc/src/sgml/html/infoschema-user-mapping-options.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-user-mapping-options.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-user-mapping-options.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-37.61. user_mapping_options
The view user_mapping_options contains all the
options defined for user mappings in the current database. Only
those user mappings are shown where the current user has access to
@@ -42,4 +42,4 @@
server owner, or the current user is a superuser. The intent is
to protect password information stored as user mapping
option.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-user-mappings.html postgresql-15-15.9/doc/src/sgml/html/infoschema-user-mappings.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-user-mappings.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-user-mappings.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-37.62. user_mappings
The view user_mappings contains all user
mappings defined in the current database. Only those user mappings
are shown where the current user has access to the corresponding
@@ -27,4 +27,4 @@
Name of the foreign server used by this mapping
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-view-column-usage.html postgresql-15-15.9/doc/src/sgml/html/infoschema-view-column-usage.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-view-column-usage.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-view-column-usage.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-37.63. view_column_usage
The view view_column_usage identifies all
columns that are used in the query expression of a view (the
SELECT statement that defines the view). A
@@ -51,4 +51,4 @@
Name of the column that is used by the view
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-view-routine-usage.html postgresql-15-15.9/doc/src/sgml/html/infoschema-view-routine-usage.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-view-routine-usage.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-view-routine-usage.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-37.64. view_routine_usage
The view view_routine_usage identifies all
routines (functions and procedures) that are used in the query
expression of a view (the SELECT statement that
@@ -40,4 +40,4 @@
The “specific name” of the function. See Section 37.45 for more information.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-view-table-usage.html postgresql-15-15.9/doc/src/sgml/html/infoschema-view-table-usage.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-view-table-usage.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-view-table-usage.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-37.65. view_table_usage
The view view_table_usage identifies all tables
that are used in the query expression of a view (the
SELECT statement that defines the view). A
@@ -44,4 +44,4 @@
Name of the table that is used by the view
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/infoschema-views.html postgresql-15-15.9/doc/src/sgml/html/infoschema-views.html
--- postgresql-15-15.8/doc/src/sgml/html/infoschema-views.html 2024-08-05 20:21:55.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/infoschema-views.html 2024-11-11 23:01:07.000000000 +0000
@@ -1,5 +1,5 @@
-37.66. views
The view views contains all views defined in the
current database. Only those views are shown that the current user
has access to (by way of being the owner or having some privilege).
@@ -67,4 +67,4 @@
YES if the view has an INSTEAD OFINSERT trigger defined on it, NO if not
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/install-binaries.html postgresql-15-15.9/doc/src/sgml/html/install-binaries.html
--- postgresql-15-15.8/doc/src/sgml/html/install-binaries.html 2024-08-05 20:21:50.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/install-binaries.html 2024-11-11 23:01:02.000000000 +0000
@@ -1,5 +1,5 @@
-Chapter 16. Installation from Binaries
PostgreSQL is available in the form of binary
packages for most common operating systems today. When available, this is
the recommended way to install PostgreSQL for users of the system. Building
@@ -10,4 +10,4 @@
the download section on the PostgreSQL website at
https://www.postgresql.org/download/ and follow the
instructions for the specific platform.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/install-getsource.html postgresql-15-15.9/doc/src/sgml/html/install-getsource.html
--- postgresql-15-15.8/doc/src/sgml/html/install-getsource.html 2024-08-05 20:21:50.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/install-getsource.html 2024-11-11 23:01:02.000000000 +0000
@@ -1,5 +1,5 @@
-17.3. Getting the Source
The PostgreSQL source code for released versions
can be obtained from the download section of our website:
https://www.postgresql.org/ftp/source/.
@@ -17,4 +17,4 @@
Alternatively, you can use the Git version control system; see
Section I.1 for more information.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/install-post.html postgresql-15-15.9/doc/src/sgml/html/install-post.html
--- postgresql-15-15.8/doc/src/sgml/html/install-post.html 2024-08-05 20:21:50.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/install-post.html 2024-11-11 23:01:02.000000000 +0000
@@ -1,5 +1,5 @@
-17.5. Post-Installation Setup
On some systems with shared libraries
you need to tell the system how to find the newly installed
shared libraries. The systems on which this is
@@ -100,4 +100,4 @@
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-15-15.8/doc/src/sgml/html/install-procedure.html postgresql-15-15.9/doc/src/sgml/html/install-procedure.html
--- postgresql-15-15.8/doc/src/sgml/html/install-procedure.html 2024-08-05 20:21:50.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/install-procedure.html 2024-11-11 23:01:02.000000000 +0000
@@ -1,5 +1,5 @@
-17.4. Installation Procedure
The first step of the installation procedure is to configure the
source tree for your system and choose the options you would like.
This is done by running the configure script. For a
@@ -815,4 +815,4 @@
makefiles. Which to use is a matter of preference, but a common habit
among developers is to use PROFILE for one-time flag
adjustments, while COPT might be kept set all the time.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/install-requirements.html postgresql-15-15.9/doc/src/sgml/html/install-requirements.html
--- postgresql-15-15.8/doc/src/sgml/html/install-requirements.html 2024-08-05 20:21:50.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/install-requirements.html 2024-11-11 23:01:02.000000000 +0000
@@ -1,5 +1,5 @@
-17.2. Requirements
In general, a modern Unix-compatible platform should be able to run
PostgreSQL.
The platforms that had received specific testing at the
@@ -194,4 +194,4 @@
run the regression tests you will temporarily need up to an extra
300 MB. Use the df command to check free disk
space.
-
\ No newline at end of file
+
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/install-short.html postgresql-15-15.9/doc/src/sgml/html/install-short.html
--- postgresql-15-15.8/doc/src/sgml/html/install-short.html 2024-08-05 20:21:50.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/install-short.html 2024-11-11 23:01:02.000000000 +0000
@@ -1,5 +1,5 @@
-17.1. Short Version
\ No newline at end of file
diff -Nru postgresql-15-15.8/doc/src/sgml/html/install-windows-full.html postgresql-15-15.9/doc/src/sgml/html/install-windows-full.html
--- postgresql-15-15.8/doc/src/sgml/html/install-windows-full.html 2024-08-05 20:21:50.000000000 +0000
+++ postgresql-15-15.9/doc/src/sgml/html/install-windows-full.html 2024-11-11 23:01:02.000000000 +0000
@@ -1,6 +1,6 @@
18.1. Building with Visual C++ or the Microsoft Windows SDK
18.1. Building with Visual C++ or the
- Microsoft Windows SDK
PostgreSQL can be built using the Visual C++ compiler suite from Microsoft.
These compilers can be either from Visual Studio,
@@ -96,13 +96,11 @@
you don't need Visual Studio to build.
Note that as of Version 8.0a the Windows SDK no longer ships with a
complete command-line build environment.
-
ActiveState Perl
- ActiveState Perl is required to run the build generation scripts. MinGW
+
Strawberry Perl
+ Strawberry Perl is required to run the build generation scripts. MinGW
or Cygwin Perl will not work. It must also be present in the PATH.
Binaries can be downloaded from
- https://www.activestate.com
- (Note: version 5.8.3 or later is required,
- the free Standard Distribution is sufficient).
+ https://strawberryperl.com.
The following additional products are not required to get started,
@@ -110,9 +108,10 @@
config.pl file to specify which directories the libraries
are available in.
-
ActiveState TCL
- Required for building PL/Tcl (Note: version
- 8.4 is required, the free Standard Distribution is sufficient).
+