From f933766ba7c5446a28d714904ae0c46d8b21b86a Mon Sep 17 00:00:00 2001
From: Tom Lane
Date: Tue, 21 Aug 2001 16:36:06 +0000
Subject: Restructure pg_opclass, pg_amop, and pg_amproc per previous
 discussions in pgsql-hackers.  pg_opclass now has a row for each opclass
 supported by each index AM, not a row for each opclass name.  This allows
 pg_opclass to show directly whether an AM supports an opclass, and
 furthermore makes it possible to store additional information about an
 opclass that might be AM-dependent. pg_opclass and pg_amop now store "lossy"
 and "haskeytype" information that we previously expected the user to remember
 to provide in CREATE INDEX commands. Lossiness is no longer an index-level
 property, but is associated with the use of a particular operator in a
 particular index opclass.

Along the way, IndexSupportInitialize now uses the syscaches to retrieve
pg_amop and pg_amproc entries.  I find this reduces backend launch time by
about ten percent, at the cost of a couple more special cases in catcache.c's
IndexScanOK.

Initial work by Oleg Bartunov and Teodor Sigaev, further hacking by Tom Lane.

initdb forced.
---
 contrib/rtree_gist/sql/rtree_gist.sql | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'contrib/rtree_gist/sql')

diff --git a/contrib/rtree_gist/sql/rtree_gist.sql b/contrib/rtree_gist/sql/rtree_gist.sql
index a0506213227..592d4c3e78b 100644
--- a/contrib/rtree_gist/sql/rtree_gist.sql
+++ b/contrib/rtree_gist/sql/rtree_gist.sql
@@ -32,7 +32,7 @@ select count(*) from polytmp where p && '(1000,1000),(0,0)'::polygon;
 
 drop index pix;
 
-create index pix on polytmp using gist (p gist_poly_ops) with(islossy);
+create index pix on polytmp using gist (p gist_poly_ops);
 
 select count(*) from polytmp where p && '(1000,1000),(0,0)'::polygon;
 
-- 
cgit v1.2.3