| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | gianni(dot)ciolli(at)2ndquadrant(dot)it |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #12752: Regression in ALTER TABLE RENAME COLUMN |
| Date: | 2015-02-09 17:49:38 |
| Message-ID: | 28749.1423504178@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
gianni(dot)ciolli(at)2ndquadrant(dot)it writes:
> It appears that the bug discussed here has regressed since 9.1:
> http://www.postgresql.org/message-id/200110121753.f9CHrnl10542@candle.pha.pa.us
We gave up trying to make index column names match the underlying table in
9.0; so no currently supported PG release does what you wish, and it's
unlikely that any future one will either. (This is called out as an
incompatibility in the 9.0 release notes, FWIW.)
> Context information: the bug breaks Londiste, which uses
> pg_attribute.attname to match columns on the primary key index with the
> corrisponding columns on the table.
> I found the bug after a customer reported Londiste issues on a table whose
> primary key had been renamed.
Sorry, but that's a Londiste bug not a Postgres bug.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-02-09 17:57:12 | Re: BUG #12752: Regression in ALTER TABLE RENAME COLUMN |
| Previous Message | Gianni Ciolli | 2015-02-09 16:31:43 | BUG #12752: example SQL |