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

From Tom Lane
Subject Re: Enum proposal / design
Date
Msg-id 28234.1155759223@sss.pgh.pa.us
Whole thread Raw
In response to Re: Enum proposal / design  (Tom Dunstan <pgsql@tomd.cc>)
Responses Re: Enum proposal / design
List pgsql-hackers
Tom Dunstan <pgsql@tomd.cc> writes:
> I thought the runtime one was kinda cute, actually, but you would have 
> to have duplicate functions for the differently sized types, eg. 
> enum1_out, enum2_out etc since otherwise you wouldn't know what sized 
> parameter you were just handed.

I'm not sure that that matters really.  What you are actually going to
get handed is a Datum that IIRC is right-justified and zero-padded, so
very probably one function would work for all stored widths.  The bigger
issue I think is the surprise factor if a column gets wider over a dump
and reload.
        regards, tom lane


pgsql-hackers by date:

Previous
From: mdean
Date:
Subject: Re: BugTracker (Was: Re: 8.2 features status)
Next
From: Simon Riggs
Date:
Subject: Re: [PATCHES] Forcing current WAL file to be archived