1. 26 Jul, 1998 1 commit
    • Marc G. Fournier's avatar
      · 5979d738
      Marc G. Fournier authored
      From: t-ishii@sra.co.jp
      
      As Bruce mentioned, this is due to the conflict among changes we made.
      Included patches should fix the problem(I changed all MB to
      MULTIBYTE). Please let me know if you have further problem.
      
      P.S. I did not include pathces to configure and gram.c to save the
      file size(configure.in and gram.y modified).
      5979d738
  2. 18 Jul, 1998 1 commit
  3. 09 Jul, 1998 1 commit
    • Marc G. Fournier's avatar
      · a0659e3e
      Marc G. Fournier authored
      From: Tom Lane <tgl@sss.pgh.pa.us>
      
      Making PQrequestCancel safe to call in a signal handler turned out to be
      much easier than I feared.  So here are the diffs.
      
      Some notes:
        * I modified the postmaster's packet "iodone" callback interface to allow
          the callback routine to return a continue-or-drop-connection return
          code; this was necessary to allow the connection to be closed after
          receiving a Cancel, rather than proceeding to launch a new backend...
          Being a neatnik, I also made the iodone proc have a typechecked
          parameter list.
        * I deleted all code I could find that had to do with OOB.
        * I made some edits to ensure that all signals mentioned in the code
          are referred to symbolically not by numbers ("SIGUSR2" not "2").
          I think Bruce may have already done at least some of the same edits;
          I hope that merging these patches is not too painful.
      a0659e3e
  4. 27 Jun, 1998 1 commit
  5. 16 Jun, 1998 1 commit
    • Bruce Momjian's avatar
      Hi, here are the patches to enhance existing MB handling. This time · cb7cbc16
      Bruce Momjian authored
      I have implemented a framework of encoding translation between the
      backend and the frontend. Also I have added a new variable setting
      command:
      
      SET CLIENT_ENCODING TO 'encoding';
      
      Other features include:
      	Latin1 support more 8 bit cleaness
      
      See doc/README.mb for more details. Note that the pacthes are
      against May 30 snapshot.
      
      Tatsuo Ishii
      cb7cbc16
  6. 15 Jun, 1998 1 commit
  7. 09 Jun, 1998 1 commit
  8. 08 Jun, 1998 1 commit
  9. 04 Jun, 1998 1 commit
  10. 29 May, 1998 1 commit
  11. 27 May, 1998 1 commit
  12. 26 May, 1998 1 commit
  13. 19 May, 1998 1 commit
  14. 06 May, 1998 1 commit
    • Bruce Momjian's avatar
      What I've done: · edbd5139
      Bruce Momjian authored
      1. Rewritten libpq to allow asynchronous clients.
      
      2. Implemented client side of cancel protocol in library,
         and patched psql.c to send a cancel request upon SIGINT.  The
         backend doesn't notice it yet :-(
      
      3. Implemented 'Z' protocol message addition and renaming of
         copy in/out start messages.  These are implemented conditionally,
         ie, the client protocol version is checked; so the code should
         still work with 1.0 clients.
      
      4. Revised protocol and libpq sgml documents (don't have an SGML
         compiler, though, so there may be some markup glitches here).
      
      
      What remains to be done:
      
      1. Implement addition of atttypmod field to RowDescriptor messages.
         The client-side code is there but ifdef'd out.  I have no idea
         what to change on the backend side.  The field should be sent
         only if protocol >= 2.0, of course.
      
      2. Implement backend response to cancel requests received as OOB
         messages.  (This prolly need not be conditional on protocol
         version; just do it if you get SIGURG.)
      
      3. Update libpq.3.  (I'm hoping this can be generated mechanically
         from libpq.sgml... if not, will do it by hand.)  Is there any
         other doco to fix?
      
      4. Update non-libpq interfaces as necessary.  I patched libpgtcl
         so that it would compile, but haven't tested it.  Dunno what
         needs to be done with the other interfaces.
      
      Have at it!
      
      Tom Lane
      edbd5139
  15. 26 Feb, 1998 1 commit
  16. 24 Feb, 1998 1 commit
    • Marc G. Fournier's avatar
      From: "Denis V. Dmitrienko" <denis@null.net> · 0227a4e1
      Marc G. Fournier authored
      What it does:
      It solves stupid problem with cyrillic charsets IP-based on-fly recoding.
      take a look at /data/charset.conf for details.
      You can use any tables for any charset.
      Tables are from Russian Apache project.
      Tables in this patch contains also Ukrainian characters.
      
      Then run ./configure --enable-recode
      0227a4e1
  17. 02 Feb, 1998 1 commit
  18. 01 Feb, 1998 1 commit
  19. 26 Jan, 1998 1 commit
    • 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
  20. 25 Jan, 1998 1 commit
  21. 13 Jan, 1998 1 commit
    • 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
  22. 09 Jan, 1998 1 commit
  23. 07 Jan, 1998 1 commit
  24. 05 Jan, 1998 1 commit
  25. 16 Dec, 1997 1 commit
  26. 11 Dec, 1997 1 commit
  27. 25 Nov, 1997 1 commit
  28. 10 Nov, 1997 1 commit
  29. 09 Nov, 1997 1 commit
  30. 07 Nov, 1997 1 commit
  31. 02 Nov, 1997 1 commit
  32. 25 Oct, 1997 1 commit
  33. 18 Sep, 1997 3 commits
  34. 15 Sep, 1997 1 commit
  35. 08 Sep, 1997 2 commits
  36. 07 Sep, 1997 1 commit
  37. 19 Aug, 1997 1 commit