delta/postgresql.git/contrib/rtree_gist/rtree_gist.sql.in, branch master

Remove contrib version of rtree_gist --- now in core system.

2005-07-01T19:23:07+00:00

Extend r-tree operator classes to handle Y-direction tests equivalent

2005-06-24T20:53:34+00:00

to the existing X-direction tests.  An rtree class now includes 4 actual
2-D tests, 4 1-D X-direction tests, and 4 1-D Y-direction tests.
This involved adding four new Y-direction test operators for each of
box and polygon; I followed the PostGIS project's lead as to the names
of these operators.
NON BACKWARDS COMPATIBLE CHANGE: the poly_overleft (&<) and poly_overright
(&>) operators now have semantics comparable to box_overleft and box_overright.
This is necessary to make r-tree indexes work correctly on polygons.
Also, I changed circle_left and circle_right to agree with box_left and
box_right --- formerly they allowed the boundaries to touch.  This isn't
actually essential given the lack of any r-tree opclass for circles, but
it seems best to sync all the definitions while we are at it.

Cleanup vectors of GISTENTRY and eliminate problem with 64-bit strict-aligned

2004-03-30T15:45:33+00:00

boxes. Change interface to user-defined GiST support methods union and
picksplit. Now instead of bytea struct it used special GistEntryVector
structure.

Backend support for autocommit removed, per recent discussions. The

2003-05-14T03:26:03+00:00

only remnant of this failed experiment is that the server will take
SET AUTOCOMMIT TO ON.  Still TODO: provide some client-side autocommit
logic in libpq.

Update /contrib for "autocommit TO 'on'".

2002-10-18T18:41:22+00:00

Create objects in public schema.

Make spacing/capitalization consistent.

Remove transaction block use for object creation.

Remove unneeded function GRANTs.

Add a bunch of pseudo-types to replace the behavior formerly associated

2002-08-22T00:01:51+00:00

with OPAQUE, as per recent pghackers discussion.  I still want to do some
more work on the 'cstring' pseudo-type, but I'm going to commit the bulk
of the changes now before the tree starts shifting under me ...

Replace ad-hoc insertions into pg_opclass and friends with CREATE

2002-07-30T17:34:37+00:00

OPERATOR CLASS commands.  Further tweaking of documentation for same.

Opclasses live in namespaces. I also took the opportunity to create

2002-04-17T20:57:57+00:00

an 'opclass owner' column in pg_opclass.  Nothing is done with it at
present, but since there are plans to invent a CREATE OPERATOR CLASS
command soon, we'll probably want DROP OPERATOR CLASS too, which
suggests that a notion of ownership would be a good idea.

Update GiST for new pg_opclass arrangement (finally a clean solution

2001-08-22T18:24:26+00:00

for haskeytype).  Update GiST contrib modules too.  Add linear-time split
algorithm for R-tree GiST opclass.
From Oleg Bartunov and Teodor Sigaev.

Restructure pg_opclass, pg_amop, and pg_amproc per previous discussions in

2001-08-21T16:36:06+00:00

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.