alter_user_mapping(7) [centos man page]

ALTER USER 
MAPPING(7)					  PostgreSQL 9.2.7 Documentation				     ALTER USER MAPPING(7)

NAME

       ALTER_USER_MAPPING - change the definition of a user mapping

SYNOPSIS

       ALTER USER MAPPING FOR { user_name | USER | CURRENT_USER | PUBLIC }
	   SERVER server_name
	   OPTIONS ( [ ADD | SET | DROP ] option ['value'] [, ... ] )

DESCRIPTION

       ALTER USER MAPPING changes the definition of a user mapping.

       The owner of a foreign server can alter user mappings for that server for any user. Also, a user can alter a user mapping for his own user
       name if USAGE privilege on the server has been granted to the user.

PARAMETERS

       user_name
	   User name of the mapping.  CURRENT_USER and USER match the name of the current user.  PUBLIC is used to match all present and future
	   user names in the system.

       server_name
	   Server name of the user mapping.

       OPTIONS ( [ ADD | SET | DROP ] option ['value'] [, ... ] )
	   Change options for the user mapping. The new options override any previously specified options.  ADD, SET, and DROP specify the action
	   to be performed.  ADD is assumed if no operation is explicitly specified. Option names must be unique; options are also validated by
	   the server's foreign-data wrapper.

EXAMPLES

       Change the password for user mapping bob, serverfoo:

	   ALTER USER MAPPING FOR bob SERVER foo OPTIONS (user 'bob', password 'public');

COMPATIBILITY

       ALTER USER MAPPING conforms to ISO/IEC 9075-9 (SQL/MED). There is a subtle syntax issue: The standard omits the FOR key word. Since both
       CREATE USER MAPPING and DROP USER MAPPING use FOR in analogous positions, and IBM DB2 (being the other major SQL/MED implementation) also
       requires it for ALTER USER MAPPING, PostgreSQL diverges from the standard here in the interest of consistency and interoperability.

SEE ALSO

       CREATE USER MAPPING (CREATE_USER_MAPPING(7)), DROP USER MAPPING (DROP_USER_MAPPING(7))

PostgreSQL 9.2.7						    2014-02-17						     ALTER USER MAPPING(7)

ALTER TEXT SEARCH 
CONFIGURATION(7)			  PostgreSQL 9.2.7 Documentation			ALTER TEXT SEARCH CONFIGURATION(7)

NAME

       ALTER_TEXT_SEARCH_CONFIGURATION - change the definition of a text search configuration

SYNOPSIS

       ALTER TEXT SEARCH CONFIGURATION name
	   ADD MAPPING FOR token_type [, ... ] WITH dictionary_name [, ... ]
       ALTER TEXT SEARCH CONFIGURATION name
	   ALTER MAPPING FOR token_type [, ... ] WITH dictionary_name [, ... ]
       ALTER TEXT SEARCH CONFIGURATION name
	   ALTER MAPPING REPLACE old_dictionary WITH new_dictionary
       ALTER TEXT SEARCH CONFIGURATION name
	   ALTER MAPPING FOR token_type [, ... ] REPLACE old_dictionary WITH new_dictionary
       ALTER TEXT SEARCH CONFIGURATION name
	   DROP MAPPING [ IF EXISTS ] FOR token_type [, ... ]
       ALTER TEXT SEARCH CONFIGURATION name RENAME TO new_name
       ALTER TEXT SEARCH CONFIGURATION name OWNER TO new_owner
       ALTER TEXT SEARCH CONFIGURATION name SET SCHEMA new_schema

DESCRIPTION

       ALTER TEXT SEARCH CONFIGURATION changes the definition of a text search configuration. You can modify its mappings from token types to
       dictionaries, or change the configuration's name or owner.

       You must be the owner of the configuration to use ALTER TEXT SEARCH CONFIGURATION.

PARAMETERS

       name
	   The name (optionally schema-qualified) of an existing text search configuration.

       token_type
	   The name of a token type that is emitted by the configuration's parser.

       dictionary_name
	   The name of a text search dictionary to be consulted for the specified token type(s). If multiple dictionaries are listed, they are
	   consulted in the specified order.

       old_dictionary
	   The name of a text search dictionary to be replaced in the mapping.

       new_dictionary
	   The name of a text search dictionary to be substituted for old_dictionary.

       new_name
	   The new name of the text search configuration.

       new_owner
	   The new owner of the text search configuration.

       new_schema
	   The new schema for the text search configuration.

       The ADD MAPPING FOR form installs a list of dictionaries to be consulted for the specified token type(s); it is an error if there is
       already a mapping for any of the token types. The ALTER MAPPING FOR form does the same, but first removing any existing mapping for those
       token types. The ALTER MAPPING REPLACE forms substitute new_dictionary for old_dictionary anywhere the latter appears. This is done for
       only the specified token types when FOR appears, or for all mappings of the configuration when it doesn't. The DROP MAPPING form removes
       all dictionaries for the specified token type(s), causing tokens of those types to be ignored by the text search configuration. It is an
       error if there is no mapping for the token types, unless IF EXISTS appears.

EXAMPLES

       The following example replaces the english dictionary with the swedish dictionary anywhere that english is used within my_config.

	   ALTER TEXT SEARCH CONFIGURATION my_config
	     ALTER MAPPING REPLACE english WITH swedish;

COMPATIBILITY

       There is no ALTER TEXT SEARCH CONFIGURATION statement in the SQL standard.

SEE ALSO

       CREATE TEXT SEARCH CONFIGURATION (CREATE_TEXT_SEARCH_CONFIGURATION(7)), DROP TEXT SEARCH CONFIGURATION (DROP_TEXT_SEARCH_CONFIGURATION(7))

PostgreSQL 9.2.7						    2014-02-17					ALTER TEXT SEARCH CONFIGURATION(7)