From: Tom Lane <tgl@sss.pgh.pa.us>
To: david@buildingfootprintusa.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18217: ALTER TABLE IF EXISTS not being honored with DROP
 CONSTRAINT IF EXISTS
In-reply-to: <18217-c7180ab143091145@postgresql.org>
References: <18217-c7180ab143091145@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Wed, 29 Nov 2023 14:59:59 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <306768.1701274440.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 29 Nov 2023 11:14:00 -0500
Message-ID: <306769.1701274440@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/306769.1701274440%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> I found this issue from running pg_restore with flags to clean and "if =

> exists".  pg_restore returns an error code which is generated from a que=
ry
> of the following form:

> ALTER TABLE IF EXISTS ONLY public.foo DROP CONSTRAINT IF EXISTS foo_pkey

This works for me in the current minor release (15.5):

$ psql
psql (15.5)
Type "help" for help.

postgres=3D# ALTER TABLE IF EXISTS ONLY public.foo DROP CONSTRAINT IF EXIS=
TS foo_pkey;
NOTICE:  relation "foo" does not exist, skipping
ALTER TABLE

Please update.  If you can still reproduce the problem in the
current release, there must be some additional contributing
factor -- please try to provide a self-contained test case.

			regards, tom lane