Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

create_tablespace(7) [mojave man page]

CREATE TABLESPACE - define a new tablespace SYNOPSIS
CREATE TABLESPACE tablespacename [ OWNER username ] LOCATION 'directory' DESCRIPTION
CREATE TABLESPACE registers a new cluster-wide tablespace. The tablespace name must be distinct from the name of any existing tablespace in the database cluster. A tablespace allows superusers to define an alternative location on the file system where the data files containing database objects (such as tables and indexes) can reside. A user with appropriate privileges can pass tablespacename to CREATE DATABASE, CREATE TABLE, CREATE INDEX or ADD CONSTRAINT to have the data files for these objects stored within the specified tablespace. PARAMETERS
tablespacename The name of a tablespace to be created. The name cannot begin with pg_, as such names are reserved for system tablespaces. username The name of the user who will own the tablespace. If omitted, defaults to the user executing the command. Only superusers can create tablespaces, but they can assign ownership of tablespaces to non-superusers. directory The directory that will be used for the tablespace. The directory must be empty and must be owned by the PostgreSQL system user. The directory must be specified by an absolute path name. NOTES
Tablespaces are only supported on systems that support symbolic links. CREATE TABLESPACE cannot be executed inside a transaction block. EXAMPLES
Create a tablespace dbspace at /data/dbs: CREATE TABLESPACE dbspace LOCATION '/data/dbs'; Create a tablespace indexspace at /data/indexes owned by user genevieve: CREATE TABLESPACE indexspace OWNER genevieve LOCATION '/data/indexes'; COMPATIBILITY
CREATE DATABASE [create_database(7)], CREATE TABLE [create_table(7)], CREATE INDEX [create_index(7)], DROP TABLESPACE [drop_tablespace(7)], ALTER TABLESPACE [alter_tablespace(7)] SQL - Language Statements 2010-05-14 CREATE TABLESPACE(7)

Check Out this Related Man Page

ALTER DATABASE - change a database SYNOPSIS
ALTER DATABASE name [ [ WITH ] option [ ... ] ] where option can be: CONNECTION LIMIT connlimit ALTER DATABASE name RENAME TO newname ALTER DATABASE name OWNER TO new_owner ALTER DATABASE name SET TABLESPACE new_tablespace ALTER DATABASE name SET configuration_parameter { TO | = } { value | DEFAULT } ALTER DATABASE name SET configuration_parameter FROM CURRENT ALTER DATABASE name RESET configuration_parameter ALTER DATABASE name 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 set- tings. 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 own the database and also be a direct or indirect member of 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. Note that tables and indexes in non-default tablespaces are not affected. 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 The name of the database whose attributes are to be altered. connlimit How many concurrent connections can be made to this database. -1 means no limit. newname The new name of the database. new_owner The new owner of the database. new_tablespace The new default tablespace of the database. configuration_parameter value Set this database's session default for the specified configuration parameter to the given value. If value is DEFAULT or, equiva- lently, RESET is used, the database-specific setting is removed, so the system-wide default setting will be inherited in new ses- sions. Use RESET ALL to clear all database-specific settings. SET FROM CURRENT saves the session's current value of the parameter as the database-specific value. See SET [set(7)] and in the documentation 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: ALTER DATABASE test SET enable_indexscan TO off; COMPATIBILITY
The ALTER DATABASE statement is a PostgreSQL extension. SEE ALSO
CREATE DATABASE [create_database(7)], DROP DATABASE [drop_database(7)], SET [set(7)], CREATE TABLESPACE [create_tablespace(7)] SQL - Language Statements 2010-05-14 ALTER DATABASE(7)
Man Page