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

pgsql: Remove bogus entries in gist point_ops operator class.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Remove bogus entries in gist point_ops operator class.
Date: 2011-12-17 23:51:30
Message-ID: E1Rc42M-0005dw-5F@gemulon.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Remove bogus entries in gist point_ops operator class.

These entries could never be matched to an index clause because they don't
have the index datatype on the left-hand side of the operator.  (Their
commutators are in the opclass, which is sensible, but that doesn't mean
these operators should be.)  Spotted by a test that I recently added to
opr_sanity to catch exactly this type of thinko.  AFAICT there is no code
in gistproc.c that is specifically meant to cover these cases, so nothing
to remove at that level.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/5577ca5bfb33bf7f31a03fc5b42a56de400e464e

Modified Files
--------------
src/include/catalog/catversion.h         |    2 +-
src/include/catalog/pg_amop.h            |    3 ---
src/test/regress/expected/opr_sanity.out |   10 ++--------
3 files changed, 3 insertions(+), 12 deletions(-)

pgsql-committers by date

Next:From: Tom LaneDate: 2011-12-18 00:08:37
Subject: pgsql: Defend against null scankeys in spgist searches.
Previous:From: Tom LaneDate: 2011-12-17 23:27:35
Subject: pgsql: Fix some long-obsolete references to XLogOpenRelation.

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