From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
Cc: | "Bruce Momjian" <momjian(at)postgresql(dot)org>, <pgsql-committers(at)postgresql(dot)org> |
Subject: | Re: pgsql: Update: < * Allow adding enumerated values to an existing |
Date: | 2008-04-25 18:52:22 |
Message-ID: | 87iqy5ojh5.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
"Andrew Dunstan" <andrew(at)dunslane(dot)net> writes:
> Where did this come from? Adding values anywhere except on the end of the
> enumeration list will be fraught with danger, as will removing them. In
> essence, either operation would entail rewriting every table that used the
> type. Anything else carries a major risk of corruption. That seems like a
> pretty bad idea.
The TODO doesn't say anything about there not being restrictions. Only being
able to add to the end seems like a likely such restriction.
And removing entries is "only" an engineering problem where you have to go out
and check that there are no records referencing that entry.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-04-25 20:02:04 | Re: Re: [COMMITTERS] pgsql: Update: < * Allow adding enumerated values to an existing |
Previous Message | Brendan Jurd | 2008-04-25 18:40:16 | Re: Re: [COMMITTERS] pgsql: Update: < * Allow adding enumerated values to an existing |
From | Date | Subject | |
---|---|---|---|
Next Message | Brendan Jurd | 2008-04-25 19:08:55 | Re: Proposed patch - psql wraps at window width |
Previous Message | Gregory Stark | 2008-04-25 18:46:46 | Re: Proposed patch - psql wraps at window width |