1. 20 Jan, 2000 1 commit
  2. 09 Jan, 2000 1 commit
  3. 07 Jan, 2000 1 commit
  4. 16 Dec, 1999 1 commit
  5. 06 Dec, 1999 1 commit
  6. 04 Dec, 1999 1 commit
  7. 03 Dec, 1999 1 commit
  8. 25 Oct, 1999 1 commit
    • Tom Lane's avatar
      Standardize on MAXPGPATH as the size of a file pathname buffer, · 51f62d50
      Tom Lane authored
      eliminating some wildly inconsistent coding in various parts of the
      system.  I set MAXPGPATH = 1024 in config.h.in.  If anyone is really
      convinced that there ought to be a configure-time test to set the
      value, go right ahead ... but I think it's a waste of time.
      51f62d50
  9. 08 Oct, 1999 4 commits
  10. 06 Oct, 1999 2 commits
  11. 30 Sep, 1999 2 commits
  12. 27 Sep, 1999 2 commits
    • Vadim B. Mikheev's avatar
      Transaction log manager core code. · 30659d43
      Vadim B. Mikheev authored
      It doesn't work currently but also don't break anything -:)
      30659d43
    • Bruce Momjian's avatar
      Lots of patches coming in from me today :-) · e0e7daef
      Bruce Momjian authored
      When drawing up a very simple "text-drawing" of how the negotiation is done,
      I realised I had done this last part (fallback) in a very stupid way. Patch
      #4 fixes this, and does it in a much better way.
      
      Included is also the simple text-drawing of how the negotiation is done.
      
      //Magnus
      e0e7daef
  13. 21 Sep, 1999 1 commit
  14. 19 Jul, 1999 1 commit
  15. 17 Jul, 1999 1 commit
  16. 16 Jul, 1999 3 commits
  17. 15 Jul, 1999 2 commits
  18. 07 Jul, 1999 1 commit
  19. 02 Jul, 1999 1 commit
  20. 04 Jun, 1999 1 commit
  21. 25 May, 1999 1 commit
  22. 22 May, 1999 1 commit
  23. 21 Feb, 1999 1 commit
    • Tom Lane's avatar
      Rearrange handling of MAXBACKENDS a little bit. The default setting · 9d197856
      Tom Lane authored
      of MAXBACKENDS is now 1024, since all it's costing is about 32 bytes of memory
      per array slot.  configure's --with-maxbackends switch now controls DEF_MAXBACKENDS
      which is simply the default value of the postmaster's -N switch.  Thus,
      the out-of-the-box configuration will still limit you to 64 backends,
      but you can go up to 1024 backends simply by restarting the postmaster with
      a different -N switch --- no rebuild required.
      9d197856
  24. 19 Feb, 1999 1 commit
    • Tom Lane's avatar
      Allow maximum number of backends to be set at configure time · e77b630c
      Tom Lane authored
      (--with-maxbackends).  Add a postmaster switch (-N backends) that allows
      the limit to be reduced at postmaster start time.  (You can't increase it,
      sorry to say, because there are still some fixed-size arrays.)
      Grab the number of semaphores indicated by min(MAXBACKENDS, -N) at
      postmaster startup, so that this particular form of bogus configuration
      is exposed immediately rather than under heavy load.
      e77b630c
  25. 13 Feb, 1999 1 commit
  26. 30 Jan, 1999 1 commit
  27. 17 Jan, 1999 1 commit
  28. 29 Nov, 1998 1 commit
  29. 01 Sep, 1998 2 commits
  30. 25 Aug, 1998 1 commit
    • Marc G. Fournier's avatar
      · 7414d619
      Marc G. Fournier authored
      From: Massimo Dal Zotto <dz@cs.unitn.it>
      
      > tprintf.patch
      >
      >       tprintf.patch
      >
      >       adds functions and macros which implement a conditional trace package
      >       with the ability to change flags and numeric options of running
      >       backends at runtime.
      >       Options/flags can be specified in the command line and/or read from
      >       the file pg_options in the data directory.
      7414d619