| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Alexander Korotkov <aekorotkov(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Range Types - typo + NULL string constructor |
| Date: | 2011-11-03 08:46:09 |
| Message-ID: | 1320309969.32341.30.camel@jdavis |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2011-11-03 08:55:11 | Re: Re: [COMMITTERS] pgsql: Reduce checkpoints and WAL traffic on low activity database serv |
| Previous Message | Jeff Davis | 2011-11-03 08:42:29 | Re: GiST for range types (was Re: Range Types - typo + NULL string constructor) |