1. 06 Feb, 2001 2 commits
  2. 24 Jan, 2001 1 commit
  3. 03 Dec, 2000 1 commit
  4. 14 Jun, 2000 1 commit
    • Peter Eisentraut's avatar
      Big warnings cleanup for Solaris/GCC. Down to about 40 now, but · 44d1abeb
      Peter Eisentraut authored
      we'll get there one day.
      
      Use `cat' to create aclocal.m4, not `aclocal'. Some people don't
      have automake installed.
      
      Only run the autoconf rule in the top-level GNUmakefile if the
      invoker specified `make configure', don't run it automatically
      because of CVS timestamp skew.
      44d1abeb
  5. 25 May, 2000 1 commit
  6. 12 Apr, 2000 1 commit
  7. 14 Mar, 2000 1 commit
  8. 11 Mar, 2000 1 commit
    • Tom Lane's avatar
      Change PQconndefaults() to return a malloc'd array, instead of a static · a71daab4
      Tom Lane authored
      array.  This allows processing of conninfo strings to be made thread-safe,
      at the cost of a small memory leak in applications that use
      PQconndefaults() and are not updated to free the returned array via
      the new PQconninfoFree() function.  But PQconndefaults() is probably not
      used very much, so this seems like a good compromise.
      a71daab4
  9. 24 Feb, 2000 1 commit
    • Tom Lane's avatar
      Tweak libpq so that if a backend ERROR message arrives while libpq · 58f481c4
      Tom Lane authored
      thinks the connection is idle, the error message is displayed as if
      it were a NOTICE.  This seems better than dropping the message on
      the floor ... particularly if the message is the backend telling us
      why it's about to close the connection.  The previous behavior was
      Backend message type 0x45 arrived while idle
      pqReadData() -- backend closed the channel unexpectedly.
      which is not real helpful.
      58f481c4
  10. 07 Feb, 2000 1 commit
  11. 26 Jan, 2000 1 commit
    • Bruce Momjian's avatar
      Add: · 5c25d602
      Bruce Momjian authored
        * Portions Copyright (c) 1996-2000, PostgreSQL, Inc
      
      to all files copyright Regents of Berkeley.  Man, that's a lot of files.
      5c25d602
  12. 24 Jan, 2000 1 commit
  13. 18 Jan, 2000 1 commit
  14. 11 Nov, 1999 1 commit
    • Bruce Momjian's avatar
      In the spirit of TODO item · 2a24ec6f
      Bruce Momjian authored
      * Add use of 'const' for varibles in source tree
      (which is misspelled, btw.)
      I went through the front-end libpq code and did so. This affects in
      particular the various accessor functions (such as PQdb() and
      PQgetvalue()) as well as, by necessity, the internal helpers they use.
      
      I have been really thorough in that regard, perhaps some people will find
      it annoying that things like
      char * foo = PQgetvalue(res, 0, 0)
      will generate a warning. On the other hand it _should_ generate one. This
      is no real compatibility break, although a few clients will have to be
      fixed to suppress warnings. (Which again would be in the spirit of the
      above TODO.)
      
      In addition I replaced some int's by size_t's and removed some warnings
      (and generated some new ones -- grmpf!). Also I rewrote PQoidStatus (so it
      actually honors the const!) and supplied a new function PQoidValue that
      returns a proper Oid type. This is only front-end stuff, none of the
      communicaton stuff was touched.
      
      
      The psql patch also adds some new consts to honor the new libpq situation,
      as well as fixes a fatal condition that resulted when using the -V
      (--version) option and there is no database listening.
      
      
      So, to summarize, the psql you should definitely put in (with or without
      the libpq). If you think I went too far with the const-mania in libpq, let
      me know and I'll make adjustments. If you approve it, I will also update
      the docs.
      
              -Peter
      
      --
      Peter Eisentraut                  Sernanders vaeg 10:115
      2a24ec6f
  15. 31 Aug, 1999 1 commit
    • Tom Lane's avatar
      Update frontend libpq to remove limits on query lengths, · ab5cafa5
      Tom Lane authored
      error/notice message lengths, and number of fields per tuple.  Add
      pqexpbuffer.c/.h, a frontend version of backend's stringinfo module.
      This is first step in applying Mike Ansley's long-query patches,
      even though he didn't do any of these particular changes...
      ab5cafa5
  16. 19 Jul, 1999 2 commits
  17. 17 Jul, 1999 1 commit
  18. 28 May, 1999 1 commit
    • Tom Lane's avatar
      When closure of the backend connection is detected during pqFlush, · f0ae1e8d
      Tom Lane authored
      do the right thing: look for a NOTICE message from the backend before we
      close our side of the socket.  6.4 libpq did not reliably print the backend's
      hara-kiri message, 'The Postmaster has informed me ...', because it only
      did the right thing if connection closure was detected during a read
      attempt instead of a write attempt.
      f0ae1e8d
  19. 25 May, 1999 1 commit
  20. 12 May, 1999 1 commit
  21. 04 Apr, 1999 1 commit
  22. 14 Mar, 1999 3 commits
  23. 13 Feb, 1999 1 commit
  24. 07 Feb, 1999 1 commit
  25. 03 Feb, 1999 1 commit
  26. 29 Nov, 1998 1 commit
  27. 18 Nov, 1998 1 commit
  28. 01 Oct, 1998 1 commit
  29. 10 Sep, 1998 1 commit
  30. 04 Sep, 1998 1 commit
  31. 03 Sep, 1998 1 commit
    • Bruce Momjian's avatar
      Attached is a patch to remove the definitions of libpq's internal · f71d0cf6
      Bruce Momjian authored
      structs from libpq-fe.h, as we previously discussed.
      
      There turned out to be sloppy coding practices in more places than
      I had realized :-(, but all in all I think it was a well-worth-while
      exercise.
      
      I ended up adding several routines to libpq's API in order to respond
      to application requirements that were exposed by this work.  I owe the
      docs crew updates for libpq.sgml to describe these changes.  I'm way too
      tired to work on the docs tonight, however.
      
      This is the last major change I intend to submit for 6.4.  I do want
      to see if I can make libpgtcl work with Tcl 8.0 before we go final,
      but hopefully that will be a minor bug fix.
      f71d0cf6
  32. 01 Sep, 1998 2 commits
  33. 29 Aug, 1998 1 commit
  34. 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
  35. 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