pg_database
#
The catalog pg_database
stores information about
the available databases. Databases are created with the CREATE DATABASE
command.
Consult Chapter 22 for details about the meaning
of some of the parameters.
Unlike most system catalogs, pg_database
is shared across all databases of a cluster: there is only one
copy of pg_database
per cluster, not
one per database.
Table 53.16. pg_database
Columns
Column Type Description |
---|
Row identifier |
Database name |
Owner of the database, usually the user who created it |
Character encoding for this database
( |
Locale provider for this database: |
If true, then this database can be cloned by
any user with |
If false then no one can connect to this database. This is
used to protect the |
Indicates that there are login event triggers defined for this database.
This flag is used to avoid extra lookups on the
|
Sets maximum number of concurrent connections that can be made to this database. -1 means no limit, -2 indicates the database is invalid. |
All transaction IDs before this one have been replaced with a permanent
(“frozen”) transaction ID in this database. This is used to
track whether the database needs to be vacuumed in order to prevent
transaction ID wraparound or to allow |
All multixact IDs before this one have been replaced with a
transaction ID in this database. This is used to
track whether the database needs to be vacuumed in order to prevent
multixact ID wraparound or to allow |
The default tablespace for the database.
Within this database, all tables for which
|
LC_COLLATE for this database |
LC_CTYPE for this database |
Collation provider locale name for this database. If the
provider is |
ICU collation rules for this database |
Provider-specific version of the collation. This is recorded when the database is created and then checked when it is used, to detect changes in the collation definition that could lead to data corruption. |
Access privileges; see Section 5.8 for details |