create_conversion(7) [centos man page]

CREATE 
CONVERSION(7)					  PostgreSQL 9.2.7 Documentation				      CREATE CONVERSION(7)

NAME

       CREATE_CONVERSION - define a new encoding conversion

SYNOPSIS

       CREATE [ DEFAULT ] CONVERSION name
	   FOR source_encoding TO dest_encoding FROM function_name

DESCRIPTION

       CREATE CONVERSION defines a new conversion between character set encodings. Also, conversions that are marked DEFAULT can be used for
       automatic encoding conversion between client and server. For this purpose, two conversions, from encoding A to B and from encoding B to A,
       must be defined.

       To be able to create a conversion, you must have EXECUTE privilege on the function and CREATE privilege on the destination schema.

PARAMETERS

       DEFAULT
	   The DEFAULT clause indicates that this conversion is the default for this particular source to destination encoding. There should be
	   only one default encoding in a schema for the encoding pair.

       name
	   The name of the conversion. The conversion name can be schema-qualified. If it is not, the conversion is defined in the current schema.
	   The conversion name must be unique within a schema.

       source_encoding
	   The source encoding name.

       dest_encoding
	   The destination encoding name.

       function_name
	   The function used to perform the conversion. The function name can be schema-qualified. If it is not, the function will be looked up in
	   the path.

	   The function must have the following signature:

	       conv_proc(
		   integer,  -- source encoding ID
		   integer,  -- destination encoding ID
		   cstring,  -- source string (null terminated C string)
		   internal, -- destination (fill with a null terminated C string)
		   integer   -- source string length
	       ) RETURNS void;

NOTES

       Use DROP CONVERSION to remove user-defined conversions.

       The privileges required to create a conversion might be changed in a future release.

EXAMPLES

       To create a conversion from encoding UTF8 to LATIN1 using myfunc:

	   CREATE CONVERSION myconv FOR 'UTF8' TO 'LATIN1' FROM myfunc;

COMPATIBILITY

       CREATE CONVERSION is a PostgreSQL extension. There is no CREATE CONVERSION statement in the SQL standard, but a CREATE TRANSLATION
       statement that is very similar in purpose and syntax.

SEE ALSO

       ALTER CONVERSION (ALTER_CONVERSION(7)), CREATE FUNCTION (CREATE_FUNCTION(7)), DROP CONVERSION (DROP_CONVERSION(7))

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

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 [ ... ] ]

DESCRIPTION

       CREATE  SCHEMA enters 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  can  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). A CREATE command specifying an unqualified object name creates the
       object in the current schema (the one at the front of the search path, which can be determined with the function current_schema).

       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.

PARAMETERS

       schemaname
	      The name of a schema to be created. If this is omitted, the user name is used as the schema name. The name cannot begin with pg_, as
	      such names are reserved for system schemas.

       username
	      The name of the user who will own the schema. If omitted, defaults to the user executing the command.  Only  superusers  can  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, CREATE INDEX, CREATE
	      SEQUENCE, CREATE TRIGGER and GRANT are accepted as clauses within CREATE SCHEMA. Other kinds of objects may be created  in  separate
	      commands after the schema is created.

NOTES

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

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

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

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

       According to the SQL standard, 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 the CREATE privilege on his schema to someone else.

SEE ALSO

       ALTER SCHEMA [alter_schema(7)], DROP SCHEMA [drop_schema(7)]

SQL - Language Statements					    2010-05-14							  CREATE SCHEMA(7)