1. 23 Feb, 2002 1 commit
  2. 19 Feb, 2002 1 commit
  3. 10 Jan, 2002 1 commit
  4. 01 Jan, 2002 1 commit
  5. 04 Dec, 2001 1 commit
  6. 10 Nov, 2001 1 commit
  7. 05 Nov, 2001 1 commit
  8. 28 Oct, 2001 1 commit
  9. 25 Oct, 2001 1 commit
  10. 21 Oct, 2001 1 commit
  11. 19 Oct, 2001 3 commits
    • Tom Lane's avatar
      Set optreset on platforms that have it before launching postmaster · 861a679f
      Tom Lane authored
      subprocesses; perhaps this will fix portability problem just noted by
      Lockhart.  Also, move test for bad permissions of DataDir to a more
      logical place.
      861a679f
    • Tom Lane's avatar
      Ensure that all startup paths (postmaster, standalone postgres, or · 6430e6e2
      Tom Lane authored
      bootstrap) check for a valid PG_VERSION file before looking at anything
      else in the data directory.  This fixes confusing error report when
      trying to start current sources in a pre-7.1 data directory.
      Per trouble report from Rich Shepard 10/18/01.
      6430e6e2
    • Tom Lane's avatar
      Move init_ps_display from postgres.c to postmaster.c, putting it · eb133197
      Tom Lane authored
      just after receipt of the startup packet.  Now, postmaster children
      that are waiting for client authentication response will show as
      'postgres: user database host authentication'.  Also, do an
      init_ps_display for startup/shutdown/checkpoint subprocesses,
      so that they are readily identifiable as well.  Fix an obscure race
      condition that could lead to Assert failure in the postmaster ---
      attempting to start a checkpoint process before any connections have
      been received led to calling PostmasterRandom before setting random_seed.
      eb133197
  12. 27 Sep, 2001 1 commit
  13. 21 Sep, 2001 1 commit
    • Tom Lane's avatar
      Add an overall timeout on the client authentication cycle, so that · 35b7601b
      Tom Lane authored
      a hung client or lost connection can't indefinitely block a postmaster
      child (not to mention the possibility of deliberate DoS attacks).
      Timeout is controlled by new authentication_timeout GUC variable,
      which I set to 60 seconds by default ... does that seem reasonable?
      35b7601b
  14. 08 Sep, 2001 1 commit
    • Tom Lane's avatar
      Clean up some confusion about where and how to set whereToSendOutput. · 02b1a7fd
      Tom Lane authored
      We will no longer try to send elog messages to the client before we have
      initialized backend libpq (oops); however, reporting bogus commandline
      switches via elog does work now (not irrelevant, because of PGOPTIONS).
      Fix problem with inappropriate sending of checkpoint-process messages
      to stderr.
      02b1a7fd
  15. 07 Sep, 2001 1 commit
  16. 04 Aug, 2001 1 commit
    • Tom Lane's avatar
      Fix handling of SIGCHLD, per recent pghackers discussion: on some · dad8e410
      Tom Lane authored
      platforms system(2) gets confused unless the signal handler is set to
      SIG_DFL, not SIG_IGN.  pgstats.c now uses pqsignal() as it should,
      not signal().  Also, arrange for the stats collector process to show
      a reasonable ID in 'ps', rather than looking like a postmaster.
      dad8e410
  17. 31 Jul, 2001 1 commit
    • Tom Lane's avatar
      Cleanup code for preparsing pg_hba.conf and pg_ident.conf. Store line · 77896d1f
      Tom Lane authored
      number in the data structure so that we can give at least a minimally
      useful idea of where the mistake is when we issue syntax error messages.
      Move the ClientAuthentication() call to where it should have been in
      the first place, so that postmaster memory releasing can happen in a
      reasonable place also.  Update obsolete comments, correct one real bug
      (auth_argument was not picked up correctly).
      77896d1f
  18. 30 Jul, 2001 1 commit
  19. 29 Jun, 2001 1 commit
  20. 25 Jun, 2001 1 commit
  21. 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
  22. 22 Jun, 2001 1 commit
  23. 20 Jun, 2001 1 commit
    • Peter Eisentraut's avatar
      Handle reading of startup packet and authentication exchange after forking · 9b4bfbdc
      Peter Eisentraut authored
      a new postmaster child process.  This should eliminate problems with
      authentication blocking (e.g., ident, SSL init) and also reduce problems
      with the accept queue filling up under heavy load.
      
      The option to send elog output to a different file per backend (postgres -o)
      has been disabled for now because the initialization would have to happen
      in a different order and it's not clear we want to keep this anyway.
      9b4bfbdc
  24. 19 Jun, 2001 1 commit
  25. 18 Jun, 2001 1 commit
    • Bruce Momjian's avatar
      RESET ALL secondary patch: · 3709a5ad
      Bruce Momjian authored
      Here is Tomified version of my 2 pending patches.
      Dropped the set_.._real change as it is not needed.
      Desc would be:
      
      * use GUC for settings from cmdline
      
      Marko Kreen
      3709a5ad
  26. 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
  27. 07 Jun, 2001 1 commit
  28. 14 Apr, 2001 1 commit
  29. 26 Mar, 2001 2 commits
  30. 23 Mar, 2001 1 commit
  31. 22 Mar, 2001 2 commits
  32. 14 Mar, 2001 2 commits
  33. 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
  34. 09 Mar, 2001 1 commit
  35. 24 Feb, 2001 1 commit