ALTER DATABASE — change a database
ALTER DATABASEname[ [ WITH ]option[ ... ] ] whereoptioncan be: CONNECTION LIMITconnlimitALTER DATABASEnameSETparameter{ TO | = } {value| DEFAULT } ALTER DATABASEnameRESETparameterALTER DATABASEnameRENAME TOnewnameALTER DATABASEnameOWNER TOnew_owner
ALTER DATABASE changes the attributes
of a database.
The first form changes certain per-database settings. (See below for details.) Only the database owner or a superuser can change these settings.
The second and third forms change the session default for a run-time
configuration variable for a PostgreSQL
database. Whenever a new session is subsequently started in that
database, the specified value becomes the session default value.
The database-specific default overrides whatever setting is present
in postgresql.conf or has been received from the
postmaster command line. Only the database
owner or a superuser can change the session defaults for a
database. Certain variables cannot be set this way, or can only be
set by a superuser.
The fourth form changes the name of the database. Only the database
owner or a superuser can rename a database; non-superuser owners must
also have the
CREATEDB privilege. The current database cannot
be renamed. (Connect to a different database if you need to do
that.)
The fifth form changes the owner of the database. Only a superuser can change the database's owner.
nameThe name of the database whose attributes are to be altered.
connlimitHow many concurrent connections can be made to this database. -1 means no limit.
parametervalue
Set this database's session default for the specified configuration
parameter to the given value. If
value is DEFAULT
or, equivalently, RESET is used, the
database-specific setting is removed, so the system-wide default
setting will be inherited in new sessions. Use RESET
ALL to clear all database-specific settings.
See SET and Chapter 17, Run-time Configuration for more information about allowed parameter names and values.
newnameThe new name of the database.
new_ownerThe new owner of the database.
It is also possible to tie a session default to a specific user rather than to a database; see ALTER USER. User-specific settings override database-specific ones if there is a conflict.