Postgres Pro
Downloads
Home   >   mailing lists

Re: [OT] why not keeping the original column name in catalog after a drop? - Mailing list pgsql-hackers

From Pavan Deolasee
Subject Re: [OT] why not keeping the original column name in catalog after a drop?
Date
Msg-id CABOikdNpDCB_-aPs8-zKzs-k0bmW_f5-Jww0XWFaJQeKvD28Cw@mail.gmail.com
Whole thread Raw
In response to [OT] why not keeping the original column name in catalog after a drop?  (Luca Ferrari <fluca1978@infinito.it>)
List pgsql-hackers
Tree view
On Wed, Nov 13, 2013 at 1:22 PM, Luca Ferrari <fluca1978@infinito.it> wrote:


I'm wondering what is the problem in placing the old/original name
after the "pg.dropped" prefix. I know that the tuple in pg_attribute
is temporary, but what are the possible conflicts the comment talks
about?


May be when a column with the same name is added and again dropped ? Of course, we can have the attribute number and column name both to avoid conflict.

Thanks,
Pavan 

--
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee

pgsql-hackers by date:

Previous
From: Luca Ferrari
Date:
Subject: [OT] why not keeping the original column name in catalog after a drop?
Next
From: Rohit Goyal
Date:
Subject: Re: Information about Access methods