aboutsummaryrefslogtreecommitdiff
path: root/src/interfaces/libpq/fe-exec.c
Commit message (Collapse)AuthorAge
* Restructure the key include files per recent pghackers discussion: thereTom Lane2001-02-10
| | | | | | | | | | | are now separate files "postgres.h" and "postgres_fe.h", which are meant to be the primary include files for backend .c files and frontend .c files respectively. By default, only include files meant for frontend use are installed into the installation include directory. There is a new make target 'make install-all-headers' that adds the whole content of the src/include tree to the installed fileset, for use by people who want to develop server-side code without keeping the complete source tree on hand. Cleaned up a whole lot of crufty and inconsistent header inclusions.
* Now that I look at it, PQoidValue() ain't quite right either.Tom Lane2001-02-06
|
* Repair PQoidStatus() bug reported by darcy@druid.net.Tom Lane2001-02-06
|
* Change Copyright from PostgreSQL, Inc to PostgreSQL Global Development Group.Bruce Momjian2001-01-24
|
* Ensure that all uses of <ctype.h> functions are applied to unsigned-charTom Lane2000-12-03
| | | | | values, whether the local char type is signed or not. This is necessary for portability. Per discussion on pghackers around 9/16/00.
* Big warnings cleanup for Solaris/GCC. Down to about 40 now, butPeter Eisentraut2000-06-14
| | | | | | | | | | | 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.
* ! * Users doing non-blocking connections need to handle the resetBruce Momjian2000-05-25
| | | | | | | ! * themselves, they'll need to check the connection status if we ! * return an error. Alfred Perlstein
* Ye-old pgindent run. Same 4-space tabs.Bruce Momjian2000-04-12
|
* Repair unintentional damage to MULTIBYTE code.Tom Lane2000-03-14
|
* Change PQconndefaults() to return a malloc'd array, instead of a staticTom Lane2000-03-11
| | | | | | | | 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.
* Tweak libpq so that if a backend ERROR message arrives while libpqTom Lane2000-02-24
| | | | | | | | | | 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.
* Fixed psql double quoting of SQL idsPeter Eisentraut2000-02-07
| | | | Fixed libpq printing functions
* Add:Bruce Momjian2000-01-26
| | | | | | * Portions Copyright (c) 1996-2000, PostgreSQL, Inc to all files copyright Regents of Berkeley. Man, that's a lot of files.
* Remove Ops parameter from STATRELID cache lookup, for Tom Lane andBruce Momjian2000-01-24
| | | | optimizer.
* Libpq non-blocking mode, from Alfred PerlsteinBruce Momjian2000-01-18
|
* In the spirit of TODO itemBruce Momjian1999-11-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * 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
* Update frontend libpq to remove limits on query lengths,Tom Lane1999-08-31
| | | | | | | 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-19
|
* Re-add getopt.h check, remove NT-specific tests for it.Bruce Momjian1999-07-19
|
* Move some system includes into c.h, and remove duplicates.Bruce Momjian1999-07-17
|
* When closure of the backend connection is detected during pqFlush,Tom Lane1999-05-28
| | | | | | | | 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-25
|
* Fix bogus assumption that MAXALIGN is at least sizeof(pointer).Tom Lane1999-05-12
|
* Use MAXALIGN value found by configure instead of aTom Lane1999-04-04
| | | | hardwired assumption.
* Reversed out libpq protocol patch for Tom Lane.Bruce Momjian1999-03-14
|
* This is another example of why not allowing utility functions in SPIBruce Momjian1999-03-14
| | | | | | | | | | | | would be a Bad Thing. For what it's worth, I found another case in libpq where you can get a T message without a D that my utility patch needs to handle. I have attached the updated patch against the 6.4.2 version of src/interfaces/libpq/fe-exec.c Jerry Gay
* Hi,Bruce Momjian1999-03-14
| | | | | | | | | Just in case you'd like to see what I was talking about, I am attaching my patch to src/interfaces/libpq/fe-exec.c to prevent utility functions called from SPI from locking up the client. Jerry Gay
* Change my-function-name-- to my_function_name, and optimizer renames.Bruce Momjian1999-02-13
|
* Add PQresStatus() function to avoid direct access to pgresStatus[] array,Tom Lane1999-02-07
| | | | making life easier for Windoids...
* The libpq function PQfnumber does not handle case-insensitiveBruce Momjian1999-02-03
| | | | | | | | comparisons correctly. The psql monitor converts all table and field names to lower case. If the PQfnumber function is called with a mixed case name, it will always return -1. Bahman Rafatjoo
* Portability fix for old SunOS releases: realloc(NULL, ...)Tom Lane1998-11-29
| | | | doesn't work there.
* Performance improvement for libpq: avoid calling malloc separatelyTom Lane1998-11-18
| | | | for each field of each tuple. Makes more difference than you'd think...
* Update libpq to store an error message in PGresult, per pgsq-interfaces ↵Tom Lane1998-10-01
| | | | discussion of 21-Sep.
* Fix for length in libpq from Tom Lane.Bruce Momjian1998-09-10
|
* libpgtcl cleanups for Tom Lane.Bruce Momjian1998-09-04
|
* Attached is a patch to remove the definitions of libpq's internalBruce Momjian1998-09-03
| | | | | | | | | | | | | | | | | 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-01
|
* Renaming cleanup, no pgindent yet.Bruce Momjian1998-09-01
|
* libpq's pqGetnchar() should not return a null-terminated valueBruce Momjian1998-08-29
| | | | anymore. Fix for large objects.
* Date: Sun, 16 Aug 1998 14:56:48 -0400Marc G. Fournier1998-08-17
| | | | | | | | 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-09
| | | | | | | | | | | | | | | | | | | | | | | | | 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
* More updates for typmod int32 change. From Tom Lane.Bruce Momjian1998-07-14
|
* Inline function, rename libpq variablees, change lrel to lockrel.Bruce Momjian1998-07-13
|
* Rename libpq to use more normal field names.Bruce Momjian1998-07-13
|
* Fix libpq because it was reading from the backend as a short.Bruce Momjian1998-07-13
|
* From: Tom Lane <tgl@sss.pgh.pa.us>Marc G. Fournier1998-07-09
| | | | | | | | | | | | | | | | | | 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.
* Hello!Bruce Momjian1998-07-03
| | | | | | | | | | | | | | 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
* Hi, here are the patches to enhance existing MB handling. This timeBruce Momjian1998-06-16
| | | | | | | | | | | | | | | | 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
* Remove un-needed braces around single statements.Bruce Momjian1998-06-15
|
* Pass atttypmod to the frontend.Bruce Momjian1998-05-14
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-05 20:21:58 +0000