Adrian,
The drop policy IF EXISTS does work.
But it would be nice to have the IF NOT EXISTS on CREATE POLICY so I don't need to do a drop and create.
From: Adrian Klaver <adrian.klaver@aklaver.com>
Sent: October 20, 2025 14:51
To: Paul Austin <paul.austin@automutatio.com>; pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Subject: Re: Extend CREATE POLICY to add IF EXISTS
On 10/20/25 14:49, Paul Austin wrote:
> I forgot DROP POLICY already has IF EXISTS
I take it that works for you?
>
> *From:*Paul Austin <paul.austin@automutatio.com>
> *Sent:* October 20, 2025 2:46 PM
> *To:* pgsql-general@lists.postgresql.org
> *Subject:* Extend CREATE POLICY to add IF EXISTS
>
> Many (but not all) DDL statements use the pattern IF EXISTS or IF NOT
> EXISTS. This is really useful if you want to create a re-start-able data
> model update script without needing to have PL/pgSQL blocks that has
> checks to see if it exists.
>
> An example of a statement that doesn’t implement this pattern in the
> CREATE POLICY statement.
>
> Is there a plan to add this pattern to the rest of the DDL statements?
> Or could it be added to the CREATE/DROP POLICY statements?
>
> Thanks,
>
> Paul
>
--
Adrian Klaver
adrian.klaver@aklaver.com
