| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Brendan Jurd" <direvus(at)gmail(dot)com> |
| Cc: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Bruce Momjian" <momjian(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: [COMMITTERS] pgsql: Update: < * Allow adding enumerated values to an existing |
| Date: | 2008-04-25 20:02:04 |
| Message-ID: | 27146.1209153724@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
"Brendan Jurd" <direvus(at)gmail(dot)com> writes:
> Has anyone had a close look at how hard it would be allow just the
> "add to the end" capability?
The problem is you can't guarantee anything about the ordering of the
new value relative to the old ones. The OID it's assigned might be
after them, or before them if the OID counter has wrapped around,
or (with much smaller probability) between two existing ones.
This is something we consciously gave up when we selected the current
ENUM implementation.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brendan Jurd | 2008-04-25 20:10:58 | Re: Re: [COMMITTERS] pgsql: Update: < * Allow adding enumerated values to an existing |
| Previous Message | Gregory Stark | 2008-04-25 18:52:22 | Re: pgsql: Update: < * Allow adding enumerated values to an existing |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brendan Jurd | 2008-04-25 20:10:58 | Re: Re: [COMMITTERS] pgsql: Update: < * Allow adding enumerated values to an existing |
| Previous Message | Alvaro Herrera | 2008-04-25 20:01:15 | Re: Proposed patch - psql wraps at window width |