ALTER_FUNCTION(7pg14)

πŸ“¦ version 14.24, in opensuse-leap 16.0

πŸ’… ALTER FUNCTION β€” change the definition of a function

okay so bestie, welcome to the glow-up page for ALTER FUNCTION β€” this is the PostgreSQL 14.24 Documentation entry, ALTER FUNCTION(7), and yes we're gonna read the whole thing together, no skipping πŸ’–


✨ NAME ✨

ALTER_FUNCTION β€” change the definition of a function. that's it, that's the vibe check, she edits functions πŸ‘‘


πŸŽ€ SYNOPSIS πŸŽ€

like, literally the exact shapes she comes in:

ALTER FUNCTION name [ ( [ [ argmode ] [ argname ] argtype [, ...] ] ) ]
    action [ ... ] [ RESTRICT ]
ALTER FUNCTION name [ ( [ [ argmode ] [ argname ] argtype [, ...] ] ) ]
    RENAME TO new_name
ALTER FUNCTION name [ ( [ [ argmode ] [ argname ] argtype [, ...] ] ) ]
    OWNER TO { new_owner | CURRENT_ROLE | CURRENT_USER | SESSION_USER }
ALTER FUNCTION name [ ( [ [ argmode ] [ argname ] argtype [, ...] ] ) ]
    SET SCHEMA new_schema
ALTER FUNCTION name [ ( [ [ argmode ] [ argname ] argtype [, ...] ] ) ]
    [ NO ] DEPENDS ON EXTENSION extension_name

where action is one of:

    CALLED ON NULL INPUT | RETURNS NULL ON NULL INPUT | STRICT
    IMMUTABLE | STABLE | VOLATILE
    [ NOT ] LEAKPROOF
    [ EXTERNAL ] SECURITY INVOKER | [ EXTERNAL ] SECURITY DEFINER
    PARALLEL { UNSAFE | RESTRICTED | SAFE }
    COST execution_cost
    ROWS result_rows
    SUPPORT support_function
    SET configuration_parameter { TO | = } { value | DEFAULT }
    SET configuration_parameter FROM CURRENT
    RESET configuration_parameter
    RESET ALL

🌸 DESCRIPTION 🌸

ALTER FUNCTION changes the definition of a function. simple as that, no cap ✨

now the permissions part, because of course there's a permissions part:

  • you must own the function to use ALTER FUNCTION, periodt
  • to change a function's schema, you also need CREATE privilege on the new schema
  • to alter the owner, you also need to be a direct or indirect member of the new owning role, and that role must have CREATE privilege on the function's schema

and why all the gatekeeping? because these restrictions enforce that altering the owner doesn't do anything you couldn't do by dropping and recreating the function. it's giving "no shortcuts, bestie" 🫢

but lowkey a superuser can alter ownership of any function anyway 😌

