Creates a new database.
CREATE DATABASE name [ [WITH] [OWNER [=] <user_name>]
[TEMPLATE [=] <template>]
[ENCODING [=] <encoding>]
[LC_COLLATE [=] <lc_collate>]
[LC_CTYPE [=] <lc_ctype>]
[TABLESPACE [=] <tablespace>]
[CONNECTION LIMIT [=] connlimit ] ]
CREATE DATABASE creates a new database. To create a database, you must be a superuser or have the special
The creator becomes the owner of the new database by default. Superusers can create databases owned by other users by using the
OWNER clause. They can even create databases owned by users with no special privileges. Non-superusers with
CREATEDB privilege can only create databases owned by themselves.
By default, the new database will be created by cloning the standard system database
template1. A different template can be specified by writing
TEMPLATE name. In particular, by writing
TEMPLATE template0, you can create a clean database containing only the standard objects predefined by Greenplum Database. This is useful if you wish to avoid copying any installation-local objects that may have been added to
DEFAULT to use the default owner (the user running the command).
DEFAULT to use the default template (template1).
'SQL_ASCII'), an integer encoding number, or
DEFAULT to use the default encoding. For more information, see
Character Set Support.
LC_COLLATE) to use in the new database. This affects the sort order applied to strings, e.g. in queries with
ORDER BY, as well as the order used in indexes on text columns. The default is to use the collation order of the template database. See the Notes section for additional restrictions.
LC_CTYPE) to use in the new database. This affects the categorization of characters, e.g. lower, upper and digit. The default is to use the character classification of the template database. See below for additional restrictions.
DEFAULT to use the template database's tablespace. This tablespace will be the default tablespace used for objects created in this database.
CREATE DATABASE cannot be run inside a transaction block.
When you copy a database by specifying its name as the template, no other sessions can be connected to the template database while it is being copied. New connections to the template database are locked out until
CREATE DATABASE completes.
CONNECTION LIMIT is not enforced against superusers.
The character set encoding specified for the new database must be compatible with the chosen locale settings (
LC_CTYPE). If the locale is
C (or equivalently
POSIX), then all encodings are allowed, but for other locale settings there is only one encoding that will work properly.
CREATE DATABASE will allow superusers to specify
SQL_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 when
template0 is used as template. This is because
CTYPE affect the ordering in indexes, so that any indexes copied from the template database would be invalid in the new database with different settings.
template0, however, is known to not contain any data or indexes that would be affected.
To create a new database:
CREATE DATABASE gpdb;
To create a database
sales owned by user
salesapp with a default tablespace of
CREATE DATABASE sales OWNER salesapp TABLESPACE salesspace;
To create a database
music which supports the ISO-8859-1 character set:
CREATE DATABASE music ENCODING 'LATIN1' TEMPLATE template0;
In this example, the
TEMPLATE template0 clause would only be required if
template1's encoding is not ISO-8859-1. Note that changing encoding might require selecting new
LC_CTYPE settings as well.
There is no
CREATE DATABASE statement in the SQL standard. Databases are equivalent to catalogs, whose creation is implementation-defined.
Parent topic: SQL Commands