ALTER EXTENSION — change the definition of an extension
nameUPDATE [ TO
new_version] ALTER EXTENSION
member_objectis: ACCESS METHOD
aggregate_signature) | CAST (
target_type) | COLLATION
object_name| EVENT TRIGGER
object_name| FOREIGN DATA WRAPPER
object_name| FOREIGN TABLE
function_name[ ( [ [
argtype[, ...] ] ) ] | MATERIALIZED VIEW
right_type) | OPERATOR CLASS
index_method| OPERATOR FAMILY
index_method| [ PROCEDURAL ] LANGUAGE
procedure_name[ ( [ [
argtype[, ...] ] ) ] | ROUTINE
routine_name[ ( [ [
argtype[, ...] ] ) ] | SCHEMA
object_name| TEXT SEARCH CONFIGURATION
object_name| TEXT SEARCH DICTIONARY
object_name| TEXT SEARCH PARSER
object_name| TEXT SEARCH TEMPLATE
object_name| TRANSFORM FOR
aggregate_signatureis: * | [
argtype[ , ... ] | [ [
argtype[ , ... ] ] ORDER BY [
argtype[ , ... ]
ALTER EXTENSION changes the
definition of an installed extension. There are several
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.
This form moves the extension's objects into another schema. The extension has to be relocatable for this command to succeed.
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.
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 Section 38.16 for more information about these operations.
You must own the extension to use
ALTER EXTENSION. The
require ownership of the added/dropped object as well.
The name of an installed extension.
The desired new version of the extension. This can be
written as either an identifier or a string literal. If
UPDATE attempts to update to whatever is shown as
the default version in the extension's control file.
The new schema for the extension.
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, procedures, routines, sequences, text search objects, types, and views can be schema-qualified.
The name of the source data type of the cast.
The name of the target data type of the cast.
The mode of a function, procedure, or aggregate
VARIADIC. If omitted, the
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
The name of a function, procedure, or aggregate
argument. Note that
EXTENSION does not actually pay any attention to
argument names, since only the argument data types are
needed to determine the function's identity.
The data type of a function, procedure, or aggregate argument.
The data type(s) of the operator's arguments
(optionally schema-qualified). Write
NONE for the missing argument of a
prefix or postfix operator.
This is a noise word.
The name of the data type of the transform.
The name of the language of the transform.
To update the
to version 2.0:
ALTER EXTENSION hstore UPDATE TO '2.0';
To change the schema of the
hstore extension to
ALTER EXTENSION hstore SET SCHEMA utils;
To add an existing function to the
ALTER EXTENSION hstore ADD FUNCTION populate_record(anyelement, hstore);
ALTER EXTENSION is a
If you see anything in the documentation that is not correct, does not match your experience with the particular feature or requires further clarification, please use this form to report a documentation issue.