Re: WIP -- renaming implicit sequences - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: WIP -- renaming implicit sequences
Date
Msg-id CADLWmXVPZDpYv2N0c2QHpSNQ9MyFx9ddB0gnfKtE2AdfjNQ95Q@mail.gmail.com
Whole thread Raw
In response to Re: WIP -- renaming implicit sequences  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: WIP -- renaming implicit sequences  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 12 January 2012 00:58, Tom Lane <tgl@sss.pgh.pa.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
thanthe 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.


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: separate initdb -A options for local and host
Next
From: Joey Adams
Date:
Subject: Re: JSON for PG 9.2