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: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: keith.fiske@crunchydata.com, pgsql-bugs@lists.postgresql.org
Date: 2019-06-20T21:08:29Z
Lists: pgsql-bugs, pgsql-hackers 
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> On 2019-Jun-20, PG Bug reporting form wrote:
>> When testing the setup of our monitoring platform, we started running into
>> an error when using PostgreSQL as a backend for Grafana.

> commit e76de886157b7f974d4d247908b242607cfbf043
> Author:     Tom Lane <tgl@sss.pgh.pa.us>
> AuthorDate: Wed Jun 12 12:29:24 2019 -0400
> CommitDate: Wed Jun 12 12:29:39 2019 -0400
>     Fix ALTER COLUMN TYPE failure with a partial exclusion constraint.

Yeah, obviously I fat-fingered something there.  Looking ...

			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.