1. 20 Jun, 2006 1 commit
    • Tom Lane's avatar
      Split definitions for md5.c out of crypt.h and into their own header · 47a37aee
      Tom Lane authored
      libpq/md5.h, so that there's a clear separation between backend-only
      definitions and shared frontend/backend definitions.  (Turns out this
      is reversing a bad decision from some years ago...)  Fix up references
      to crypt.h as needed.  I looked into moving the code into src/port, but
      the headers in src/include/libpq are sufficiently intertwined that it
      seems more work than it's worth to do that.
      47a37aee
  2. 06 Mar, 2006 1 commit
  3. 05 Mar, 2006 1 commit
  4. 17 Oct, 2005 1 commit
  5. 15 Oct, 2005 1 commit
  6. 11 Aug, 2005 1 commit
    • Tom Lane's avatar
      Autovacuum loose end mop-up. Provide autovacuum-specific vacuum cost · d90c5311
      Tom Lane authored
      delay and limit, both as global GUCs and as table-specific entries in
      pg_autovacuum.  stats_reset_on_server_start is now OFF by default,
      but a reset is forced if we did WAL replay.  XID-wrap vacuums do not
      ANALYZE, but do FREEZE if it's a template database.  Alvaro Herrera
      d90c5311
  7. 29 Jul, 2005 1 commit
    • Tom Lane's avatar
      Clean up a number of autovacuum loose ends. Make the stats collector · 5d5f1a79
      Tom Lane authored
      track shared relations in a separate hashtable, so that operations done
      from different databases are counted correctly.  Add proper support for
      anti-XID-wraparound vacuuming, even in databases that are never connected
      to and so have no stats entries.  Miscellaneous other bug fixes.
      Alvaro Herrera, some additional fixes by Tom Lane.
      5d5f1a79
  8. 28 Jul, 2005 1 commit
  9. 28 Jun, 2005 2 commits
  10. 27 Jun, 2005 1 commit
  11. 21 Jun, 2005 1 commit
  12. 26 Feb, 2005 1 commit
    • Tom Lane's avatar
      Finish up the flat-files project: get rid of GetRawDatabaseInfo() hack · 0fc4ecf9
      Tom Lane authored
      in favor of looking at the flat file copy of pg_database during backend
      startup.  This should finally eliminate the various corner cases in which
      backend startup fails unexpectedly because it isn't able to distinguish
      live and dead tuples in pg_database.  Simplify locking on pg_database
      to be similar to the rules used with pg_shadow and pg_group, and eliminate
      FlushRelationBuffers operations that were used only to reduce the odds
      of failure of GetRawDatabaseInfo.
      initdb forced due to addition of a trigger to pg_database.
      0fc4ecf9
  13. 20 Feb, 2005 2 commits
    • Tom Lane's avatar
      Flat file cleanup phase 2: make it work for pg_group. The flat group · 3f9aec50
      Tom Lane authored
      file now identifies group members by usesysid not name; this avoids
      needing to depend on SearchSysCache which we can't use during startup.
      (The old representation was entirely broken anyway, since we did not
      regenerate the file following RENAME USER.)  It's only a 95% solution
      because if the group membership list is big enough to be toasted out
      of line, we cannot read it during startup.  I think this will do for
      the moment, until we have time to implement the planned pg_role
      replacement for pg_group.
      3f9aec50
    • Tom Lane's avatar
      Add code to prevent transaction ID wraparound by enforcing a safe limit · 60b2444c
      Tom Lane authored
      in GetNewTransactionId().  Since the limit value has to be computed
      before we run any real transactions, this requires adding code to database
      startup to scan pg_database and determine the oldest datfrozenxid.
      This can conveniently be combined with the first stage of an attack on
      the problem that the 'flat file' copies of pg_shadow and pg_group are
      not properly updated during WAL recovery.  The code I've added to
      startup resides in a new file src/backend/utils/init/flatfiles.c, and
      it is responsible for rewriting the flat files as well as initializing
      the XID wraparound limit value.  This will eventually allow us to get
      rid of GetRawDatabaseInfo too, but we'll need an initdb so we can add
      a trigger to pg_database.
      60b2444c
  14. 12 Feb, 2005 1 commit
  15. 31 Dec, 2004 1 commit
    • PostgreSQL Daemon's avatar
      · 2ff50159
      PostgreSQL Daemon authored
      Tag appropriate files for rc3
      
      Also performed an initial run through of upgrading our Copyright date to
      extend to 2005 ... first run here was very simple ... change everything
      where: grep 1996-2004 && the word 'Copyright' ... scanned through the
      generated list with 'less' first, and after, to make sure that I only
      picked up the right entries ...
      2ff50159
  16. 27 Dec, 2004 1 commit
  17. 17 Nov, 2004 1 commit
  18. 12 Oct, 2004 1 commit
  19. 09 Oct, 2004 1 commit
  20. 08 Oct, 2004 1 commit
  21. 18 Sep, 2004 1 commit
  22. 29 Aug, 2004 2 commits
  23. 26 Jul, 2004 1 commit
  24. 11 Jul, 2004 1 commit
  25. 30 May, 2004 1 commit
  26. 26 May, 2004 2 commits
    • Bruce Momjian's avatar
      *) inet_(client|server)_(addr|port)() and necessary documentation for · 97d625dd
      Bruce Momjian authored
      the four functions.
      
      
      > Also, please justify the temp-related changes.  I was not aware that we
      > had any breakage there.
      
      patch-tmp-schema.txt contains the following bits:
      
      *) Changes pg_namespace_aclmask() so that the superuser is always able
      to create objects in the temp namespace.
      *) Changes pg_namespace_aclmask() so that if this is a temp namespace,
      objects are only allowed to be created in the temp namespace if the
      user has TEMP privs on the database.  This encompasses all object
      creation, not just TEMP tables.
      *) InitTempTableNamespace() checks to see if the current user, not the
      session user, has access to create a temp namespace.
      
      The first two changes are necessary to support the third change.  Now
      it's possible to revoke all temp table privs from non-super users and
      limiting all creation of temp tables/schemas via a function that's
      executed with elevated privs (security definer).  Before this change,
      it was not possible to have a setuid function to create a temp
      table/schema if the session user had no TEMP privs.
      
      patch-area-path.txt contains:
      
      *) Can now determine the area of a closed path.
      
      
      patch-dfmgr.txt contains:
      
      *) Small tweak to add the library path that's being expanded.
      
      I was using $lib/foo.so and couldn't easily figure out what the error
      message, "invalid macro name in dynamic library path" meant without
      looking through the source code.  With the path in there, at least I
      know where to start looking in my config file.
      
      Sean Chittenden
      97d625dd
    • Neil Conway's avatar
      Reimplement the linked list data structure used throughout the backend. · d0b4399d
      Neil Conway authored
      In the past, we used a 'Lispy' linked list implementation: a "list" was
      merely a pointer to the head node of the list. The problem with that
      design is that it makes lappend() and length() linear time. This patch
      fixes that problem (and others) by maintaining a count of the list
      length and a pointer to the tail node along with each head node pointer.
      A "list" is now a pointer to a structure containing some meta-data
      about the list; the head and tail pointers in that structure refer
      to ListCell structures that maintain the actual linked list of nodes.
      
      The function names of the list API have also been changed to, I hope,
      be more logically consistent. By default, the old function names are
      still available; they will be disabled-by-default once the rest of
      the tree has been updated to use the new API names.
      d0b4399d
  27. 25 May, 2004 1 commit
  28. 19 May, 2004 1 commit
  29. 02 Feb, 2004 1 commit
  30. 25 Dec, 2003 1 commit
  31. 05 Dec, 2003 1 commit
  32. 29 Nov, 2003 1 commit
    • PostgreSQL Daemon's avatar
      · 969685ad
      PostgreSQL Daemon authored
      $Header: -> $PostgreSQL Changes ...
      969685ad
  33. 25 Oct, 2003 1 commit
  34. 25 Sep, 2003 1 commit
  35. 05 Sep, 2003 2 commits