1. 16 Nov, 2007 1 commit
    • Tom Lane's avatar
      Improve GIN index build's tracking of memory usage by using · 6f4cfe48
      Tom Lane authored
      GetMemoryChunkSpace, not just the palloc request size.  This brings the
      allocatedMemory counter close enough to reality (as measured by
      MemoryContextStats printouts) that I think we can get rid of the arbitrary
      factor-of-2 adjustment that was put into the code initially.  Given the
      sensitivity of GIN build to work memory size, not using as much of work
      memory as we're allowed to seems a pretty bad idea.
      6f4cfe48
  2. 05 Jun, 2007 1 commit
  3. 01 Feb, 2007 1 commit
  4. 31 Jan, 2007 1 commit
  5. 05 Jan, 2007 1 commit
  6. 04 Oct, 2006 1 commit
  7. 14 Jul, 2006 1 commit
  8. 11 Jul, 2006 1 commit
    • Teodor Sigaev's avatar
      GIN improvements · 23416364
      Teodor Sigaev authored
      - Replace sorted array of entries in maintenance_work_mem to binary tree,
        this should improve create performance.
      - More precisely calculate allocated memory, eliminate leaks
        with user-defined extractValue()
      - Improve wordings in tsearch2
      23416364
  9. 10 May, 2006 1 commit
    • Tom Lane's avatar
      Clean up code associated with updating pg_class statistics columns · 3fdeb189
      Tom Lane authored
      (relpages/reltuples).  To do this, create formal support in heapam.c for
      "overwrite" tuple updates (including xlog replay capability) and use that
      instead of the ad-hoc overwrites we'd been using in VACUUM and CREATE INDEX.
      Take the responsibility for updating stats during CREATE INDEX out of the
      individual index AMs, and do it where it belongs, in catalog/index.c.  Aside
      from being more modular, this avoids having to update the same tuple twice in
      some paths through CREATE INDEX.  It's probably not measurably faster, but
      for sure it's a lot cleaner than before.
      3fdeb189
  10. 02 May, 2006 1 commit