1. 13 Jul, 2002 1 commit
  2. 16 Jun, 2002 1 commit
  3. 17 May, 2002 2 commits
  4. 14 May, 2002 1 commit
  5. 21 Apr, 2002 1 commit
  6. 03 Apr, 2002 1 commit
  7. 01 Apr, 2002 1 commit
    • Tom Lane's avatar
      Create a new GUC variable search_path to control the namespace search · 838fe25a
      Tom Lane authored
      path.  The default behavior if no per-user schemas are created is that
      all users share a 'public' namespace, thus providing behavior backwards
      compatible with 7.2 and earlier releases.  Probably the semantics and
      default setting will need to be fine-tuned, but this is a start.
      838fe25a
  8. 24 Mar, 2002 1 commit
  9. 06 Mar, 2002 1 commit
    • Bruce Momjian's avatar
      Change made to elog: · 92288a1c
      Bruce Momjian authored
      o  Change all current CVS messages of NOTICE to WARNING.  We were going
      to do this just before 7.3 beta but it has to be done now, as you will
      see below.
      
      o Change current INFO messages that should be controlled by
      client_min_messages to NOTICE.
      
      o Force remaining INFO messages, like from EXPLAIN, VACUUM VERBOSE, etc.
      to always go to the client.
      
      o Remove INFO from the client_min_messages options and add NOTICE.
      
      Seems we do need three non-ERROR elog levels to handle the various
      behaviors we need for these messages.
      
      Regression passed.
      92288a1c
  10. 02 Mar, 2002 1 commit
    • Bruce Momjian's avatar
      Commit to match discussed elog() changes. Only update is that LOG is · a033daf5
      Bruce Momjian authored
      now just below FATAL in server_min_messages.  Added more text to
      highlight ordering difference between it and client_min_messages.
      
      ---------------------------------------------------------------------------
      
      REALLYFATAL => PANIC
      STOP => PANIC
      New INFO level the prints to client by default
      New LOG level the prints to server log by default
      Cause VACUUM information to print only to the client
      NOTICE => INFO where purely information messages are sent
      DEBUG => LOG for purely server status messages
      DEBUG removed, kept as backward compatible
      DEBUG5, DEBUG4, DEBUG3, DEBUG2, DEBUG1 added
      DebugLvl removed in favor of new DEBUG[1-5] symbols
      New server_min_messages GUC parameter with values:
              DEBUG[5-1], INFO, NOTICE, ERROR, LOG, FATAL, PANIC
      New client_min_messages GUC parameter with values:
              DEBUG[5-1], LOG, INFO, NOTICE, ERROR, FATAL, PANIC
      Server startup now logged with LOG instead of DEBUG
      Remove debug_level GUC parameter
      elog() numbers now start at 10
      Add test to print error message if older elog() values are passed to elog()
      Bootstrap mode now has a -d that requires an argument, like postmaster
      a033daf5
  11. 01 Mar, 2002 1 commit
  12. 23 Feb, 2002 1 commit
  13. 30 Oct, 2001 1 commit
  14. 28 Oct, 2001 1 commit
  15. 25 Oct, 2001 1 commit
  16. 30 Sep, 2001 2 commits
    • Tom Lane's avatar
      Allow the postmaster to accept changes in PGC_BACKEND GUC variables · f00da6d8
      Tom Lane authored
      from the config file, so that these changes will propagate to backends
      started later.  Already-started backends continue to ignore changes
      in these variables.
      f00da6d8
    • Tom Lane's avatar
      Create a GUC parameter max_files_per_process that is a configurable · f9f25828
      Tom Lane authored
      upper limit on what we will believe from sysconf(_SC_OPEN_MAX).  The
      default value is 1000, so that under ordinary conditions it won't
      affect the behavior.  But on platforms where the kernel promises far
      more than it can deliver, this can be used to prevent running out of
      file descriptors.  See numerous past discussions, eg, pgsql-hackers
      around 23-Dec-2000.
      f9f25828
  17. 29 Sep, 2001 1 commit
    • Tom Lane's avatar
      Implement new 'lightweight lock manager' that's intermediate between · 499abb0c
      Tom Lane authored
      existing lock manager and spinlocks: it understands exclusive vs shared
      lock but has few other fancy features.  Replace most uses of spinlocks
      with lightweight locks.  All remaining uses of spinlocks have very short
      lock hold times (a few dozen instructions), so tweak spinlock backoff
      code to work efficiently given this assumption.  All per my proposal on
      pghackers 26-Sep-01.
      499abb0c
  18. 23 Sep, 2001 1 commit
  19. 21 Sep, 2001 2 commits
  20. 20 Sep, 2001 1 commit
  21. 12 Sep, 2001 1 commit
  22. 07 Sep, 2001 1 commit
  23. 15 Aug, 2001 1 commit
  24. 05 Jul, 2001 1 commit
  25. 30 Jun, 2001 1 commit
  26. 27 Jun, 2001 1 commit
    • Tom Lane's avatar
      Install infrastructure for shared-memory free space map. Doesn't actually · e0c9301c
      Tom Lane authored
      do anything yet, but it has the necessary connections to initialization
      and so forth.  Make some gestures towards allowing number of blocks in
      a relation to be BlockNumber, ie, unsigned int, rather than signed int.
      (I doubt I got all the places that are sloppy about it, yet.)  On the
      way, replace the hardwired NLOCKS_PER_XACT fudge factor with a GUC
      variable.
      e0c9301c
  27. 23 Jun, 2001 1 commit
    • Bruce Momjian's avatar
      > Marko Kreen <marko@l-t.ee> writes: · 6a7f23c2
      Bruce Momjian authored
      > > secure_ctx changes too.  it will be PGC_BACKEND after '-p'.
      >
      > Oh, okay, I missed that part.  Could we see the total state of the
      > patch --- ie, a diff against current CVS, not a bunch of deltas?
      > I've gotten confused about what's in and what's out.
      
      Ok, here it is.  Cleared the ctx comment too - after -p
      it will be PGC_BACKEND in any case.
      
      Marko Kreen
      6a7f23c2
  28. 19 Jun, 2001 1 commit
  29. 18 Jun, 2001 2 commits
  30. 12 Jun, 2001 1 commit
    • Tom Lane's avatar
      Extend GUC concepts of parse_hook and assign_hook to all four supported · 2938eec7
      Tom Lane authored
      datatypes, not only strings.  parse_hook is useless for bool, I suppose,
      but it seems possibly useful for int and double to apply variable-specific
      constraints that are more complex than simple range limits.  assign_hook
      is definitely useful for all datatypes --- we need it right now for bool
      to support date cache reset when changing Australian timezone rule setting.
      Also, clean up some residual problems with the reset all/show all patch,
      including memory leaks and mistaken reset of PostPortNumber.  It seems
      best that RESET ALL not touch variables that don't have SUSET or
      USERSET context.
      2938eec7
  31. 07 Jun, 2001 1 commit
  32. 17 May, 2001 1 commit
  33. 22 Mar, 2001 2 commits
  34. 16 Mar, 2001 1 commit
    • Tom Lane's avatar
      Support syncing WAL log to disk using either fsync(), fdatasync(), · 9d645fd8
      Tom Lane authored
      O_SYNC, or O_DSYNC (as available on a given platform).  Add GUC parameter
      to control sync method.
      Also, add defense to XLogWrite to prevent it from going nuts if passed
      a target write position that's past the end of the buffers so far filled
      by XLogInsert.
      9d645fd8
  35. 13 Mar, 2001 1 commit
    • Tom Lane's avatar
      XLOG (and related) changes: · 4d14fe00
      Tom Lane authored
      * Store two past checkpoint locations, not just one, in pg_control.
        On startup, we fall back to the older checkpoint if the newer one
        is unreadable.  Also, a physical copy of the newest checkpoint record
        is kept in pg_control for possible use in disaster recovery (ie,
        complete loss of pg_xlog).  Also add a version number for pg_control
        itself.  Remove archdir from pg_control; it ought to be a GUC
        parameter, not a special case (not that it's implemented yet anyway).
      
      * Suppress successive checkpoint records when nothing has been entered
        in the WAL log since the last one.  This is not so much to avoid I/O
        as to make it actually useful to keep track of the last two
        checkpoints.  If the things are right next to each other then there's
        not a lot of redundancy gained...
      
      * Change CRC scheme to a true 64-bit CRC, not a pair of 32-bit CRCs
        on alternate bytes.  Polynomial borrowed from ECMA DLT1 standard.
      
      * Fix XLOG record length handling so that it will work at BLCKSZ = 32k.
      
      * Change XID allocation to work more like OID allocation.  (This is of
        dubious necessity, but I think it's a good idea anyway.)
      
      * Fix a number of minor bugs, such as off-by-one logic for XLOG file
        wraparound at the 4 gig mark.
      
      * Add documentation and clean up some coding infelicities; move file
        format declarations out to include files where planned contrib
        utilities can get at them.
      
      * Checkpoint will now occur every CHECKPOINT_SEGMENTS log segments or
        every CHECKPOINT_TIMEOUT seconds, whichever comes first.  It is also
        possible to force a checkpoint by sending SIGUSR1 to the postmaster
        (undocumented feature...)
      
      * Defend against kill -9 postmaster by storing shmem block's key and ID
        in postmaster.pid lockfile, and checking at startup to ensure that no
        processes are still connected to old shmem block (if it still exists).
      
      * Switch backends to accept SIGQUIT rather than SIGUSR1 for emergency
        stop, for symmetry with postmaster and xlog utilities.  Clean up signal
        handling in bootstrap.c so that xlog utilities launched by postmaster
        will react to signals better.
      
      * Standalone bootstrap now grabs lockfile in target directory, as added
        insurance against running it in parallel with live postmaster.
      4d14fe00