Horton

Re: Range Types - typo + NULL string constructor

Jeff Davis <pgsql@j-davis.com>

View thread
From: Jeff Davis <pgsql@j-davis.com>
To: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: Alexander Korotkov <aekorotkov@gmail.com>, pgsql-hackers@postgresql.org
Date: 2011-11-03T08:46:09Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Replace the "New Linear" GiST split algorithm for boxes and points with a

On Thu, 2011-11-03 at 10:37 +0200, Heikki Linnakangas wrote:
> Looking at the most recent patch, I don't actually see any GiST support 
> for the empty and non-empty operators (!? and ?). I don't see how those 
> could be accelerated with GiST, anyway; I think if you want to use an 
> index for those operators, you might as well create a partial or 
> functional index on empty(x).
> 
> So I'm actually inclined to remove not only the nonempty function, but 
> also the ? and !? operators. They don't seem very useful, and ? and !? 
> don't feel very intuitive to me, anyway. I'll just leave the empty(x) 
> function.

That's fine with me. At best, they were only marginally useful.

Regards,
	Jeff Davis