Re: Enum proposal / design - Mailing list pgsql-hackers

From Tom Dunstan
Subject Re: Enum proposal / design
Date
Msg-id 44e3d0fc.26.5029.8318@internode.on.net
Whole thread Raw
In response to Enum proposal / design  (Tom Dunstan <pgsql@tomd.cc>)
List 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 by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [PATCHES] Adjust autovacuum naptime automatically
Next
From: "Tom Dunstan"
Date:
Subject: Re: Enum proposal / design