summaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistproc.c
Commit message (Collapse)AuthorAgeFilesLines
...
* pgindent run for 9.0Bruce Momjian2010-02-261-32/+32
|
* Add point_ops opclass for GiST.Teodor Sigaev2010-01-141-3/+171
|
* Update copyright for the year 2010.Bruce Momjian2010-01-021-2/+2
|
* Fix incorrect arguments for gist_box_penalty call. The bug could be observedTeodor Sigaev2009-09-181-3/+3
| | | | | | only for secondary page split (i.e. for non-first columns of index) Patch by Paul Ramsey <pramsey@opengeo.org>
* 8.4 pgindent run, with new combined Linux/FreeBSD/MinGW typedef listBruce Momjian2009-06-111-7/+10
| | | | provided by Andrew.
* Fix 'all at one page bug' in picksplit method of R-tree emulation. Add defenseTeodor Sigaev2009-04-061-41/+80
| | | | from buggy user-defined picksplit to GiST.
* Update copyright for 2009.Bruce Momjian2009-01-011-2/+2
|
* Push index operator lossiness determination down to GIST/GIN opclassTom Lane2008-04-141-3/+18
| | | | | | | | | | | "consistent" functions, and remove pg_amop.opreqcheck, as per recent discussion. The main immediate benefit of this is that we no longer need 8.3's ugly hack of requiring @@@ rather than @@ to test weight-using tsquery searches on GIN indexes. In future it should be possible to optimize some other queries better than is done now, by detecting at runtime whether the index match is exact or not. Tom Lane, after an idea of Heikki's, and with some help from Teodor.
* Update copyrights in source tree to 2008.Bruce Momjian2008-01-011-2/+2
|
* pgindent run for 8.3.Bruce Momjian2007-11-151-12/+14
|
* Improve page split in rtree emulation. Now if splitted result hasTeodor Sigaev2007-09-071-45/+34
| | | | | | | | | big misalignement, then it tries to split page basing on distribution of boxe's centers. Per report from Dolafi, Tom <dolafit@janelia.hhmi.org> Backpatch is needed, change doesn't affect on-disk storage.
* Update CVS HEAD for 2007 copyright. Back branches are typically notBruce Momjian2007-01-051-2/+2
| | | | back-stamped for this.
* pgindent run for 8.2.Bruce Momjian2006-10-041-52/+65
|
* Rename contains/contained-by operators to @> and <@, per discussion thatTom Lane2006-09-101-1/+5
| | | | | | | | agreed these symbols are less easily confused. I made new pg_operator entries (with new OIDs) for the old names, so as to provide backward compatibility while making it pretty easy to remove the old names in some future release cycle. This commit only touches the core datatypes, contrib will be fixed separately.
* Remove 576 references of include files that were not needed.Bruce Momjian2006-07-141-2/+1
|
* ChangesTeodor Sigaev2006-06-281-38/+101
| | | | | | | | | | | | | | | | | | | | * new split algorithm (as proposed in http://archives.postgresql.org/pgsql-hackers/2006-06/msg00254.php) * possible call pickSplit() for second and below columns * add spl_(l|r)datum_exists to GIST_SPLITVEC - pickSplit should check its values to use already defined spl_(l|r)datum for splitting. pickSplit should set spl_(l|r)datum_exists to 'false' (if they was 'true') to signal to caller about using spl_(l|r)datum. * support for old pickSplit(): not very optimal but correct split * remove 'bytes' field from GISTENTRY: in any case size of value is defined by it's type. * split GIST_SPLITVEC to two structures: one for using in picksplit and second - for internal use. * some code refactoring * support of subsplit to rtree opclasses TODO: add support of subsplit to contrib modules
* Update copyright for 2006. Update scripts.Bruce Momjian2006-03-051-2/+2
|
* R-tree is dead ... long live GiST.Tom Lane2005-11-071-4/+43
|
* Standard pgindent run for 8.1.Bruce Momjian2005-10-151-2/+2
|
* pgindent new GIST index code, per request from Tom.Bruce Momjian2005-09-221-36/+36
|
* Migrate rtree_gist functionality into the core system, and add someTom Lane2005-07-011-0/+708
basic regression tests for GiST to the standard regression tests. I took the opportunity to add an rtree-equivalent gist opclass for circles; the contrib version only covered boxes and polygons, but indexing circles is very handy for distance searches.