1. 01 Feb, 2007 1 commit
  2. 31 Jan, 2007 1 commit
    • 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
  3. 25 Jan, 2007 1 commit
  4. 07 Oct, 2006 1 commit
    • Peter Eisentraut's avatar
      The -X option in pg_dump was supposed to be a workaround for the lack of · 2b25e116
      Peter Eisentraut authored
      portable long options.  But we have had portable long options for a long
      time now, so this is obsolete.  Now people have added options which *only*
      work with -X but not as regular long option, so I'm putting a stop to this:
      -X is deprecated; it still works, but it has been removed from the
      documentation, and please don't add more of them.
      2b25e116
  5. 16 Sep, 2006 1 commit
  6. 05 Jun, 2006 1 commit
    • Tom Lane's avatar
      Add a GUC parameter seq_page_cost, and use that everywhere we formerly · eed6c9ed
      Tom Lane authored
      assumed that a sequential page fetch has cost 1.0.  This patch doesn't
      in itself change the system's behavior at all, but it opens the door to
      people adopting other units of measurement for EXPLAIN costs.  Also, if
      we ever decide it's worth inventing per-tablespace access cost settings,
      this change provides a workable intellectual framework for that.
      eed6c9ed
  7. 10 Mar, 2006 1 commit
  8. 20 Dec, 2005 1 commit
  9. 04 Nov, 2005 1 commit
  10. 02 Sep, 2005 2 commits
  11. 25 Mar, 2005 1 commit
    • Tom Lane's avatar
      Improve EXPLAIN ANALYZE to show the time spent in each trigger when · adb1a6e9
      Tom Lane authored
      executing a statement that fires triggers.  Formerly this time was
      included in "Total runtime" but not otherwise accounted for.
      As a side benefit, we avoid re-opening relations when firing non-deferred
      AFTER triggers, because the trigger code can re-use the main executor's
      ResultRelInfo data structure.
      adb1a6e9
  12. 03 Feb, 2005 1 commit
  13. 23 Dec, 2004 1 commit
  14. 01 Dec, 2004 1 commit
    • Tom Lane's avatar
      Change planner to use the current true disk file size as its estimate of · 5374d097
      Tom Lane authored
      a relation's number of blocks, rather than the possibly-obsolete value
      in pg_class.relpages.  Scale the value in pg_class.reltuples correspondingly
      to arrive at a hopefully more accurate number of rows.  When pg_class
      contains 0/0, estimate a tuple width from the column datatypes and divide
      that into current file size to estimate number of rows.  This improved
      methodology allows us to jettison the ancient hacks that put bogus default
      values into pg_class when a table is first created.  Also, per a suggestion
      from Simon, make VACUUM (but not VACUUM FULL or ANALYZE) adjust the value
      it puts into pg_class.reltuples to try to represent the mean tuple density
      instead of the minimal density that actually prevails just after VACUUM.
      These changes alter the plans selected for certain regression tests, so
      update the expected files accordingly.  (I removed join_1.out because
      it's not clear if it still applies; we can add back any variant versions
      as they are shown to be needed.)
      5374d097
  15. 15 Nov, 2004 1 commit
  16. 27 May, 2004 1 commit
  17. 22 Apr, 2004 2 commits
  18. 25 Mar, 2004 1 commit
  19. 09 Mar, 2004 1 commit
  20. 03 Feb, 2004 1 commit
    • Tom Lane's avatar
      Rename SortMem and VacuumMem to work_mem and maintenance_work_mem. · 391c3811
      Tom Lane authored
      Make btree index creation and initial validation of foreign-key constraints
      use maintenance_work_mem rather than work_mem as their memory limit.
      Add some code to guc.c to allow these variables to be referenced by their
      old names in SHOW and SET commands, for backwards compatibility.
      391c3811
  21. 11 Jan, 2004 1 commit
  22. 14 Dec, 2003 1 commit
  23. 29 Nov, 2003 1 commit
    • PostgreSQL Daemon's avatar
      · 969685ad
      PostgreSQL Daemon authored
      $Header: -> $PostgreSQL Changes ...
      969685ad
  24. 01 Nov, 2003 1 commit
  25. 17 Oct, 2003 2 commits
  26. 10 Oct, 2003 1 commit
  27. 11 Sep, 2003 2 commits
  28. 31 Aug, 2003 1 commit
  29. 25 Jun, 2003 1 commit
  30. 24 Jun, 2003 1 commit
  31. 25 Mar, 2003 1 commit
  32. 13 Mar, 2003 1 commit
  33. 28 Jan, 2003 1 commit
  34. 27 Jan, 2003 1 commit
  35. 25 Jan, 2003 1 commit
    • Tom Lane's avatar
      Allow the planner to collapse explicit inner JOINs together, rather than · 9f5f2124
      Tom Lane authored
      necessarily following the JOIN syntax to develop the query plan.  The old
      behavior is still available by setting GUC variable JOIN_COLLAPSE_LIMIT
      to 1.  Also create a GUC variable FROM_COLLAPSE_LIMIT to control the
      similar decision about when to collapse sub-SELECT lists into their parent
      lists.  (This behavior existed already, but the limit was always
      GEQO_THRESHOLD/2; now it's separately adjustable.)
      9f5f2124
  36. 12 Jan, 2003 1 commit