DROP_STATISTICS(7)

💅 DROP STATISTICS 💅

okay bestie, welcome to DROP_STATISTICS(7) — that's the PostgreSQL 18.6 documentation page, and she's a short one but she's important, so let's get into it ✨

---

🌸 NAME 🌸

DROP_STATISTICS — remove extended statistics 🗑️✨

---

🎀 SYNOPSIS 🎀

DROP STATISTICS [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]

that's it. that's the whole vibe. short, sweet, devastating 💅

---

🦋 DESCRIPTION 🦋

so, DROP STATISTICS removes statistics object(s) from the database. like, gone gone. poof 🫶

but ngl there's a gatekeeper, and the gatekeeper is permissions. Only these three people can drop a statistics object:

• the statistics object's owner
• the schema owner
• a superuser

that's the list. no plus-ones. periodt 👑

---

✨ PARAMETERS ✨

• IF EXISTS — do not throw an error if the statistics object does not exist. a notice is issued in this case. so instead of a whole dramatic meltdown, you just get a lil "hey, that wasn't there btw" 😌
• name — the name (optionally schema-qualified) of the statistics object to drop. so like, myschema.mystats is valid, and so is just mystats. iykyk 🧚
• CASCADE
• RESTRICT — okay so these two key words do not have any effect, since there are no dependencies on statistics. they're literally just there vibing. main character energy with zero plot relevance 💀

---

🌈 EXAMPLES 🌈

want to destroy two statistics objects in different schemas, without failing if they don't exist? say less:

DROP STATISTICS IF EXISTS
    accounting.users_uid_creation,
    public.grants_user_role;

two schemas, one command, zero tears. slay 🔥

---

💜 COMPATIBILITY 💜

there is no DROP STATISTICS command in the SQL standard. so if you're out here trying to be standards-compliant about it... girl, there's nothing to comply with 🙈

---

⭐ SEE ALSO ⭐

• ALTER STATISTICS (ALTER_STATISTICS(7))
• CREATE STATISTICS (CREATE_STATISTICS(7))

---

and that's the whole page, bestie!! this one came to you from PostgreSQL 18.6, dated 2026 — love her, respect her, drop your stats responsibly 💖🎀🦋