PolarDB:ALTER OPERATOR

Description

To use ALTER OPERATOR, you must own the operator. To change the owner, you must also be a direct or indirect member of the new owning role, and that role must have CREATE privilege on the operator's schema. These restrictions ensure that changing the owner is equivalent to dropping and recreating the operator — no privilege escalation is possible. Superusers can change the ownership of any operator regardless of these restrictions.

Synopsis

ALTER OPERATOR name ( { left_type | NONE } , { right_type | NONE } )
        OWNER TO { new_owner | CURRENT_USER | SESSION_USER }

ALTER OPERATOR name ( { left_type | NONE } , { right_type | NONE } )
        SET SCHEMA new_schema

ALTER OPERATOR name ( { left_type | NONE } , { right_type | NONE } )
        SET ( {  RESTRICT = { res_proc | NONE }
               | JOIN = { join_proc | NONE }
             } [, ... ] )

Parameters

name: The name (optionally schema-qualified) of an existing operator.

left_type: The data type of the operator's left operand. Write NONE if the operator has no left operand.

right_type: The data type of the operator's right operand. Write NONE if the operator has no right operand.

new_owner: The new owner of the operator.

new_schema: The new schema for the operator.

res_proc: The restriction selectivity estimator function for this operator. Write NONE to remove the existing selectivity estimator.

join_proc: The join selectivity estimator function for this operator. Write NONE to remove the existing selectivity estimator.

Examples

Change the owner of a custom operator @@ for type text:

ALTER OPERATOR @@ (text, text) OWNER TO joe;

Change the restriction and join selectivity estimator functions of a custom operator && for type int[]:

ALTER OPERATOR && (_int4, _int4) SET (RESTRICT = _int_contsel, JOIN = _int_contjoinsel);