Skip to content
Snippets Groups Projects
  1. Apr 10, 2011
  2. Jan 01, 2011
  3. Dec 04, 2010
    • Tom Lane's avatar
      KNNGIST, otherwise known as order-by-operator support for GIST. · 55450687
      Tom Lane authored
      This commit represents a rather heavily editorialized version of
      Teodor's builtin_knngist_itself-0.8.2 and builtin_knngist_proc-0.8.1
      patches.  I redid the opclass API to add a separate Distance method
      instead of turning the Consistent method into an illogical mess,
      fixed some bit-rot in the rbtree interfaces, and generally worked over
      the code style and comments.
      
      There's still no non-code documentation to speak of, but I'll work on
      that separately.  Some contrib-module changes are also yet to come
      (right now, point <-> point is the only KNN-ified operator).
      
      Teodor Sigaev and Tom Lane
      55450687
  4. Nov 15, 2010
  5. Sep 20, 2010
  6. Feb 26, 2010
  7. Jan 14, 2010
  8. Jan 02, 2010
  9. Sep 18, 2009
  10. Jun 11, 2009
  11. Apr 06, 2009
  12. Jan 01, 2009
  13. Apr 14, 2008
    • Tom Lane's avatar
      Push index operator lossiness determination down to GIST/GIN opclass · 9b5c8d45
      Tom Lane authored
      "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.
      9b5c8d45
  14. Jan 01, 2008
  15. Nov 15, 2007
  16. Sep 07, 2007
  17. Jan 05, 2007
  18. Oct 04, 2006
  19. Sep 10, 2006
    • Tom Lane's avatar
      Rename contains/contained-by operators to @> and <@, per discussion that · ba920e1c
      Tom Lane authored
      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.
      ba920e1c
  20. Jul 14, 2006
  21. Jun 28, 2006
    • Teodor Sigaev's avatar
      Changes · 1f7ef548
      Teodor Sigaev authored
      * 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
      1f7ef548
  22. Mar 05, 2006
  23. Nov 07, 2005
  24. Oct 15, 2005
  25. Sep 22, 2005
  26. Jul 01, 2005
  27. Jun 24, 2005
    • Tom Lane's avatar
      Extend r-tree operator classes to handle Y-direction tests equivalent · b90f8f20
      Tom Lane authored
      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.
      b90f8f20
    • Tom Lane's avatar
      Fix rtree and contrib/rtree_gist search behavior for the 1-D box and · 9a09248e
      Tom Lane authored
      polygon operators (<<, &<, >>, &>).  Per ideas originally put forward
      by andrew@supernews and later rediscovered by moi.  This patch just
      fixes the existing opclasses, and does not add any new behavior as I
      proposed earlier; that can be sorted out later.  In principle this
      could be back-patched, since it changes only search behavior and not
      system catalog entries nor rtree index contents.  I'm not currently
      planning to do that, though, since I think it could use more testing.
      9a09248e
  28. May 25, 2005
  29. May 21, 2005
  30. Aug 29, 2004
  31. Mar 30, 2004
  32. Nov 29, 2003
    • PostgreSQL Daemon's avatar
      · 969685ad
      PostgreSQL Daemon authored
      $Header: -> $PostgreSQL Changes ...
      969685ad
  33. Jul 27, 2003
  34. Sep 04, 2002
  35. May 28, 2002
  36. Oct 25, 2001
  37. Oct 01, 2001
  38. Aug 22, 2001
  39. May 31, 2001
Loading