Fix two bugs in tsquery @> operator. 1. The comparison for matching terms used only the CRC to decide if there's a match. Two different terms with the same CRC gave a match.
2. It assumed that if the second operand has more terms than the first, it's never a match. That assumption is bogus, because there can be duplicate terms in either operand. Rewrite the implementation in a way that doesn't have those bugs. Backpatch to all supported versions. Branch ------ REL9_0_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/10059c2da7ee2a355e261ed5e56dcec4657e01aa Modified Files -------------- src/backend/utils/adt/tsquery_op.c | 129 +++++++++++++++++++++++++----------- 1 file changed, 89 insertions(+), 40 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
