Thread: pgsql: Fix core dump in QTNodeCompare when tsquery_cmp() is applied to
pgsql: Fix core dump in QTNodeCompare when tsquery_cmp() is applied to
From
tgl@postgresql.org (Tom Lane)
Date:
Log Message:
-----------
Fix core dump in QTNodeCompare when tsquery_cmp() is applied to two empty
tsqueries. CompareTSQ has to have a guard for the case rather than blindly
applying QTNodeCompare to random data past the end of the datums. Also,
change QTNodeCompare to be a little less trusting: use an actual test rather
than just Assert'ing that the input is sane. Problem encountered while
investigating another issue (I saw a core dump in autoanalyze on a table
containing multiple empty tsquery values).
Back-patch to all branches with tsquery support.
In HEAD, also fix some bizarre (though not outright wrong) coding in
tsq_mcontains().
Tags:
----
REL8_4_STABLE
Modified Files:
--------------
pgsql/src/backend/utils/adt:
tsquery_op.c (r1.6 -> r1.6.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/tsquery_op.c?r1=1.6&r2=1.6.2.1)
tsquery_util.c (r1.11 -> r1.11.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/tsquery_util.c?r1=1.11&r2=1.11.2.1)