summaryrefslogtreecommitdiff
path: root/src/interfaces/libpq/fe-misc.c
Commit message (Collapse)AuthorAgeFilesLines
* Lots of patches coming in from me today :-)Bruce Momjian1999-09-271-4/+22
| | | | | | | | | | 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
* Patch to cure O(N^2) behavior in libpq when reading a longTom Lane1999-09-131-3/+25
| | | | | | message under a kernel that only returns one packet per recv() call. This didn't use to matter much, but it starts to get annoying with multi-megabyte EXPLAIN VERBOSE responses...
* Update frontend libpq to remove limits on query lengths,Tom Lane1999-08-311-37/+40
| | | | | | | 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...
* Enable WIN32 compilation of libpq.Bruce Momjian1999-07-191-2/+3
|
* Re-add getopt.h check, remove NT-specific tests for it.Bruce Momjian1999-07-191-11/+8
|
* Move some system includes into c.h, and remove duplicates.Bruce Momjian1999-07-171-3/+2
|
* When closure of the backend connection is detected during pqFlush,Tom Lane1999-05-281-9/+10
| | | | | | | | 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.
* pgindent run over code.Bruce Momjian1999-05-251-6/+8
|
* Final optimizer cleanups.Bruce Momjian1999-02-221-3/+3
|
* Fix memory leak from Tom Lane.Bruce Momjian1998-09-201-4/+35
|
* Attached is a patch to remove the definitions of libpq's internalBruce Momjian1998-09-031-5/+4
| | | | | | | | | | | | | | | | | 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.
* OK, folks, here is the pgindent output.Bruce Momjian1998-09-011-57/+64
|
* libpq's pqGetnchar() should not return a null-terminated valueBruce Momjian1998-08-291-5/+4
| | | | anymore. Fix for large objects.
* Date: Sun, 16 Aug 1998 14:56:48 -0400Marc G. Fournier1998-08-171-6/+19
| | | | | | | | 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>
* The attached patch implements some changes that were discussed aBruce Momjian1998-08-091-4/+12
| | | | | | | | | | | | | | | | | | | | | | | | | 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
* Hello!Bruce Momjian1998-07-031-1/+9
| | | | | | | | | | | | | | 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
* Remove un-needed braces around single statements.Bruce Momjian1998-06-151-3/+1
|
* Add sys/time.h to fe-misc.c, prevent pgtclsh from using old libaries,Bruce Momjian1998-05-121-1/+2
| | | | and allow CUSTOM_COPT to appear in compile AND LINK commands.
* Add missing includes.Bruce Momjian1998-05-071-1/+2
|
* It seems the regression tests don't cover copy in/out at all, soBruce Momjian1998-05-061-1/+19
| | | | | | | code that I had assumed was working had not been tested. Naturally, it was broken ... Tom Lane
* What I've done:Bruce Momjian1998-05-061-71/+390
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* pgindent run before 6.3 release, with Thomas' requested changes.Bruce Momjian1998-02-261-3/+3
|
* From: Phil Thompson <phil@river-bank.demon.co.uk>Marc G. Fournier1998-01-261-36/+12
| | | | | | | | | | | | | | | | | | | 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.
* Used modified version of indent that understands over 100 typedefs.Bruce Momjian1997-09-081-9/+9
|
* Another PGINDENT run that changes variable indenting and case label ↵Bruce Momjian1997-09-081-25/+25
| | | | indenting. Also static variable indenting.
* Massive commit to run PGINDENT on all *.c and *.h files.Bruce Momjian1997-09-071-108/+119
|
* om: "Martin J. Laubach" <mjl@CSlab.tuwien.ac.at>Marc G. Fournier1997-03-161-86/+77
| | | | | | | | | | | Subject: [HACKERS] Patch for io routines I am currently trying to improve on the front-backend communication routines; and noticed that lots of code are duplicated for libpq and the backend. This is a first patch that tries to share code between the two, more to follow. mjl
* Make error messages more explicit, PQtrace() output more readable.Bryan Henderson1996-12-311-9/+15
|
* shared build fails, but the rest compiles...formatting error in theMarc G. Fournier1996-11-031-1/+4
| | | | cc -shared, I believe...
* Fixes for:Marc G. Fournier1996-08-061-3/+4
| | | | | | | | | | | Here are a few minor fixes to Postgres95. Mostly I have added const to some of the char pointers. There was also a missing header file and a place where it looks like "==" was used when "=" was meant. I also changed some variables from Pfin and Pfout tp pfin and pfout because the latter shadow global variables and that just seems like an unsafe practice which I like to avoid. Submitted by: "D'Arcy J.M. Cain" <darcy@druid.druid.com>
* Postgres95 1.01 Distribution - Virgin SourcesPG95-1_01Marc G. Fournier1996-07-091-0/+193
View Lorry Controller Status