<!--

$PostgreSQL: pgsql/doc/src/sgml/ref/alter_database.sgml,v 1.13 2004/07/05 02:34:43 momjian Exp $

$PostgreSQL: pgsql/doc/src/sgml/ref/alter_database.sgml,v 1.14 2005/01/04 00:39:53 tgl Exp $

PostgreSQL documentation

-->

ALTER DATABASE <replaceable class="PARAMETER">name</replaceable> RENAME TO <replaceable>newname</replaceable>

ALTER DATABASE <replaceable class="PARAMETER">name</replaceable> OWNER TO <replaceable>new_owner</replaceable>

ALTER DATABASE <replaceable class="PARAMETER">name</replaceable> OWNER TO <replaceable>newowner</replaceable>

</synopsis>

</refsynopsisdiv>

<refsect1>

<title>Description</title>

<para>

<command>ALTER DATABASE</command>is used to change the attributes

<command>ALTER DATABASE</command>changes the attributes

of a database.

</para>

<para>

The first two forms change the session defaultof a run-time

The first two forms change the session defaultfor a run-time

configuration variable for a <productname>PostgreSQL</productname>

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 <filename>postgresql.conf</> or has been received from the

<command>postmaster</command> command line. Only the database

owner or a superuser can change the session defaults for a

database.

database. Certain variables cannot be set this way, or can only be

set by a superuser.

</para>

<para>

The third form changes the name of the database. Only the database

owner can rename a database, and only if he has the

owner or a superuser can rename a database; non-superuser owners must

also have the

<literal>CREATEDB</literal> privilege. The current database cannot

be renamed. (Connect to a different database if you need to do

that.)

<term><replaceable class="PARAMETER">name</replaceable></term>

<listitem>

<para>

The name of the database whosesession defaults are to be altered.

The name of the database whoseattributes are to be altered.

</para>

</listitem>

</varlistentry>

<term><replaceable>value</replaceable></term>

<listitem>

<para>

Setthesession default forthis database ofthe specified

configurationparameter to the given value. If

Setthis database'ssession default for the specified configuration

parameter to the given value. If

<replaceable>value</replaceable> is <literal>DEFAULT</literal>

or, equivalently, <literal>RESET</literal> is used, the

database-specific variable setting is removed and the system-wide

default

database-specific setting is removed, so the system-wide default

setting will be inherited in new sessions. Use <literal>RESET

ALL</literal> to clear all settings.

ALL</literal> to clear alldatabase-specificsettings.

</para>

<para>

</para>

</listitem>

</varlistentry>

<varlistentry>

<term><replaceable class="parameter">newowner</replaceable></term>

<listitem>

<para>

The new owner of the database.

</para>

</listitem>

</varlistentry>

</variablelist>

</refsect1>

<refsect1>

<title>Notes</title>

<para>

Using <xref linkend="sql-alteruser" endterm="sql-alteruser-title">,

it is also possible to tie a session default to a specific user

rather than a database. User-specific settings override database-specific

It is also possible to tie a session default to a specific user

rather than to a database; see

<xref linkend="sql-alteruser" endterm="sql-alteruser-title">.

User-specific settings override database-specific

ones if there is a conflict.

</para>

</refsect1>

<title>See Also</title>

<simplelist type="inline">

<member><xref linkend="sql-alteruser" endterm="sql-alteruser-title"></member>

<member><xref linkend="sql-createdatabase" endterm="sql-createdatabase-title"></member>

<member><xref linkend="sql-dropdatabase" endterm="sql-dropdatabase-title"></member>

<member><xref linkend="sql-set" endterm="sql-set-title"></member>

<!--

$PostgreSQL: pgsql/doc/src/sgml/ref/alter_group.sgml,v 1.14 2003/11/29 19:51:38 pgsql Exp $

$PostgreSQL: pgsql/doc/src/sgml/ref/alter_group.sgml,v 1.15 2005/01/04 00:39:53 tgl Exp $

PostgreSQL documentation

-->

<title>Description</title>

<para>

<command>ALTER GROUP</command> is used to change a user group. The

first two variants add or remove users from a group. Only database

superusers can use this command. Adding a user to a group does not

create the user. Similarly, removing a user from a group does not

drop the user itself.

<command>ALTER GROUP</command> changes the attributes of a user group.

</para>

<para>

The first two variants add users to a group or remove them from a group.

Only database superusers can use this command.

</para>

<para>

<term><replaceable class="PARAMETER">username</replaceable></term>

<listitem>

<para>

Users which are to be added or removed from the group. The users

must exist.

Users that are to be added to or removed from the group. The users

must already exist; <command>ALTER GROUP</> does not create or

drop users.

</para>

</listitem>

</varlistentry>

<!--

$PostgreSQL: pgsql/doc/src/sgml/ref/alter_table.sgml,v 1.74 2004/10/22 17:20:04 tgl Exp $

$PostgreSQL: pgsql/doc/src/sgml/ref/alter_table.sgml,v 1.75 2005/01/04 00:39:53 tgl Exp $

