Re: Transforming IN (...) to ORs, volatility

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Transforming IN (...) to ORs, volatility
Date: 2011-09-06 17:58:15
Message-ID: 201109061758.p86HwFk18565@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Heikki Linnakangas wrote:
> On 06.09.2011 20:53, Bruce Momjian wrote:
> > Tom Lane wrote:
> >> Bruce Momjian<bruce(at)momjian(dot)us> writes:
> >>> Uh, have we addressed this? I don't think so.
> >>
> >> No. IIRC, I didn't like Heikki's proposed patch, so it's on my head
> >> to come up with something better.
> >
> > You can blame me for getting it into the parser. It used to be in
> > gram.y!
>
> Huh? Isn't "the parser" and "gram.y" more or less the same thing?
> Anyway, it needs to be somewhere else..

I meant the '/parser' directory. It actually created AND nodes in gram.y
so the rest of the parser didn't even know a BETWEEN was used.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andreas Joseph Krogh 2011-09-06 18:21:06 Re: WIP: SP-GiST, Space-Partitioned GiST
Previous Message Heikki Linnakangas 2011-09-06 17:54:29 Re: Transforming IN (...) to ORs, volatility