PostgreSQL Bugs

Collected from the PG bugs email list.

Bug ID15871
PG Version11.4
OSLinux x86_64 (Alpine 3.9)
Opened2019-06-25 04:49:24+00
Reported byTom Dunstan
StatusNew

Body of first available message related to this bug follows.

The following bug has been logged on the website:

Bug reference:      15871
Logged by:          Tom Dunstan
Email address:      (redacted)
PostgreSQL version: 11.4
Operating system:   Linux x86_64 (Alpine 3.9)
Description:        

This worked up to 11.3:

test=# CREATE TABLE foo (ts1 TIMESTAMP NOT NULL, ts2 TIMESTAMP NOT NULL);
CREATE TABLE
test=# CREATE INDEX foo_ts1_idx ON foo (ts1);
CREATE INDEX
test=# CREATE INDEX foo_ts2_idx ON foo (ts2);
CREATE INDEX
test=# ALTER TABLE FOO ALTER ts1 TYPE TIMESTAMP WITH TIME ZONE, ALTER ts2
TYPE TIMESTAMP WITH TIME ZONE;
ERROR:  42P07: relation "foo_ts1_idx" already exists
LOCATION:  index_create, index.c:877

Necessary condition seems to be:
 - Multiple columns altered in the same statement
 - Both altered columns have an index

Altering in separate statements, or not having one of the indexes doesn't
trigger it.

May be related to this item mentioned in the 11.4 release notes: "Fix
failure of ALTER TABLE ... ALTER COLUMN TYPE when the table has a partial
exclusion constraint (Tom Lane)"

Messages

DateAuthorSubject
2019-06-25 04:49:24+00PG Bug reporting formBUG #15871: Regression in 11.4 altering type on column with an index
2019-06-25 05:03:57+00"David G(dot) Johnston"BUG #15871: Regression in 11.4 altering type on column with an index
2019-06-25 05:25:03+00Tom DunstanRe: BUG #15871: Regression in 11.4 altering type on column with an index