create_schema(7) [redhat man page]

CREATE 
SCHEMA(7)						   SQL Commands 						  CREATE SCHEMA(7)

NAME

       CREATE SCHEMA - define a new schema

SYNOPSIS

       CREATE SCHEMA schemaname [ AUTHORIZATION username ] [ schema_element [ ... ] ]
       CREATE SCHEMA AUTHORIZATION username [ schema_element [ ... ] ]

   INPUTS
       schemaname
	      The name of a schema to be created. If this is omitted, the user name is used as the schema name.

       username
	      The  name  of  the  user who will own the schema. If omitted, defaults to the user executing the command. Only superusers may create
	      schemas owned by users other than themselves.

       schema_element
	      An SQL statement defining an object to be created within the schema.  Currently, only CREATE  TABLE,  CREATE  VIEW,  and	GRANT  are
	      accepted as clauses within CREATE SCHEMA. Other kinds of objects may be created in separate commands after the schema is created.

   OUTPUTS
       CREATE SCHEMA
	      Message returned if the command is successful.

       ERROR: namespace "schemaname" already exists
	      If the schema specified already exists.

DESCRIPTION

       CREATE  SCHEMA will enter a new schema into the current database.  The schema name must be distinct from the name of any existing schema in
       the current database.

       A schema is essentially a namespace: it contains named objects (tables, data types, functions, and operators)  whose  names  may  duplicate
       those of other objects existing in other schemas. Named objects are accessed either by ``qualifying'' their names with the schema name as a
       prefix, or by setting a search path that includes the desired schema(s).

       Optionally, CREATE SCHEMA can include subcommands to create objects within the new schema. The subcommands are treated essentially the same
       as  separate  commands  issued  after creating the schema, except that if the AUTHORIZATION clause is used, all the created objects will be
       owned by that user.

   NOTES
       To create a schema, the invoking user must have CREATE privilege for the current database. (Of course, superusers bypass this check.)

       Use DROP SCHEMA to remove a schema.

EXAMPLES

       Create a schema:

       CREATE SCHEMA myschema;

       Create a schema for user joe --- the schema will also be named joe:

       CREATE SCHEMA AUTHORIZATION joe;

       Create a schema and create a table and view within it:

       CREATE SCHEMA hollywood
	   CREATE TABLE films (title text, release date, awards text[])
	   CREATE VIEW winners AS
	       SELECT title, release FROM films WHERE awards IS NOT NULL;

       Notice that the individual subcommands do not end with semicolons.

       The following is an equivalent way of accomplishing the same result:

       CREATE SCHEMA hollywood;
       CREATE TABLE hollywood.films (title text, release date, awards text[]);
       CREATE VIEW hollywood.winners AS
	   SELECT title, release FROM hollywood.films WHERE awards IS NOT NULL;

COMPATIBILITY

   SQL92
       SQL92 allows a DEFAULT CHARACTER SET clause in CREATE SCHEMA, as well as more subcommand types than are presently accepted by PostgreSQL.

       SQL92 specifies that the subcommands in CREATE SCHEMA may appear in any order. The present PostgreSQL implementation does  not  handle  all
       cases of forward references in subcommands; it may sometimes be necessary to reorder the subcommands to avoid forward references.

       In  SQL92, the owner of a schema always owns all objects within it.  PostgreSQL allows schemas to contain objects owned by users other than
       the schema owner. This can happen only if the schema owner grants CREATE rights on his schema to someone else.

SQL - Language Statements					    2002-11-22							  CREATE SCHEMA(7)

CREATE 
EXTENSION(7)					  PostgreSQL 9.2.7 Documentation				       CREATE EXTENSION(7)

NAME

       CREATE_EXTENSION - install an extension

SYNOPSIS

       CREATE EXTENSION [ IF NOT EXISTS ] extension_name
	   [ WITH ] [ SCHEMA schema_name ]
		    [ VERSION version ]
		    [ FROM old_version ]

DESCRIPTION

       CREATE EXTENSION loads a new extension into the current database. There must not be an extension of the same name already loaded.

       Loading an extension essentially amounts to running the extension's script file. The script will typically create new SQL objects such as
       functions, data types, operators and index support methods.  CREATE EXTENSION additionally records the identities of all the created
       objects, so that they can be dropped again if DROP EXTENSION is issued.

       Loading an extension requires the same privileges that would be required to create its component objects. For most extensions this means
       superuser or database owner privileges are needed. The user who runs CREATE EXTENSION becomes the owner of the extension for purposes of
       later privilege checks, as well as the owner of any objects created by the extension's script.

PARAMETERS

       IF NOT EXISTS
	   Do not throw an error if an extension with the same name already exists. A notice is issued in this case. Note that there is no
	   guarantee that the existing extension is anything like the one that would have been created from the currently-available script file.

       extension_name
	   The name of the extension to be installed.  PostgreSQL will create the extension using details from the file
	   SHAREDIR/extension/extension_name.control.

       schema_name
	   The name of the schema in which to install the extension's objects, given that the extension allows its contents to be relocated. The
	   named schema must already exist. If not specified, and the extension's control file does not specify a schema either, the current
	   default object creation schema is used.

	   Remember that the extension itself is not considered to be within any schema: extensions have unqualified names that must be unique
	   database-wide. But objects belonging to the extension can be within schemas.

       version
	   The version of the extension to install. This can be written as either an identifier or a string literal. The default version is
	   whatever is specified in the extension's control file.

       old_version
	   FROM old_version must be specified when, and only when, you are attempting to install an extension that replaces an "old style" module
	   that is just a collection of objects not packaged into an extension. This option causes CREATE EXTENSION to run an alternative
	   installation script that absorbs the existing objects into the extension, instead of creating new objects. Be careful that SCHEMA
	   specifies the schema containing these pre-existing objects.

	   The value to use for old_version is determined by the extension's author, and might vary if there is more than one version of the
	   old-style module that can be upgraded into an extension. For the standard additional modules supplied with pre-9.1 PostgreSQL, use
	   unpackaged for old_version when updating a module to extension style.

NOTES

       Before you can use CREATE EXTENSION to load an extension into a database, the extension's supporting files must be installed. Information
       about installing the extensions supplied with PostgreSQL can be found in Additional Supplied Modules.

       The extensions currently available for loading can be identified from the pg_available_extensions or pg_available_extension_versions system
       views.

       For information about writing new extensions, see Section 35.15, "Packaging Related Objects into an Extension", in the documentation.

EXAMPLES

       Install the hstore extension into the current database:

	   CREATE EXTENSION hstore;

       Update a pre-9.1 installation of hstore into extension style:

	   CREATE EXTENSION hstore SCHEMA public FROM unpackaged;

       Be careful to specify the schema in which you installed the existing hstore objects.

COMPATIBILITY

       CREATE EXTENSION is a PostgreSQL extension.

SEE ALSO

       ALTER EXTENSION (ALTER_EXTENSION(7)), DROP EXTENSION (DROP_EXTENSION(7))

PostgreSQL 9.2.7						    2014-02-17						       CREATE EXTENSION(7)