Re: BUG #15865: ALTER TABLE statements causing "relation alreadyexists" errors when some indexes exist - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #15865: ALTER TABLE statements causing "relation alreadyexists" errors when some indexes exist
Date
Msg-id 20190621004554.GB1626@paquier.xyz
Whole thread Raw
In response to Re: BUG #15865: ALTER TABLE statements causing "relation already exists" errors when some indexes exist  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Thu, Jun 20, 2019 at 08:20:55PM -0400, Tom Lane wrote:
> This is a pretty embarrassing bug, reinforcing my hindsight view
> that I was firing on very few cylinders last week.  It basically
> means that any ALTER TABLE that tries to alter the type of more than
> one column is going to fail, if any but the last such column has a
> dependent plain (non-constraint) index.  The test cases added by
> e76de8861 were oh so close to noticing that, but not close enough.
>
> I'll go fix it, but do we need to consider a near-term re-release?

Ugh.  That's a possibility.  Changing each ALTER TABLE to be run
individually can be a pain, and we really ought to push for the fix of
the most recent CVE as soon as possible :(
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: BUG #15827: Unable to connect on Windows using pg_services.confusing Python psycopg2
Next
From: Tom Lane
Date:
Subject: Re: BUG #15827: Unable to connect on Windows using pg_services.conf using Python psycopg2