From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | "pgsql(at)tomd(dot)cc" <pgsql(at)tomd(dot)cc>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | BUG #15871: Regression in 11.4 altering type on column with an index |
Date: | 2019-06-25 05:03:57 |
Message-ID: | CAKFQuwYM+X1guwL9mQwH0U4Z5PXkzyJ9osdpGCgCqNutzy_4Fw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Monday, June 24, 2019, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:
> The following bug has been logged on the website:
>
> Bug reference: 15871
> Logged by: Tom Dunstan
> Email address: pgsql(at)tomd(dot)cc
> PostgreSQL version: 11.4
> Operating system: Linux x86_64 (Alpine 3.9)
> Description:
>
> 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
>
Seems to be the same behavior as BUG #1586 whose fix just got applied today
and will appear in the next point release.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Dunstan | 2019-06-25 05:25:03 | Re: BUG #15871: Regression in 11.4 altering type on column with an index |
Previous Message | PG Bug reporting form | 2019-06-25 04:49:24 | BUG #15871: Regression in 11.4 altering type on column with an index |