Skip site navigation (1) Skip section navigation (2)

Re: Between Node

From: Rod Taylor <rbt(at)zort(dot)ca>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>,Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Between Node
Date: 2002-07-18 20:29:02
Message-ID: 1027024143.280.135.camel@jester (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
On Thu, 2002-07-18 at 09:39, Tom Lane wrote:
> Rod Taylor <rbt(at)zort(dot)ca> writes:
> > On Thu, 2002-07-18 at 00:56, Christopher Kings-Lynne wrote:
> >> I believe Tom mentioned that having BETWEEN as a node would allow him to do
> >> some sort of funky optimiser improvement.  Is that already done or does he
> >> still need to do it?
> > I don't know what improvement this would be.  I only touched the parser
> > and executor.
> In that case, this code is worse than before as far as developing plans
> goes.  The selectivity estimator needs to be taught about what BETWEEN
> means.  Currently it recognizes (x > foo AND x < bar) as a range query
> --- a BETWEEN node is obviously much easier to recognize, but you still
> have to add code to do it.
> 			regards, tom lane

In response to

pgsql-patches by date

Next:From: Rod TaylorDate: 2002-07-18 20:30:27
Subject: Re: Between Node
Previous:From: Bruce MomjianDate: 2002-07-18 20:24:17
Subject: Re: [HACKERS] [PATCH] Win32 native fixes after SSL updates (+more)

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group