From: | Thomas Munro <munro(at)ip9(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: WIP -- renaming implicit sequences |
Date: | 2012-01-14 22:51:54 |
Message-ID: | CADLWmXVPZDpYv2N0c2QHpSNQ9MyFx9ddB0gnfKtE2AdfjNQ95Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12 January 2012 00:58, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Hmm ... this seems a bit inconsistent with the fact that we got rid of
> automatic renaming of indexes a year or three back. Won't renaming of
> serials have all the same problems that caused us to give up on renaming
> indexes?
I was sort of planning to do something similar for constraints (once
the patch to support renaming constraints lands) and indexes (I didn't
know they'd previously been automatically renamed and that had been
dropped).
Would you say that I should abandon this, no chance of being accepted?
Is there a technical problem I'm missing, other than the gap between
unique name generation and execution of the implicit ALTERs?
Maybe I should look into writing a 'tidy rename' procedure for tables
and columns instead, rather than modifying the behaviour of core ALTER
TABLE.
From | Date | Subject | |
---|---|---|---|
Next Message | Joey Adams | 2012-01-14 23:11:57 | Re: JSON for PG 9.2 |
Previous Message | Peter Eisentraut | 2012-01-14 22:18:51 | Re: separate initdb -A options for local and host |