DROP_SEQUENCE(7)

✨ DROP SEQUENCE ✨

okay bestie, welcome to the DROP SEQUENCE page of the PostgreSQL 18.6 docs (manual section 7, for the record) 💖 this is the one where we say bye-bye to a sequence, and honestly? it's giving spring cleaning 🧹✨

---

🌸 NAME 🌸

DROP_SEQUENCE — remove a sequence 💅

---

🦋 SYNOPSIS 🦋

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

---

🎀 DESCRIPTION 🎀

So DROP SEQUENCE removes sequence number generators. that's the whole vibe. but listen — not just anyone can do it: a sequence can only be dropped by its owner or a superuser. no random walk-ups, no cap 🫶

---

💖 PARAMETERS 💖

• IF EXISTS — don't throw an error if the sequence literally does not exist. instead a notice gets issued in that case. so chill of it 🙈
• name — the name of a sequence (and yes, it can be schema-qualified if you're feeling fancy 🎀).
• CASCADE — automatically drops objects that depend on the sequence, and in turn all the objects that depend on those objects (peep Section 5.15 for the lore). it's the domino effect, it's giving chain reaction 💀
• RESTRICT — refuse to drop the sequence if any objects depend on it. this is the default, so it's the chill safe one 🧚

---

🌈 EXAMPLES 🌈

wanna remove the sequence serial? say less:

DROP SEQUENCE serial;

and that's it, she's gone, main character exit 👑

---

⭐ COMPATIBILITY ⭐

DROP SEQUENCE conforms to the SQL standard 🫶 except — plot twist — the standard only allows one sequence to be dropped per command. and also, apart from the IF EXISTS option, which is a PostgreSQL extension. so we're a little extra, as always 💅

---

👑 SEE ALSO 👑

• CREATE SEQUENCE (CREATE_SEQUENCE(7))
• ALTER SEQUENCE (ALTER_SEQUENCE(7))

---

okay that's the whole page bestie, go forth and drop responsibly 🌸✨ this was PostgreSQL 18.6, dated 2026, and it's DROP SEQUENCE(7) — periodt 💖🦋🎀