Re: Re: Abbreviated keys for Datum tuplesort - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: Re: Abbreviated keys for Datum tuplesort
Date
Msg-id 20150403121718.GD3663@tamriel.snowman.net
Whole thread Raw
In response to Re: Re: Abbreviated keys for Datum tuplesort  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Re: Abbreviated keys for Datum tuplesort
List pgsql-hackers
* Robert Haas (robertmhaas@gmail.com) wrote:
> I'm about as much
> of a stickler for the details as you will find on this mailing list,
> or possibly, in the observable universe,

This made me laugh. :)

> but even I'm not willing to
> expend the amount of ink and emotional energy you have on whether a
> variable that holds +1, 0, or -1 ought to be declared as "int" or
> "int32".  Does it matter?  Yeah.  Is it worth this much argument?  No.

My only comment will be on this very minor aspect (and I'm quite
agnostic as to what is decided, particularly as I haven't read the patch
at all), but, should we consider an enum (generically) for such cases?
If that's truly the extent of possible values, and anything else is an
error, then at least if I was writing DDL to support this, I'd use an
enum, maybe a domain, or a CHECK constraint (though I'd likely feel
better about the enum or domain approach).
Thanks!
    Stephen

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Re: Abbreviated keys for Datum tuplesort
Next
From: Peter Geoghegan
Date:
Subject: Re: Re: Abbreviated keys for Datum tuplesort