1. 29 Aug, 1998 1 commit
  2. 17 Aug, 1998 1 commit
    • Marc G. Fournier's avatar
      · 93120330
      Marc G. Fournier authored
      Date: Sun, 16 Aug 1998 14:56:48 -0400
      From: Tom Lane <tgl@sss.pgh.pa.us>
      Attached is a patch for this weekend's work on libpq.  I've dealt
      with several issues:
      
              <for details: see message, in pgsql-patches archive for above data>
      93120330
  3. 09 Aug, 1998 1 commit
    • Bruce Momjian's avatar
      · e6311b4a
      Bruce Momjian authored
      The attached patch implements some changes that were discussed a
      couple weeks ago on the hackers and interfaces lists:
      
      1. When the backend sends a NOTICE message and closes the connection
         (typically, because it was told to by the postmaster after
         another backend coredumped), libpq will now print the notice
         and close the connection cleanly.  Formerly, the frontend app
         would usually terminate ungracefully due to a SIGPIPE.  (I am
         not sure if 6.3.2 behaved that way, but the current cvs sources
         do...)
      
      2. libpq's various printouts to stderr are now fed through a single
         "notice processor" routine, which can be overridden by the
         application to direct notices someplace else.  This should ease
         porting libpq to Windows.
      
      I also noticed and fixed a problem in PQprint: when sending output
      to a pager subprocess, it would disable SIGPIPE in case the pager
      terminates early (this is good) --- but afterwards it reset SIGPIPE
      to SIG_DFL, rather than restoring the application's prior setting
      (bad).
      
      			regards, tom lane
      e6311b4a
  4. 14 Jul, 1998 1 commit
  5. 13 Jul, 1998 3 commits
  6. 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
  7. 03 Jul, 1998 1 commit
    • Bruce Momjian's avatar
      Hello! · c765b4b0
      Bruce Momjian authored
      Through some minor changes, I have been able to compile the libpq
      client libraries on the Win32 platform. Since the libpq communications
      part has been rewritten, this has become much easier. Enclosed is
      a patch that will allow at least Microsoft Visual C++ to compile
      libpq into both a static and a dynamic library.  I will take a look
      at porting the psql frontend as well, but I figured it was a good
      idea to send in these patches first - so no major changes are done
      to the files before it gets applied (if it does).
      
      Regards,
        Magnus Hagander
      c765b4b0
  8. 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
  9. 15 Jun, 1998 1 commit
  10. 14 May, 1998 1 commit
  11. 06 May, 1998 2 commits
    • Bruce Momjian's avatar
      It seems the regression tests don't cover copy in/out at all, so · 1c2d9cb6
      Bruce Momjian authored
      code that I had assumed was working had not been tested.  Naturally,
      it was broken ...
      
      Tom Lane
      1c2d9cb6
    • 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
  12. 29 Apr, 1998 1 commit
    • Marc G. Fournier's avatar
      From: Oliver Elphick <olly@lfix.co.uk> · a9ed49d5
      Marc G. Fournier authored
      If PQfn() receives NOTICEs from the backend, it fails because there is no
      provision to deal with them.
      
      This patch (supplied by Anders Hammarquist <iko@netg.se> to me as Debian
      maintainer of postgresql) cures the problem:
      a9ed49d5
  13. 15 Mar, 1998 1 commit
  14. 26 Feb, 1998 1 commit
  15. 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
  16. 23 Dec, 1997 1 commit
  17. 05 Dec, 1997 1 commit
  18. 04 Dec, 1997 1 commit
  19. 01 Dec, 1997 2 commits
  20. 10 Nov, 1997 1 commit
  21. 03 Nov, 1997 1 commit
  22. 08 Sep, 1997 2 commits
  23. 07 Sep, 1997 1 commit
  24. 05 Sep, 1997 1 commit
  25. 27 Aug, 1997 1 commit
  26. 12 Jul, 1997 1 commit
  27. 01 Jun, 1997 3 commits
    • Marc G. Fournier's avatar
      From: Igor <igor@sba.miami.edu> · 9a5529f4
      Marc G. Fournier authored
      Subject: [PATCHES] memory leak patches in libpq and psql
      
      A couple of small memory leak patches (detected with Purify) primarily
      in libpq.
      
      * Fixed (NULL) border problem in psql (run psql, do \m, then select
        something from a table...row separators will be nulls)
      * Fixed memory leak with the abovementioned border not being freed
        properly.
      * Fixed memory leak in freePGconn() not freeing conn->port
      * Fixed up PQclear() to free parts of PGresult only if these
        parts are not null.
      * Fixed a decent memory leak that occured after executing every command
        in psql. PGresult *results was not freed most of the time.
      
      There is still a leak being detected (2 bytes) in readline functions, but
      I think this is old readline library. I will install new one and test it.
      9a5529f4
    • Bruce Momjian's avatar
      Added \n to error message. · d9557276
      Bruce Momjian authored
      d9557276
    • Bruce Momjian's avatar
      35717aa2
  28. 20 May, 1997 1 commit
  29. 24 Jan, 1997 1 commit
    • Marc G. Fournier's avatar
      Remove from include/config.h: · cfe18a8e
      Marc G. Fournier authored
      #if defined(aix)
      #define TERMIOS_H_LOCATION <termios.h>
      #else
      #define TERMIOS_H_LOCATION <sys/termios.h>
      #endif
      
      libpq/fe-exec.c modified so that location of termios.h is determined
      by whether HAVE_TERMIOS_H is defined or not, in preparation for switch
      to configure
      cfe18a8e
  30. 08 Jan, 1997 1 commit
    • Marc G. Fournier's avatar
      From: wieck@sapserv.debis.de · 389e336c
      Marc G. Fournier authored
      Hi,
      
          counting the empty dummy queries in libpq isn't everything.
          If the backend sends an error, the I returns from the dummies
          still come. So we must eat them up in any case, not just
          returning on the occurence of an E reply.
      
      Until later, Jan
      389e336c
  31. 31 Dec, 1996 1 commit
  32. 28 Dec, 1996 1 commit
  33. 26 Dec, 1996 1 commit