1. 14 Mar, 2001 17 commits
  2. 13 Mar, 2001 11 commits
    • Peter Eisentraut's avatar
      Provide more useful error message if 'postgres -V' failed. Advertise · f192da1b
      Peter Eisentraut authored
      pg_ctl '-l' option.
      f192da1b
    • Peter Eisentraut's avatar
      update · 253c8fec
      Peter Eisentraut authored
      253c8fec
    • Peter Eisentraut's avatar
      update · a0d82817
      Peter Eisentraut authored
      a0d82817
    • Tom Lane's avatar
      Change xlog page-header format to include StartUpID. Use the SUI to · 1b87e24c
      Tom Lane authored
      detect case that next page in log came from an older run than the prior
      page.  This avoids the necessity to re-zero the log after recovery from
      a crash, which is good because we need not risk destroying valuable log
      information.
      This forces another initdb since yesterday :-(.  Need to get that log
      reset utility done...
      1b87e24c
    • Peter Eisentraut's avatar
      e2f91389
    • Bruce Momjian's avatar
      Update FAQ. · fb8cdc2f
      Bruce Momjian authored
      fb8cdc2f
    • Philip Warner's avatar
      Document changed features of pg_dump, including: · 704d7fa8
      Philip Warner authored
      - Large Object dumps
      - Compressed custom format
      - Requirement to use template0 when creating DB
      704d7fa8
    • Philip Warner's avatar
      - Use subselect when enabling triggers, · ccca223b
      Philip Warner authored
      - Use exact table names when enabling/disabling triggers
      ccca223b
    • Hiroshi Inoue's avatar
      The attached file contains the registry settings required to install the · e376cb60
      Hiroshi Inoue authored
      ODBC driver on Windows 9X/ME/NT/2K when using the later versions of the
      driver that don't have the Installshield installation:
      
      1) Install psqlodbc.dll in to C:\Windows\System or C:\Winnt\System32
      2) Add the registry settings in the attached file using regedit.
      
      A useful addition to src/interfaces/odbc perhaps?
      
      Regards, Dave.
      e376cb60
    • Tom Lane's avatar
      Update for new pg_control format. · 0c383155
      Tom Lane authored
      0c383155
    • 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
  3. 12 Mar, 2001 1 commit
  4. 11 Mar, 2001 3 commits
  5. 10 Mar, 2001 8 commits