Re: Cause of intermittent rangetypes regression test failures

From: "Erik Rijkers" <er(at)xs4all(dot)nl>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Jeff Davis" <pgsql(at)j-davis(dot)com>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Cause of intermittent rangetypes regression test failures
Date: 2011-11-14 18:54:57
Message-ID: e1b5e16ececf727967d38842df0e011c.squirrel@webmail.xs4all.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, November 14, 2011 19:43, Tom Lane wrote:
> Jeff Davis <pgsql(at)j-davis(dot)com> writes:
>> On Mon, 2011-11-14 at 08:11 -0500, Tom Lane wrote:
>
> While thinking about this ... would it be sensible for range_lower and
> range_upper to return NULL instead of throwing an exception for empty or
> infinite ranges? As with these comparison functions, throwing an error
> seems like a fairly unpleasant definition to work with in practice.
>

+1

much better, IMHO.

Erik Rijkers

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2011-11-14 18:56:15 Re: So where are we on the open commitfest?
Previous Message Tom Lane 2011-11-14 18:43:20 Re: Cause of intermittent rangetypes regression test failures