Re: Macros for typtype (was Re: Arrays of Complex Types)

Tom Lane wrote:
> It seems clear to me that this authorizes, but *does not require*,
> the compiler to store an enum field in a byte or short instead of
> an int when all the declared values will fit.  So if we tried to
> do this, we'd have the problem of needing compiler-specific data
> type information entered in pg_type.

FWIW, I never meant to suggest using enums tuple structures.  I did, 
however, stumble over a case that appears to be handled similar to what 
I had in mind: see enum CoercionCodes in primnodes.h.  Again, it's not 
really important, but it's interesting to see that there is precedent.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/