Horton

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

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Keith Fiske <keith.fiske@crunchydata.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, pgsql-bugs@lists.postgresql.org
Date: 2019-06-21T17:27:47Z
Lists: pgsql-bugs, pgsql-hackers 
Keith Fiske <keith.fiske@crunchydata.com> writes:
> On Fri, Jun 21, 2019 at 12:12 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> As before, I attach a patch against HEAD, plus one that assumes e76de8861
>> has been reverted first, which is likely easier to review.

> Tested applying the patch against HEAD this time. Combined ALTER TABLE
> again works without issue.

Again, thanks for testing!

			regards, tom lane

Commits

  1. Simplify psql \d's rule for ordering the indexes of a table.

  2. Purely-cosmetic adjustments in tablecmds.c.

  3. Further fix ALTER COLUMN TYPE's handling of indexes and index constraints.

  4. Fix ALTER COLUMN TYPE failure with a partial exclusion constraint.