ALTER EXTENSION — change the definition of an extension
ALTER EXTENSIONname
UPDATE [ TOnew_version
] ALTER EXTENSIONname
SET SCHEMAnew_schema
ALTER EXTENSIONname
ADDmember_object
ALTER EXTENSIONname
DROPmember_object
wheremember_object
is: AGGREGATEaggregate_name
(aggregate_signature
) | CAST (source_type
AStarget_type
) | COLLATIONobject_name
| CONVERSIONobject_name
| DOMAINobject_name
| EVENT TRIGGERobject_name
| FOREIGN DATA WRAPPERobject_name
| FOREIGN TABLEobject_name
| FUNCTIONfunction_name
( [ [argmode
] [argname
]argtype
[, ...] ] ) | MATERIALIZED VIEWobject_name
| OPERATORoperator_name
(left_type
,right_type
) | OPERATOR CLASSobject_name
USINGindex_method
| OPERATOR FAMILYobject_name
USINGindex_method
| [ PROCEDURAL ] LANGUAGEobject_name
| SCHEMAobject_name
| SEQUENCEobject_name
| SERVERobject_name
| TABLEobject_name
| TEXT SEARCH CONFIGURATIONobject_name
| TEXT SEARCH DICTIONARYobject_name
| TEXT SEARCH PARSERobject_name
| TEXT SEARCH TEMPLATEobject_name
| TYPEobject_name
| VIEWobject_name
andaggregate_signature
is: * | [argmode
] [argname
]argtype
[ , ... ] | [ [argmode
] [argname
]argtype
[ , ... ] ] ORDER BY [argmode
] [argname
]argtype
[ , ... ]
ALTER EXTENSION changes the definition of an installed extension. There are several subforms:
UPDATE
This form updates the extension to a newer version. The extension must supply a suitable update script (or series of scripts) that can modify the currently-installed version into the requested version.
SET SCHEMA
This form moves the extension's objects into another schema. The extension has to be relocatable for this command to succeed.
ADD member_object
This form adds an existing object to the extension. This is mainly useful in extension update scripts. The object will subsequently be treated as a member of the extension; notably, it can only be dropped by dropping the extension.
DROP member_object
This form removes a member object from the extension. This is mainly useful in extension update scripts. The object is not dropped, only disassociated from the extension.
See the section called “Packaging Related Objects into an Extension” for more information about these operations.
You must own the extension to use ALTER EXTENSION.
The ADD
/DROP
forms require ownership of the
added/dropped object as well.
name
The name of an installed extension.
new_version
The desired new version of the extension. This can be written as either an identifier or a string literal. If not specified, ALTER EXTENSION UPDATE attempts to update to whatever is shown as the default version in the extension's control file.
new_schema
The new schema for the extension.
object_name
, aggregate_name
, function_name
, operator_name
The name of an object to be added to or removed from the extension. Names of tables, aggregates, domains, foreign tables, functions, operators, operator classes, operator families, sequences, text search objects, types, and views can be schema-qualified.
source_type
The name of the source data type of the cast.
target_type
The name of the target data type of the cast.
argmode
The mode of a function or aggregate
argument: IN
, OUT
,
INOUT
, or VARIADIC
.
If omitted, the default is IN
.
Note that ALTER EXTENSION does not actually pay
any attention to OUT
arguments, since only the input
arguments are needed to determine the function's identity.
So it is sufficient to list the IN
, INOUT
,
and VARIADIC
arguments.
argname
The name of a function or aggregate argument. Note that ALTER EXTENSION does not actually pay any attention to argument names, since only the argument data types are needed to determine the function's identity.
argtype
The data type of a function or aggregate argument.
left_type
, right_type
The data type(s) of the operator's arguments (optionally
schema-qualified). Write NONE
for the missing argument
of a prefix or postfix operator.
PROCEDURAL
This is a noise word.
To update the hstore
extension to version 2.0:
ALTER EXTENSION hstore UPDATE TO '2.0';
To change the schema of the hstore
extension
to utils
:
ALTER EXTENSION hstore SET SCHEMA utils;
To add an existing function to the hstore
extension:
ALTER EXTENSION hstore ADD FUNCTION populate_record(anyelement, hstore);