1. 23 Feb, 2010 1 commit
  2. 08 Feb, 2010 1 commit
    • Tom Lane's avatar
      Remove old-style VACUUM FULL (which was known for a little while as · 0a469c87
      Tom Lane authored
      VACUUM FULL INPLACE), along with a boatload of subsidiary code and complexity.
      Per discussion, the use case for this method of vacuuming is no longer large
      enough to justify maintaining it; not to mention that we don't wish to invest
      the work that would be needed to make it play nicely with Hot Standby.
      
      Aside from the code directly related to old-style VACUUM FULL, this commit
      removes support for certain WAL record types that could only be generated
      within VACUUM FULL, redirect-pointer removal in heap_page_prune, and
      nontransactional generation of cache invalidation sinval messages (the last
      being the sticking point for Hot Standby).
      
      We still have to retain all code that copes with finding HEAP_MOVED_OFF and
      HEAP_MOVED_IN flag bits on existing tuples.  This can't be removed as long
      as we want to support in-place update from pre-9.0 databases.
      0a469c87
  3. 03 Feb, 2010 1 commit
  4. 16 Nov, 2009 1 commit
  5. 07 Aug, 2009 1 commit
  6. 17 Jun, 2009 1 commit
  7. 16 May, 2009 1 commit
  8. 23 Apr, 2009 1 commit
  9. 06 Apr, 2009 2 commits
  10. 09 Feb, 2009 1 commit
  11. 16 Jan, 2009 1 commit
  12. 11 Dec, 2008 1 commit
  13. 08 Dec, 2008 1 commit
  14. 16 Jun, 2008 1 commit
  15. 28 Nov, 2007 1 commit
  16. 07 Oct, 2007 1 commit
  17. 06 Oct, 2007 1 commit
  18. 24 Sep, 2007 1 commit
    • Tom Lane's avatar
      Simplify and rename some GUC variables, per various recent discussions: · 48f7e643
      Tom Lane authored
      * stats_start_collector goes away; we always start the collector process,
      unless prevented by a problem with setting up the stats UDP socket.
      
      * stats_reset_on_server_start goes away; it seems useless in view of the
      availability of pg_stat_reset().
      
      * stats_block_level and stats_row_level are merged into a single variable
      "track_counts", which controls all reports sent to the collector process.
      
      * stats_command_string is renamed to track_activities.
      
      * log_autovacuum is renamed to log_autovacuum_min_duration to better reflect
      its meaning.
      
      The log_autovacuum change is not a compatibility issue since it didn't exist
      before 8.3 anyway.  The other changes need to be release-noted.
      48f7e643
  19. 14 Sep, 2007 2 commits
  20. 13 Sep, 2007 1 commit
  21. 19 Aug, 2007 1 commit
  22. 23 Jul, 2007 1 commit
  23. 18 Jul, 2007 1 commit
  24. 30 May, 2007 1 commit
  25. 15 May, 2007 1 commit
  26. 03 May, 2007 1 commit
  27. 18 Apr, 2007 1 commit
  28. 16 Apr, 2007 1 commit
    • Alvaro Herrera's avatar
      Add a multi-worker capability to autovacuum. This allows multiple worker · e2a186b0
      Alvaro Herrera authored
      processes to be running simultaneously.  Also, now autovacuum processes do not
      count towards the max_connections limit; they are counted separately from
      regular processes, and are limited by the new GUC variable
      autovacuum_max_workers.
      
      The launcher now has intelligence to launch workers on each database every
      autovacuum_naptime seconds, limited only on the max amount of worker slots
      available.
      
      Also, the global worker I/O utilization is limited by the vacuum cost-based
      delay feature.  Workers are "balanced" so that the total I/O consumption does
      not exceed the established limit.  This part of the patch was contributed by
      ITAGAKI Takahiro.
      
      Per discussion.
      e2a186b0
  29. 01 Feb, 2007 2 commits
  30. 31 Jan, 2007 2 commits
    • Bruce Momjian's avatar
      Update documentation on may/can/might: · a134ee33
      Bruce Momjian authored
      Standard English uses "may", "can", and "might" in different ways:
      
              may - permission, "You may borrow my rake."
      
              can - ability, "I can lift that log."
      
              might - possibility, "It might rain today."
      
      Unfortunately, in conversational English, their use is often mixed, as
      in, "You may use this variable to do X", when in fact, "can" is a better
      choice.  Similarly, "It may crash" is better stated, "It might crash".
      
      Also update two error messages mentioned in the documenation to match.
      a134ee33
    • Bruce Momjian's avatar
      08674935
  31. 16 Jan, 2007 1 commit
  32. 27 Dec, 2006 1 commit
  33. 05 Nov, 2006 1 commit
    • Tom Lane's avatar
      Fix recently-understood problems with handling of XID freezing, particularly · 48188e16
      Tom Lane authored
      in PITR scenarios.  We now WAL-log the replacement of old XIDs with
      FrozenTransactionId, so that such replacement is guaranteed to propagate to
      PITR slave databases.  Also, rather than relying on hint-bit updates to be
      preserved, pg_clog is not truncated until all instances of an XID are known to
      have been replaced by FrozenTransactionId.  Add new GUC variables and
      pg_autovacuum columns to allow management of the freezing policy, so that
      users can trade off the size of pg_clog against the amount of freezing work
      done.  Revise the already-existing code that forces autovacuum of tables
      approaching the wraparound point to make it more bulletproof; also, revise the
      autovacuum logic so that anti-wraparound vacuuming is done per-table rather
      than per-database.  initdb forced because of changes in pg_class, pg_database,
      and pg_autovacuum catalogs.  Heikki Linnakangas, Simon Riggs, and Tom Lane.
      48188e16
  34. 23 Oct, 2006 1 commit
  35. 16 Sep, 2006 1 commit
  36. 29 Aug, 2006 1 commit