Text Size: Normal / Large

42.15. pg_database

The catalog pg_database stores information about the available databases. Databases are created with the CREATE DATABASE command. Consult Chapter 19 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 42-15. pg_database Columns

NameTypeReferencesDescription
datnamename Database name
datdbaoidpg_authid.oidOwner of the database, usually the user who created it
encodingint4 Character encoding for this database
datistemplatebool  If true then this database can be used in the TEMPLATE clause of CREATE DATABASE to create a new database as a clone of this one.
datallowconnbool  If false then no one can connect to this database. This is used to protect the template0 database from being altered.
datconnlimitint4  Sets maximum number of concurrent connections that can be made to this database. -1 means no limit.
datlastsysoidoid  Last system OID in the database; useful particularly to pg_dump
datvacuumxidxid  All rows inserted or deleted by transaction IDs before this one have been marked as known committed or known aborted in this database. This is used to determine when commit-log space can be recycled.
datfrozenxidxid  All rows inserted by transaction IDs before this one have been relabeled with a permanent ("frozen") transaction ID in this database. This is useful to check whether a database must be vacuumed soon to avoid transaction ID wrap-around problems.
dattablespaceoidpg_tablespace.oid The default tablespace for the database. Within this database, all tables for which pg_class.reltablespace is zero will be stored in this tablespace; in particular, all the non-shared system catalogs will be there.
datconfigtext[] Session defaults for run-time configuration variables
dataclaclitem[]  Access privileges; see GRANT and REVOKE for details.

User Comments

No comments could be found for this page.

Add Comment

Please use this form to add your own comments regarding your experience with particular features of PostgreSQL, clarifications of the documentation, or hints for other users. Please note, this is not a support forum, and your IP address will be logged. If you have a question or need help, please see the faq, try a mailing list, or join us on IRC. Note that submissions containing URLs or other keywords commonly found in 'spam' comments may be silently discarded. Please contact the webmaster if you think this is happening to you in error.

In order to submit a comment, you must have a community account.

* Comment
 

* denotes required field

Privacy Policy | Project hosted by hub.org | Designed by tinysofa
Copyright © 1996 – 2007 PostgreSQL Global Development Group