Re: Precedence of NOT LIKE, NOT BETWEEN, etc

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Precedence of NOT LIKE, NOT BETWEEN, etc
Date: 2015-04-30 15:02:27
Message-ID: 36183.1430406147@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Wed, Apr 8, 2015 at 01:14:38PM -0400, Tom Lane wrote:
>> Greg Stark <stark(at)mit(dot)edu> writes:
>>> On Tue, Feb 24, 2015 at 5:04 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>>> Also, it strikes me that we could significantly reduce, maybe even fully
>>>> eliminate, the funny behaviors around the existing base_yylex()
>>>> substitutions if we made them use the same idea, ie replace the leading
>>>> token with something special but keep the second token's separate
>>>> identity. Unless somebody sees a hole in this idea, I'll probably go
>>>> do that and then come back to the precedence issues.

>>> IIRC that's exactly what the earlier patch for this did.

>> Right, see d809fd0008a2e26de463f47b7aba0365264078f3

> Where are we on this?

It's done as far as seemed reasonable to push it.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-04-30 15:02:55 Re: Use outerPlanState() consistently in executor code
Previous Message Bruce Momjian 2015-04-30 15:01:01 Re: collations in shared catalogs?