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

pgsql: Fix erroneous parsing of tsquery input "... & !(subexpression)|

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix erroneous parsing of tsquery input "... & !(subexpression)|
Date: 2010-12-19 17:49:17
Message-ID: E1PUNNl-00011E-Tp@gemulon.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Fix erroneous parsing of tsquery input "... & !(subexpression) | ..."

After parsing a parenthesized subexpression, we must pop all pending
ANDs and NOTs off the stack, just like the case for a simple operand.
Per bug #5793.

Also fix clones of this routine in contrib/intarray and contrib/ltree,
where input of types query_int and ltxtquery had the same problem.

Back-patch to all supported versions.

Branch
------
REL8_3_STABLE

Details
-------
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=d9b99b4b60fd0925b9e223ec9f5ea275a8c2dde5

Modified Files
--------------
contrib/intarray/_int_bool.c    |    4 ++--
contrib/ltree/ltxtquery_io.c    |    4 ++--
src/backend/utils/adt/tsquery.c |    4 ++--
3 files changed, 6 insertions(+), 6 deletions(-)

pgsql-committers by date

Next:From: Tom LaneDate: 2010-12-19 20:32:59
Subject: pgsql: Fix up handling of simple-form CASE with constant testexpressio
Previous:From: Magnus HaganderDate: 2010-12-19 15:48:20
Subject: pgsql: Support for collecting crash dumps on Windows

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