From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(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 13:37:25 |
Message-ID: | 20150430133725.GB24214@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2015-04-30 13:41:15 | Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API) |
Previous Message | Sergey Grinko | 2015-04-30 13:34:25 | Re: Loss of some parts of the function definition |