PostgreSQL documentation

-->

<xref linkend="sql-analyze" endterm="sql-analyze-title"> operations.

The target can be set in the range 0 to 1000; alternatively, set it

to -1 to revert to using the system default statistics

target. For more information on the use of statistics by the

target (<xref linkend="guc-default-statistics-target">).

For more information on the use of statistics by the

<productname>PostgreSQL</productname> query planner, refer to

<xref linkend="planner-stats">.

</para>

compressible data. <literal>EXTERNAL</literal> is for external,

uncompressed data, and <literal>EXTENDED</literal> is for external,

compressed data. <literal>EXTENDED</literal> is the default for all

data types that support it.The useof <literal>EXTERNAL</literal> will, for example,

make substring operations ona<type>text</type>column faster, at the penalty of

increased storage space.

data types that support it.Useof <literal>EXTERNAL</literal> will

make substring operations on <type>text</type>and <type>bytea</type>

columns faster, at the penalty ofincreased storage space.

</para>

</listitem>

</varlistentry>

<term><replaceable class="PARAMETER">name</replaceable></term>

<listitem>

<para>

The name (possibly schema-qualified) of an existing table to

alter. If <literal>ONLY</> is specified, only that table is

altered. If <literal>ONLY</> is not specified, the table and all

its descendant tables (if any) are updated. <literal>*</> can be

appended to the table name to indicate that descendant tables are

to be altered, but in the current version, this is the default

behavior. (In releases before 7.1, <literal>ONLY</> was the

default behavior. The default can be altered by changing the

configuration parameter <xref linkend="guc-sql-inheritance">.)

The name (possibly schema-qualified) of an existing table to

alter. If <literal>ONLY</> is specified, only that table is

altered. If <literal>ONLY</> is not specified, the table and all

its descendant tables (if any) are updated. <literal>*</> can be

appended to the table name to indicate that descendant tables are

to be altered, but in the current version, this is the default

behavior. (In releases before 7.1, <literal>ONLY</> was the

default behavior. The default can be altered by changing the

configuration parameter <xref linkend="guc-sql-inheritance">.)

</para>

</listitem>

</varlistentry>

<term><replaceable class="PARAMETER">column</replaceable></term>

<listitem>

<para>

Name of a new or existing column.

Name of a new or existing column.

</para>

</listitem>

</varlistentry>

<term><replaceable class="PARAMETER">new_column</replaceable></term>

<listitem>

<para>

New name for an existing column.

New name for an existing column.

</para>

</listitem>

</varlistentry>

<term><replaceable class="PARAMETER">new_name</replaceable></term>

<listitem>

<para>

New name for the table.

New name for the table.

</para>

</listitem>

</varlistentry>

<term><replaceable class="PARAMETER">type</replaceable></term>

<listitem>

<para>

Data type of the new column, or new data type for an existing

column.

Data type of the new column, or new data type for an existing

column.

</para>

</listitem>

</varlistentry>

<term><replaceable class="PARAMETER">table_constraint</replaceable></term>

<listitem>

<para>

New table constraint for the table.

New table constraint for the table.

</para>

</listitem>

</varlistentry>

<term><replaceable class="PARAMETER">constraint_name</replaceable></term>

<listitem>

<para>

Name of an existing constraint to drop.

Name of an existing constraint to drop.

</para>

</listitem>

</varlistentry>

<listitem>

<para>

Automatically drop objects that depend on the dropped column

or constraint (for example, views referencing the column).

or constraint (for example, views referencing the column).

</para>

</listitem>

</varlistentry>

<listitem>

<para>

Refuse to drop the column or constraint if there are any dependent

objects. This is the default behavior.

objects. This is the default behavior.

</para>

</listitem>

</varlistentry>

<term><replaceable class="PARAMETER">index_name</replaceable></term>

<listitem>

<para>

The index name on which the table should be marked for clustering.

The index name on which the table should be marked for clustering.

</para>

</listitem>

</varlistentry>

<term><replaceable class="PARAMETER">new_owner</replaceable></term>

<listitem>

<para>

The user name of the new owner of the table.

The user name of the new owner of the table.

</para>

</listitem>

</varlistentry>

<term><replaceable class="PARAMETER">tablespace_name</replaceable></term>

<listitem>

<para>

The tablespace name to which the table will be moved.

The tablespace name to which the table will be moved.

</para>

</listitem>

</varlistentry>

though a <literal>USING</literal> clause is supplied. In such cases,

drop the default with <literal>DROP DEFAULT</>, perform the <literal>ALTER

TYPE</>, and then use <literal>SET DEFAULT</> to add a suitable new

default.

default. Similar considerations apply to indexes and constraints involving

the column.

</para>

<para>

</para>

<para>

To move a table to a different tablespace:

To move a table to a different tablespace:

<programlisting>

ALTER TABLE distributors SET TABLESPACE fasttablespace;

</programlisting>