Movatterモバイル変換

CREATE DATABASE

CREATE DATABASE — create a new database

Synopsis

CREATE DATABASEname    [ WITH ] [ OWNER [=]user_name ]           [ TEMPLATE [=]template ]           [ ENCODING [=]encoding ]           [ STRATEGY [=]strategy ]           [ LOCALE [=]locale ]           [ LC_COLLATE [=]lc_collate ]           [ LC_CTYPE [=]lc_ctype ]           [ BUILTIN_LOCALE [=]builtin_locale ]           [ ICU_LOCALE [=]icu_locale ]           [ ICU_RULES [=]icu_rules ]           [ LOCALE_PROVIDER [=]locale_provider ]           [ COLLATION_VERSION =collation_version ]           [ TABLESPACE [=]tablespace_name ]           [ ALLOW_CONNECTIONS [=]allowconn ]           [ CONNECTION LIMIT [=]connlimit ]           [ IS_TEMPLATE [=]istemplate ]           [ OID [=]oid ]

Description

CREATE DATABASE creates a newPostgreSQL database.

To create a database, you must be a superuser or have the specialCREATEDB privilege. SeeCREATE ROLE.

By default, the new database will be created by cloning the standard system databasetemplate1. A different template can be specified by writingTEMPLATEname. In particular, by writingTEMPLATE template0, you can create a pristine database (one where no user-defined objects exist and where the system objects have not been altered) containing only the standard objects predefined by your version ofPostgreSQL. This is useful if you wish to avoid copying any installation-local objects that might have been added totemplate1.

Parameters

Optional parameters can be written in any order, not only the order illustrated above.

Notes

CREATE DATABASE cannot be executed inside a transaction block.

Errors along the line of“could not initialize database directory” are most likely related to insufficient permissions on the data directory, a full disk, or other file system problems.

UseDROP DATABASE to remove a database.

The programcreatedb is a wrapper program around this command, provided for convenience.

Database-level configuration parameters (set viaALTER DATABASE) and database-level permissions (set viaGRANT) are not copied from the template database.

Although it is possible to copy a database other thantemplate1 by specifying its name as the template, this is not (yet) intended as a general-purpose“COPY DATABASE” facility. The principal limitation is that no other sessions can be connected to the template database while it is being copied.CREATE DATABASE will fail if any other connection exists when it starts; otherwise, new connections to the template database are locked out untilCREATE DATABASE completes. SeeSection 22.3 for more information.

The character set encoding specified for the new database must be compatible with the chosen locale settings (LC_COLLATE andLC_CTYPE). If the locale isC (or equivalentlyPOSIX), then all encodings are allowed, but for other locale settings there is only one encoding that will work properly. (On Windows, however, UTF-8 encoding can be used with any locale.)CREATE DATABASE will allow superusers to specifySQL_ASCII encoding regardless of the locale settings, but this choice is deprecated and may result in misbehavior of character-string functions if data that is not encoding-compatible with the locale is stored in the database.

The encoding and locale settings must match those of the template database, except whentemplate0 is used as template. This is because other databases might contain data that does not match the specified encoding, or might contain indexes whose sort ordering is affected byLC_COLLATE andLC_CTYPE. Copying such data would result in a database that is corrupt according to the new settings.template0, however, is known to not contain any data or indexes that would be affected.

There is currently no option to use a database locale with nondeterministic comparisons (seeCREATE COLLATION for an explanation). If this is needed, then per-column collations would need to be used.

TheCONNECTION LIMIT option is only enforced approximately; if two new sessions start at about the same time when just one connection“slot” remains for the database, it is possible that both will fail. Also, the limit is not enforced against superusers or background worker processes.

Examples

To create a new database:

CREATE DATABASE lusiadas;

To create a databasesales owned by usersalesapp with a default tablespace ofsalesspace:

CREATE DATABASE sales OWNER salesapp TABLESPACE salesspace;

To create a databasemusic with a different locale:

CREATE DATABASE music    LOCALE 'sv_SE.utf8'    TEMPLATE template0;

In this example, theTEMPLATE template0 clause is required if the specified locale is different from the one intemplate1. (If it is not, then specifying the locale explicitly is redundant.)

To create a databasemusic2 with a different locale and a different character set encoding:

CREATE DATABASE music2    LOCALE 'sv_SE.iso885915'    ENCODING LATIN9    TEMPLATE template0;

The specified locale and encoding settings must match, or an error will be reported.

Note that locale names are specific to the operating system, so that the above commands might not work in the same way everywhere.

Compatibility

There is noCREATE DATABASE statement in the SQL standard. Databases are equivalent to catalogs, whose creation is implementation-defined.

See Also