DROP_POLICY(7pg17)

💅 DROP POLICY 💅

okay so this is the DROP POLICY(7) page from the PostgreSQL 17.11 docs, and it's literally the “bye bye, row-level security policy” page. Pull up a chair, bestie 🫶

---

🌸 NAME 🌸

DROP_POLICY — remove a row-level security policy from a table.

✨ SYNOPSIS ✨

DROP POLICY [ IF EXISTS ] name ON table_name [ CASCADE | RESTRICT ]

🦋 DESCRIPTION 🦋

DROP POLICY removes the specified policy from the table. Periodt.

Important vibe check: if you remove the last policy for a table and that table still has row-level security enabled via ALTER TABLE, then the default-deny policy will be used. No cap — default-deny is the main character then. 😭

If you want to turn row-level security off for a table, ALTER TABLE ... DISABLE ROW LEVEL SECURITY can be used — whether policies for the table exist or not. Slay.

🎀 PARAMETERS 🎀

• IF EXISTS — do not throw an error if the policy does not exist. A notice is issued in this case, so you get a lil heads-up instead of a whole crash-out.
• name — the name of the policy to drop.
• table_name — the name (optionally schema-qualified) of the table that the policy is on.
• CASCADE, RESTRICT — these key words do not have any effect, since there are no dependencies on policies. They're just there, being iconic and doing absolutely nothing. 💅

🍓 EXAMPLES 🍓

To drop the policy called p1 on the table named my_table:

DROP POLICY p1 ON my_table;

🌈 COMPATIBILITY 🌈

DROP POLICY is a PostgreSQL extension.

👑 SEE ALSO 👑

• CREATE POLICY (CREATE_POLICY(7))
• ALTER POLICY (ALTER_POLICY(7))

---

mwah 💖 this page is from PostgreSQL 17.11, dated 2026, and it's the DROP POLICY(7) manual page. bye bestie, go drop those policies responsibly 🫶✨