DROP_AGGREGATE(7pg15)

💅 NAME

okay so this is the DROP AGGREGATE manual page — you can call it DROP_AGGREGATE(7pg15) if you're in the group chat — and it's literally all about removing an aggregate function. No cap. The NAME vibe is: DROP_AGGREGATE — remove an aggregate function. 💖

✨ SYNOPSIS ✨

DROP AGGREGATE [ IF EXISTS ] name ( aggregate_signature ) [, ...] [ CASCADE | RESTRICT ]

where aggregate_signature is:

* |
[ argmode ] [ argname ] argtype [ , ... ] |
[ [ argmode ] [ argname ] argtype [ , ... ] ] ORDER BY [ argmode ] [ argname ] argtype [ , ... ]

🫶 DESCRIPTION 🫶

DROP AGGREGATE removes an existing aggregate function. To execute this command the current user must be the owner of the aggregate function. That's the whole main-character requirement, bestie: you gotta own it. 👑

🎀 PARAMETERS 🎀

• IF EXISTS — do not throw an error if the aggregate does not exist. A notice is issued in this case. So it's giving "no drama if it's already gone."
• name — the name (optionally schema-qualified) of an existing aggregate function. iykyk, schema-qualified is your friend.
• argmode — the mode of an argument: IN or VARIADIC. If omitted, the default is IN.
• argname — the name of an argument. Note that DROP AGGREGATE does not actually pay any attention to argument names, since only the argument data types are needed to determine the aggregate function's identity. So the name is lowkey just vibes here.
• argtype — an input data type on which the aggregate function operates. To reference a zero-argument aggregate function, write * in place of the list of argument specifications. To reference an ordered-set aggregate function, write ORDER BY between the direct and aggregated argument specifications.
• CASCADE — automatically drop objects that depend on the aggregate function (such as views using it), and in turn all objects that depend on those objects (see Section 5.14). This is the full-send option, bestie.
• RESTRICT — refuse to drop the aggregate function if any objects depend on it. This is the default. Safe, polite, boundaries intact.

CASCADE is dramatic in the best way: it takes the dependent objects with it, then the objects that depend on those objects too (see Section 5.14). Do not pretend you didn't read that. 💀

🧚 NOTES 🧚

Alternative syntaxes for referencing ordered-set aggregates are described under ALTER AGGREGATE (ALTER_AGGREGATE(7)). Go look if you're feeling fancy.

🌸 EXAMPLES 🌸

To remove the aggregate function myavg for type integer:

DROP AGGREGATE myavg(integer);

To remove the hypothetical-set aggregate function myrank, which takes an arbitrary list of ordering columns and a matching list of direct arguments:

DROP AGGREGATE myrank(VARIADIC "any" ORDER BY VARIADIC "any");

To remove multiple aggregate functions in one command:

DROP AGGREGATE myavg(integer), myavg(bigint);

⭐ COMPATIBILITY ⭐

There is no DROP AGGREGATE statement in the SQL standard. Periodt. The SQL standard simply did not include it. 🙈

🔥 SEE ALSO 🔥

ALTER AGGREGATE (ALTER_AGGREGATE(7)), CREATE AGGREGATE (CREATE_AGGREGATE(7)) 💖✨

---

okay that's the whole page, bestie! sign-off time: this is the DROP AGGREGATE(7) page from the PostgreSQL 15.19 docs, dated 2026. mwah 💋🎀🦋