πŸ¦‹ PARAMETERS πŸ¦‹

  • name β€” the name of an existing function, optionally schema-qualified. heads up: if no argument list is specified, the name must be unique in its schema. no duplicates allowed, iykyk πŸ’…
  • argmode β€” the mode of an argument: IN, OUT, INOUT, or VARIADIC. if you omit it, the default is IN. also, fun fact, ALTER FUNCTION does not actually pay any attention to OUT arguments, since only the input arguments are needed to determine the function's identity. so listing the IN, INOUT, and VARIADIC arguments is sufficient β€” she literally doesn't care about the OUTs πŸ™ˆ
  • argname β€” the name of an argument. and again, ALTER FUNCTION does not actually pay any attention to argument names, since only the argument data types are needed to determine the function's identity. names? irrelevant to her. iconic behavior ngl πŸ’€
  • argtype β€” the data type(s) of the function's arguments, optionally schema-qualified, if any.
  • new_name β€” the new name of the function. rebrand era πŸ¦‹
  • new_owner β€” the new owner of the function. important note: if the function is marked SECURITY DEFINER, it will subsequently execute as the new owner. so like, choose wisely bestie 😭
  • new_schema β€” the new schema for the function.
  • DEPENDS ON EXTENSION extension_name / NO DEPENDS ON EXTENSION extension_name β€” this form marks the function as dependent on the extension, or no longer dependent on that extension if NO is specified πŸ”— a function that's marked as dependent on an extension is dropped when the extension is dropped, even if CASCADE is not specified. and a function can depend upon multiple extensions, and will be dropped when any one of those extensions is dropped. so like, multiple leashes, all of them yank at once πŸ’€
  • CALLED ON NULL INPUT / RETURNS NULL ON NULL INPUT / STRICT β€” CALLED ON NULL INPUT changes the function so that it will be invoked when some or all of its arguments are null. RETURNS NULL ON NULL INPUT or STRICT changes the function so that it is not invoked if any of its arguments are null; instead, a null result is assumed automatically. see CREATE FUNCTION (CREATE_FUNCTION(7)) for more information ✨
  • IMMUTABLE / STABLE / VOLATILE β€” change the volatility of the function to the specified setting. see CREATE FUNCTION (CREATE_FUNCTION(7)) for details 🌈
  • [ EXTERNAL ] SECURITY INVOKER / [ EXTERNAL ] SECURITY DEFINER β€” change whether the function is a security definer or not. the key word EXTERNAL is ignored for SQL conformance. see CREATE FUNCTION (CREATE_FUNCTION(7)) for more information about this capability πŸ‘‘
  • PARALLEL β€” change whether the function is deemed safe for parallelism. see CREATE FUNCTION (CREATE_FUNCTION(7)) for details ⚑
  • LEAKPROOF β€” change whether the function is considered leakproof or not. see CREATE FUNCTION (CREATE_FUNCTION(7)) for more information about this capability πŸ›‘οΈ
  • COST execution_cost β€” change the estimated execution cost of the function. see CREATE FUNCTION (CREATE_FUNCTION(7)) for more information πŸ’Έ
  • ROWS result_rows β€” change the estimated number of rows returned by a set-returning function. see CREATE FUNCTION (CREATE_FUNCTION(7)) for more information πŸ“Š
  • SUPPORT support_function β€” set or change the planner support function to use for this function. see Section 38.11 for details. you must be superuser to use this option πŸ”₯
this option cannot be used to remove the support function altogether, since it must name a new support function. use CREATE OR REPLACE FUNCTION if you need to do that. no "just delete it" energy here, sorry bestie 😭
  • configuration_parameter / value β€” add or change the assignment to be made to a configuration parameter when the function is called. if value is DEFAULT or, equivalently, RESET is used, the function-local setting is removed, so that the function executes with the value present in its environment. use RESET ALL to clear all function-local settings. SET FROM CURRENT saves the value of the parameter that is current when ALTER FUNCTION is executed as the value to be applied when the function is entered 🌸

see SET(7) and Chapter 20 for more information about allowed parameter names and values.

  • RESTRICT β€” ignored for conformance with the SQL standard. she's just there for the vibe πŸŽ€

πŸ’œ EXAMPLES πŸ’œ

okay now the fun part, real examples, copy them exactly bestie:

to rename the function sqrt for type integer to square_root:

ALTER FUNCTION sqrt(integer) RENAME TO square_root;

to change the owner of the function sqrt for type integer to joe:

ALTER FUNCTION sqrt(integer) OWNER TO joe;

to change the schema of the function sqrt for type integer to maths:

ALTER FUNCTION sqrt(integer) SET SCHEMA maths;

to mark the function sqrt for type integer as being dependent on the extension mathlib:

ALTER FUNCTION sqrt(integer) DEPENDS ON EXTENSION mathlib;

to adjust the search path that is automatically set for a function:

ALTER FUNCTION check_password(text) SET search_path = admin, pg_temp;

to disable automatic setting of search_path for a function:

ALTER FUNCTION check_password(text) RESET search_path;

and after that last one, the function will now execute with whatever search path is used by its caller. she's free, she's independent, she borrows your search path πŸ¦‹βœ¨


⭐ COMPATIBILITY ⭐

this statement is partially compatible with the ALTER FUNCTION statement in the SQL standard 🫢

like, the standard allows more properties of a function to be modified, but it does not provide the ability to:

  • rename a function
  • make a function a security definer
  • attach configuration parameter values to a function
  • change the owner, schema, or volatility of a function

the standard also requires the RESTRICT key word, which is optional in PostgreSQL. so we're out here being flexible, we love that for us πŸ’…


🌈 SEE ALSO 🌈


and that's the whole page bestie, you ate that πŸ“ this was ALTER FUNCTION(7) from PostgreSQL 14.24, dated 2026 β€” go forth and alter your functions, but like, responsibly πŸ‘‘πŸ’–

πŸ“¦ where this page comes from