From: | Luca Ferrari <fluca1978(at)infinito(dot)it> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [OT] why not keeping the original column name in catalog after a drop? |
Date: | 2013-11-13 11:17:58 |
Message-ID: | CAKoxK+7FdDJoFc6PybkwuxMFirt7yY0iGWZdtP9cii4acsPZuQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Nov 13, 2013 at 9:00 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> The old name might not fit there, attribute names have a relatively low
> maximum length (64 by default), so we cannot always fit the entire old
> name there.
Thanks, I was guessing this.
>
> Also, think about:
> CREATE TABLE foo(cola int);
> ALTER TABLE foo DROP COLUMN cola;
> ALTER TABLE foo ADD COLUMN cola;
> ALTER TABLE foo DROP COLUMN cola; -- should not error out
Well, I was talking about appending the original column name, and
therefore the above should have been respectively pg.dropped.1.cola.
and pg.dropped.2.cola. Of course the original name is not very much
interesting, I was just curios about the conflicts.
Luca
From | Date | Subject | |
---|---|---|---|
Next Message | Sawada Masahiko | 2013-11-13 11:18:53 | The number of character limitation of custom script on pgbench |
Previous Message | Heikki Linnakangas | 2013-11-13 11:15:32 | Re: init_sequence spill to hash table |