1. 12 Sep, 2001 1 commit
  2. 09 Sep, 2001 1 commit
  3. 07 Sep, 2001 1 commit
  4. 15 Aug, 2001 1 commit
  5. 09 Aug, 2001 1 commit
  6. 15 Jul, 2001 1 commit
  7. 30 Jun, 2001 2 commits
  8. 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
  9. 23 Jun, 2001 1 commit
  10. 18 Jun, 2001 1 commit
  11. 17 May, 2001 1 commit
  12. 12 May, 2001 1 commit
  13. 08 May, 2001 1 commit
  14. 07 May, 2001 1 commit
  15. 04 May, 2001 2 commits
  16. 03 May, 2001 1 commit
  17. 02 May, 2001 1 commit
  18. 01 May, 2001 1 commit
  19. 24 Mar, 2001 1 commit
  20. 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
  21. 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
  22. 18 Feb, 2001 1 commit
  23. 16 Feb, 2001 3 commits
  24. 15 Feb, 2001 1 commit
  25. 10 Feb, 2001 1 commit
  26. 09 Feb, 2001 1 commit
  27. 24 Jan, 2001 2 commits
  28. 08 Jan, 2001 1 commit
  29. 30 Dec, 2000 1 commit
  30. 22 Dec, 2000 1 commit
  31. 21 Dec, 2000 1 commit
  32. 17 Dec, 2000 1 commit
  33. 03 Dec, 2000 1 commit
  34. 30 Nov, 2000 1 commit
  35. 25 Nov, 2000 1 commit
    • Tom Lane's avatar
      Store current LC_COLLATE and LC_CTYPE settings in pg_control during initdb; · bbea3643
      Tom Lane authored
      re-adopt these settings at every postmaster or standalone-backend startup.
      This should fix problems with indexes becoming corrupt due to failure to
      provide consistent locale environment for postmaster at all times.  Also,
      refuse to start up a non-locale-enabled compilation in a database originally
      initdb'd with a non-C locale.  Suppress LIKE index optimization if locale
      is not "C" or "POSIX" (are there any other locales where it's safe?).
      Issue NOTICE during initdb if selected locale disables LIKE optimization.
      bbea3643