DROP_AGGREGATE(7pg16)

💅 DROP_AGGREGATE(7) — PostgreSQL 16.15 Documentation 💅

Hii bestie, welcome to the DROP AGGREGATE(7) page from the PostgreSQL 16.15 docs 💖 This is the one where we remove an aggregate function, and yes, the vibes are immaculate cleanup energy ✨

---

🌸 NAME 🌸

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 🦋

Okay so 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 rule, bestie — no cap 👑

---

✨ PARAMETERS ✨

• IF EXISTS — do not throw an error if the aggregate does not exist. A notice is issued in this case. Very “no drama, just a little heads-up” of it 💅
• name — the name (optionally schema-qualified) of an existing aggregate function. Slay, but make sure it's the right one 🎀
• argmode — the mode of an argument: IN or VARIADIC. If omitted, the default is IN. Lowkey important, highkey iconic ✨
• 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 yeah, the names are giving decoration, not main character energy 🙈
• 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. This is the part where the syntax gets a little fancy, but you got this 💖
• 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). It's giving domino effect, so use it with intention 🌈
• RESTRICT — refuse to drop the aggregate function if any objects depend on it. This is the default. The safe little guardrail keeping your schema from chaos 🫶

---

🧚 NOTES 🧚

Alternative syntaxes for referencing ordered-set aggregates are described under ALTER AGGREGATE (ALTER_AGGREGATE(7)). Go check that page if you want the extra lore 📖✨

---

🍓 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. So this one is PostgreSQL-specific, bestie — no standard-SQL twin to match with 💀

---

👑 SEE ALSO 👑

ALTER AGGREGATE (ALTER_AGGREGATE(7)), CREATE AGGREGATE (CREATE_AGGREGATE(7)) 💜

---

xoxo, from the PostgreSQL 16.15 docs, dated 2026, page DROP AGGREGATE(7) — bye bestie, go drop those aggregates responsibly 💖✨🎀