Re: Re: [COMMITTERS] pgsql: Update: < * Allow adding enumerated values to an existing

Поиск
Список
Период
Сортировка
От Brendan Jurd
Тема Re: Re: [COMMITTERS] pgsql: Update: < * Allow adding enumerated values to an existing
Дата
Msg-id 37ed240d0804251310qff5cc2dy31e425fd7721547c@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Re: [COMMITTERS] pgsql: Update: < * Allow adding enumerated values to an existing  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Re: [COMMITTERS] pgsql: Update: < * Allow adding enumerated values to an existing  (Alvaro Herrera <alvherre@commandprompt.com>)
Список pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, Apr 26, 2008 at 6:02 AM, Tom Lane  wrote:
> "Brendan Jurd"  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.
>

I see.  So to add a value on to the end with guaranteed ordering, you
would have to rebuild the enum from scratch anyway.

Then there's no technical difference at all in implementing "add to
the end" and "add/remove".

Thanks for the answer.

Cheers,
BJ
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: http://getfiregpg.org

iD8DBQFIEjrO5YBsbHkuyV0RAogmAKC3u8wogvrUNSfFUx/PbKyS6U2/DgCgjDSu
z+VNazq7LiRdiU4oUvKL0jc=
=obXq
-----END PGP SIGNATURE-----


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Re: [COMMITTERS] pgsql: Update: < * Allow adding enumerated values to an existing
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Proposed patch - psql wraps at window width