Re: BUG #15865: ALTER TABLE statements causing "relation already exists" errors when some indexes exist

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, keith(dot)fiske(at)crunchydata(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15865: ALTER TABLE statements causing "relation already exists" errors when some indexes exist
Date: 2019-06-21 00:45:54
Message-ID: 20190621004554.GB1626@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-06-21 00:48:33 Re: BUG #15827: Unable to connect on Windows using pg_services.conf using Python psycopg2
Previous Message Michael Paquier 2019-06-21 00:42:33 Re: BUG #15827: Unable to connect on Windows using pg_services.conf using Python psycopg2

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-06-21 01:54:46 Re: BUG #15865: ALTER TABLE statements causing "relation already exists" errors when some indexes exist
Previous Message Tom Lane 2019-06-21 00:20:55 Re: BUG #15865: ALTER TABLE statements causing "relation already exists" errors when some indexes exist