alter_database(7) - BetterMan

—

SYNOPSIS

bash

ALTER DATABASE \nname\n [ [ WITH ] \noption\n [ ... ] ]
where \noption\n can be:
\n
    ALLOW_CONNECTIONS \nallowconn\n
\n
    CONNECTION LIMIT \nconnlimit\n
\n
    IS_TEMPLATE \nistemplate\n
ALTER DATABASE \nname\n RENAME TO \nnew_name\n
ALTER DATABASE \nname\n OWNER TO { \nnew_owner\n | CURRENT_ROLE | CURRENT_USER | SESSION_USER }
ALTER DATABASE \nname\n SET TABLESPACE \nnew_tablespace\n
ALTER DATABASE \nname\n REFRESH COLLATION VERSION
ALTER DATABASE \nname\n SET \nconfiguration_parameter\n { TO | = } { \nvalue\n | DEFAULT }
ALTER DATABASE \nname\n SET \nconfiguration_parameter\n FROM CURRENT
ALTER DATABASE \nname\n RESET \nconfiguration_parameter\n
ALTER DATABASE \nname\n RESET ALL

DESCRIPTION

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 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 third form changes the owner of the database. To alter the owner, you must be able to SET ROLE to the new owning role, and you must have the CREATEDB privilege. (Note that superusers have all these privileges automatically.)

The fourth form changes the default tablespace of the database. Only the database owner or a superuser can do this; you must also have create privilege for the new tablespace. This command physically moves any tables or indexes in the database's old default tablespace to the new tablespace. The new default tablespace must be empty for this database, and no one can be connected to the database. Tables and indexes in non-default tablespaces are unaffected.

The remaining 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 postgres 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.

PARAMETERS

name

allowconn

connlimit

istemplate

new_name

new_owner

new_tablespace

This form of the command cannot be executed inside a transaction block.

REFRESH COLLATION VERSION

configuration_parameter value

See SET(7) and Chapter 19 for more information about allowed parameter names and values.

NOTES

It is also possible to tie a session default to a specific role rather than to a database; see ALTER ROLE (ALTER_ROLE(7)). Role-specific settings override database-specific ones if there is a conflict.

EXAMPLES

To disable index scans by default in the database test:

bash

ALTER DATABASE test SET enable_indexscan TO off;

COMPATIBILITY

The ALTER DATABASE statement is a PostgreSQL extension.