1. 05 5月, 2002 1 次提交
  2. 13 3月, 2002 1 次提交
    • P
      Move · f362dcec
      Peter Eisentraut 提交于
        src/GNUmakefile.in to src/Makefile
      and
        src/backend/port/Makefile.in to src/backend/port/Makefile
      
      All configure substitutions are now done in Makefile.global.
      f362dcec
  3. 06 3月, 2002 1 次提交
    • B
      Change made to elog: · 92288a1c
      Bruce Momjian 提交于
      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
  4. 05 3月, 2002 1 次提交
  5. 18 2月, 2002 1 次提交
  6. 13 2月, 2002 1 次提交
  7. 12 2月, 2002 1 次提交
  8. 21 12月, 2001 1 次提交
  9. 05 12月, 2001 1 次提交
  10. 16 11月, 2001 1 次提交
  11. 12 11月, 2001 1 次提交
  12. 09 11月, 2001 1 次提交
  13. 08 11月, 2001 1 次提交
  14. 06 11月, 2001 1 次提交
  15. 01 11月, 2001 1 次提交
  16. 28 10月, 2001 1 次提交
  17. 25 10月, 2001 2 次提交
  18. 07 9月, 2001 1 次提交
  19. 24 8月, 2001 1 次提交
  20. 08 8月, 2001 1 次提交
  21. 21 6月, 2001 1 次提交
  22. 31 5月, 2001 1 次提交
  23. 24 5月, 2001 1 次提交
    • B
      I haven't tried building postgres with the Watcom compiler for 7.1 because · f36fc7bb
      Bruce Momjian 提交于
      it does not support 64bit integers. AFAIK that's the default data type for
      OIDs, so I am not surprised that this does not work. Use gcc instead.
      BTW., 7.1 does not compile as is with gcc either, I believed the
      required patches made it into the 7.1.1 release but obviously I missed
      the deadline.
      Since the ports mailing list does not seem to be archived I have attached
      a copy of the patch (for 7.1 and 7.1.1).
      
      I've just performed a build of a Watcom compiled version and found a couple
      of bugs in the watcom specific part of that patch. Please use the attached
      version instead.
      
      Tegge, Bernd
      f36fc7bb
  24. 16 5月, 2001 1 次提交
  25. 15 5月, 2001 2 次提交
  26. 09 5月, 2001 1 次提交
  27. 02 4月, 2001 1 次提交
  28. 27 3月, 2001 1 次提交
    • B
      The following patch updates the FAQ_AIX and makes C++ code work with · 341cb700
      Bruce Momjian 提交于
      more recent versions of the IBM C++ compiler (now called VisualAge C++).
      The C++ part was previously broken (g++ and xlC), thus this is zero risk.
      Only AIX specific parts are touched (1 Makefile.shlib line (link with $(COMPILER
      ) instead
      of $(CC) and one shell script line (parameter -C to nm to not demangle C++ symbo
      ls for
      .exp file)).
      
      I thus ask you to please apply this patch before release.
      
      With or without this patch RC1 on AIX 4.3.2 RS6000 passes "gmake check" for both
       the native
      compiler vac.C 5.0.1 and gcc 2.95.2 :-)
      
      Andreas
      341cb700
  29. 22 3月, 2001 1 次提交
  30. 19 3月, 2001 2 次提交
  31. 13 3月, 2001 1 次提交
    • T
      XLOG (and related) changes: · 4d14fe00
      Tom Lane 提交于
      * 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
  32. 02 3月, 2001 1 次提交
  33. 10 2月, 2001 2 次提交
    • T
      Restructure the key include files per recent pghackers discussion: there · d08741ea
      Tom Lane 提交于
      are now separate files "postgres.h" and "postgres_fe.h", which are meant
      to be the primary include files for backend .c files and frontend .c files
      respectively.  By default, only include files meant for frontend use are
      installed into the installation include directory.  There is a new make
      target 'make install-all-headers' that adds the whole content of the
      src/include tree to the installed fileset, for use by people who want to
      develop server-side code without keeping the complete source tree on hand.
      Cleaned up a whole lot of crufty and inconsistent header inclusions.
      d08741ea
    • T
      This hasn't been used for anything for a long time... · b1e4cfa5
      Tom Lane 提交于
      b1e4cfa5
  34. 08 2月, 2001 1 次提交
  35. 03 2月, 2001 1 次提交
  36. 25 1月, 2001 1 次提交