Re: Enum proposal / design
| От | Tom Dunstan |
|---|---|
| Тема | Re: Enum proposal / design |
| Дата | |
| Msg-id | 44e3d0fc.26.5029.8318@internode.on.net обсуждение исходный текст |
| Ответ на | Enum proposal / design (Tom Dunstan <pgsql@tomd.cc>) |
| Список | pgsql-hackers |
Tom Lane <tgl@sss.pgh.pa.us> writes: > If you're gonna fix it at 4 bytes, then I strongly suggest > that the value identifiers actually be OIDs assigned > through the standard OID-generating mechanism, and that > the pg_enum table have the structure ... > The advantage of doing this is that you can use the > existing, well debugged, normally-quite-fast mechanisms > for generating new unique value identifiers. Rather than > consing up your own slow full-table-scan mechanism as > envisioned in the original proposal. Yeah, I was never all that happy with that anyway, and figured for the unique value thingy that we could either use oids or set up a new sequence, but oids sounded like significantly less work. Cheers Tom
В списке pgsql-hackers по дате отправления: