1. 20 Oct, 2008 1 commit
  2. 04 Sep, 2008 1 commit
  3. 11 Jul, 2008 1 commit
  4. 19 Jun, 2008 1 commit
  5. 16 May, 2008 1 commit
  6. 12 May, 2008 1 commit
    • Alvaro Herrera's avatar
      Restructure some header files a bit, in particular heapam.h, by removing some · f8c4d7db
      Alvaro Herrera authored
      unnecessary #include lines in it.  Also, move some tuple routine prototypes and
      macros to htup.h, which allows removal of heapam.h inclusion from some .c
      files.
      
      For this to work, a new header file access/sysattr.h needed to be created,
      initially containing attribute numbers of system columns, for pg_dump usage.
      
      While at it, make contrib ltree, intarray and hstore header files more
      consistent with our header style.
      f8c4d7db
  7. 22 Apr, 2008 1 commit
    • Teodor Sigaev's avatar
      Fix using too many LWLocks bug, reported by Craig Ringer · cf23b75b
      Teodor Sigaev authored
      <craig@postnewspapers.com.au>.
      It was my mistake, I missed limitation of number of held locks, now GIN doesn't
      use continiuous locks, but still hold buffers pinned to prevent interference
      with vacuum's deletion algorithm.
      
      Backpatch is needed.
      cf23b75b
  8. 14 Apr, 2008 1 commit
    • 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
  9. 13 Apr, 2008 1 commit
    • Tom Lane's avatar
      Phase 2 of project to make index operator lossiness be determined at runtime · 24558da1
      Tom Lane authored
      instead of plan time.  Extend the amgettuple API so that the index AM returns
      a boolean indicating whether the indexquals need to be rechecked, and make
      that rechecking happen in nodeIndexscan.c (currently the only place where
      it's expected to be needed; other callers of index_getnext are just erroring
      out for now).  For the moment, GIN and GIST have stub logic that just always
      sets the recheck flag to TRUE --- I'm hoping to get Teodor to handle pushing
      that control down to the opclass consistent() functions.  The planner no
      longer pays any attention to amopreqcheck, and that catalog column will go
      away in due course.
      24558da1
  10. 10 Apr, 2008 1 commit
    • Tom Lane's avatar
      Replace "amgetmulti" AM functions with "amgetbitmap", in which the whole · 4e82a954
      Tom Lane authored
      indexscan always occurs in one call, and the results are returned in a
      TIDBitmap instead of a limited-size array of TIDs.  This should improve
      speed a little by reducing AM entry/exit overhead, and it is necessary
      infrastructure if we are ever to support bitmap indexes.
      
      In an only slightly related change, add support for TIDBitmaps to preserve
      (somewhat lossily) the knowledge that particular TIDs reported by an index
      need to have their quals rechecked when the heap is visited.  This facility
      is not really used yet; we'll need to extend the forced-recheck feature to
      plain indexscans before it's useful, and that hasn't been coded yet.
      The intent is to use it to clean up 8.3's horrid @@@ kluge for text search
      with weighted queries.  There might be other uses in future, but that one
      alone is sufficient reason.
      
      Heikki Linnakangas, with some adjustments by me.
      4e82a954
  11. 01 Jan, 2008 1 commit
  12. 15 Nov, 2007 1 commit
  13. 04 Jun, 2007 1 commit
    • Teodor Sigaev's avatar
      Fix bundle bugs of GIN: · 853d1c31
      Teodor Sigaev authored
      - Fix possible deadlock between UPDATE and VACUUM queries. Bug never was
        observed in 8.2, but it still exist there. HEAD is more sensitive to
        bug after recent "ring" of buffer improvements.
      - Fix WAL creation: if parent page is stored as is after split then
        incomplete split isn't removed during replay. This happens rather rare, only
        on large tables with a lot of updates/inserts.
      - Fix WAL replay: there was wrong test of XLR_BKP_BLOCK_* for left
        page after deletion of page. That causes wrong rightlink field: it pointed
        to deleted page.
      - add checking of match of clearing incomplete split
      - cleanup incomplete split list after proceeding
      
      All of this chages doesn't change on-disk storage, so backpatch...
      But second point may be an issue for replaying logs from previous version.
      853d1c31
  14. 01 Feb, 2007 1 commit
  15. 31 Jan, 2007 1 commit
  16. 05 Jan, 2007 1 commit
  17. 12 Nov, 2006 1 commit
  18. 04 Oct, 2006 1 commit
  19. 14 Jul, 2006 1 commit
  20. 02 May, 2006 1 commit