Skip to content
Snippets Groups Projects
  1. Feb 02, 1998
  2. Feb 01, 1998
  3. Jan 26, 1998
    • Marc G. Fournier's avatar
      From: Phil Thompson <phil@river-bank.demon.co.uk> · d5bbe2ac
      Marc G. Fournier authored
      I've completed the patch to fix the protocol and authentication issues I
      was discussing a couple of weeks ago.  The particular changes are:
      
      - the protocol has a version number
      - network byte order is used throughout
      - the pg_hba.conf file is used to specify what method is used to
        authenticate a frontend (either password, ident, trust, reject, krb4
        or krb5)
      - support for multiplexed backends is removed
      - appropriate changes to man pages
      - the -a switch to many programs to specify an authentication service
        no longer has any effect
      - the libpq.so version number has changed to 1.1
      
      The new backend still supports the old protocol so old interfaces won't
      break.
      d5bbe2ac
  4. Jan 25, 1998
  5. Jan 13, 1998
    • Marc G. Fournier's avatar
      Some *very* major changes by darrenk@insightdist.com (Darren King) · 374bb5d2
      Marc G. Fournier authored
      ==========================================
      What follows is a set of diffs that cleans up the usage of BLCKSZ.
      
      As a side effect, the person compiling the code can change the
      value of BLCKSZ _at_their_own_risk_.  By that, I mean that I've
      tried it here at 4096 and 16384 with no ill-effects.  A value
      of 4096 _shouldn't_ affect much as far as the kernel/file system
      goes, but making it bigger than 8192 can have severe consequences
      if you don't know what you're doing.  16394 worked for me, _BUT_
      when I went to 32768 and did an initdb, the SCSI driver broke and
      the partition that I was running under went to hell in a hand
      basket. Had to reboot and do a good bit of fsck'ing to fix things up.
      
      The patch can be safely applied though.  Just leave BLCKSZ = 8192
      and everything is as before.  It basically only cleans up all of the
      references to BLCKSZ in the code.
      
      If this patch is applied, a comment in the config.h file though above
      the BLCKSZ define with warning about monkeying around with it would
      be a good idea.
      
      Darren  darrenk@insightdist.com
      
      (Also cleans up some of the #includes in files referencing BLCKSZ.)
      ==========================================
      374bb5d2
  6. Jan 09, 1998
  7. Jan 07, 1998
  8. Jan 05, 1998
  9. Dec 16, 1997
  10. Dec 11, 1997
  11. Nov 25, 1997
  12. Nov 10, 1997
  13. Nov 09, 1997
  14. Nov 07, 1997
  15. Nov 02, 1997
  16. Oct 25, 1997
  17. Sep 18, 1997
  18. Sep 15, 1997
  19. Sep 08, 1997
  20. Sep 07, 1997
  21. Aug 19, 1997
  22. Aug 14, 1997
  23. Aug 12, 1997
  24. Aug 06, 1997
  25. Jul 29, 1997
  26. Jul 28, 1997
  27. Jul 24, 1997
  28. Apr 24, 1997
  29. Apr 23, 1997
  30. Feb 14, 1997
  31. Feb 12, 1997
    • Marc G. Fournier's avatar
      Patch from Massimo Dal Zotto <dz@cs.unitn.it> · fb70587c
      Marc G. Fournier authored
      The following patches add to the backend a new debugging flag -K which prints
      a debug trace of all locking operations on user relations (those with oid
      greater than 20000). The code is compiled only if LOCK_MGR_DEBUG is defined,
      so the patch should be harmless if not explicitly enabled.
      I'm using the code to trace deadlock conditions caused by application queries
      using the command "$POSTMASTER -D $PGDATA -o '-d 1 -K 1'.
      The patches are for version 6.0 dated 970126.
      fb70587c
  32. Feb 03, 1997
  33. Jan 27, 1997
  34. Jan 26, 1997
Loading