summaryrefslogtreecommitdiff
path: root/src/bin/psql
Commit message (Collapse)AuthorAgeFilesLines
* From: Tatsuo Ishii <t-ishii@sra.co.jp>Marc G. Fournier1999-02-211-2/+2
| | | | | | Ok. I made patches replacing all of "#if FALSE" or "#if 0" to "#ifdef NOT_USED" for current. I have tested these patches in that the postgres binaries are identical.
* Change my-function-name-- to my_function_name, and optimizer renames.Bruce Momjian1999-02-134-8/+8
|
* Allow psql to do \p\g. Ingres does it, why not us?Bruce Momjian1999-02-071-17/+40
|
* Cleanup of source files where 'return' or 'var =' is alone on a line.Bruce Momjian1999-02-031-3/+2
|
* Included patches make some enhancements to the multi-byte support.Bruce Momjian1999-02-021-2/+2
| | | | | | | | | | | | | | | | | | | o allow to use Big5 (a Chinese encoding used in Taiwan) as a client encoding. In this case the server side encoding should be EUC_TW o add EUC_TW and Big5 test cases to the regression and the mb test (contributed by Jonah Kuo) o fix mistake in include/mb/pg_wchar.h. An encoding id for EUC_TW was not correct (was 3 and now is 4) o update documents (doc/README.mb and README.mb.jp) o update psql helpfile (bin/psql/psqlHelp.h) -- Tatsuo Ishii t-ishii@sra.co.jp
* psql help fix.Bruce Momjian1999-02-021-2/+2
|
* Fix for psql help create table.Bruce Momjian1999-02-021-3/+3
|
* Add TEMP tables/indexes. Add COPY pfree(). Other cleanups.Bruce Momjian1999-02-021-3/+3
|
* From: Tatsuo Ishii <t-ishii@sra.co.jp>Marc G. Fournier1999-01-271-2/+3
| | | | | | Included patches fix a portability problem of unsetenv() used in 6.4.2 multi-byte support. unsetenv() is only avaliable on FreeBSD and Linux so I decided to replace with putenv().
* Apply Win32 patch from Horak Daniel.Bruce Momjian1999-01-172-4/+31
|
* Current multi-byte related codes have a bug with SQL_ASCIIBruce Momjian1998-12-141-1/+22
| | | | | | | | | | | support. Included patches will solve it and should be applied to both trees. Also, it fix the problem with \c command of psql when switching different encoding databases. Regression tests passed. -- Tatsuo Ishii t-ishii@sra.co.jp
* Portability fixes found needed for SunOS 4.1.x:Tom Lane1998-11-301-2/+2
| | | | | | SunOS has tas(), but not memmove or strerror, and its sprintf() doesn't return int. Also, older versions of GNU Make don't like rules with empty left-hand sides...
* Additional fixes for mixed-case table names from Billy Allie.Thomas G. Lockhart1998-11-171-3/+8
|
* Get rid of some minor compiler warnings.Tom Lane1998-10-261-5/+5
|
* New QUERY_LIMIT set command.Bruce Momjian1998-10-141-6/+8
|
* I continue my quest to eliminate documentation that claimsTom Lane1998-10-081-7/+7
| | | | a listen/notify condition name is a class or table name, 'cause it ain't.
* Hello!Bruce Momjian1998-10-081-13/+1
| | | | | | | | | | | | | | | | | | | Here are two new patches for the Win32 support. 1) The patch based on the one from Hiroshi Inoue [Inoue@tpf.co.jp], to load Winsock.dll from libpq.dll. 2) A patch for psql.c to remove the call to WSAStartup(), since it is not required when it's done in libpq.dll. I'm still looking for the possibility of having a crypt() function in libpq.dll too, the same way getopt was included. Any chance of getting this before 6.4, or should we wait for the next one? //Magnus
* Here are the patches against the current source tree. I have run theBruce Momjian1998-10-061-0/+8
| | | | | | | | | | | | | | regression test on a FreeBSD box with both non-MULTIBYTE and MULTIBYTE-enabled, and confirmed that the results are same. However I do not tested on PCs(I don't have access to win). Please let me know if the patches break anything on PCs. Also please note that the patch for varchar.c is a fix for a nasty bug of char(n) types that I introduced and I believe at least this should be applied. Tatsuo Ishii
* Fix for \z formatting from Tom Lane.Bruce Momjian1998-09-211-9/+49
|
* patch cleanups.Bruce Momjian1998-09-031-2/+2
|
* Remove \r\n in windows makefile.Bruce Momjian1998-09-031-64/+64
|
* Attached is a patch to remove the definitions of libpq's internalBruce Momjian1998-09-031-19/+16
| | | | | | | | | | | | | | | | | 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-014-110/+120
|
* Hello!Bruce Momjian1998-08-291-8/+13
| | | | | | | | | | | | | | | | | | Here is a new patch for libpq, to make it work on Win32 again (since the latest modifications broke it a little). Please also add the file "libpq.rc" to the interfaces/libpq directory. This will allow version-stamping of the generated DLL file, so that automatic install programs (and interested users) can determine the version of the file. The file is currently set as "prerelease". Before the release, somebody should change the line "FILEFLAGS VS_FF_PRERELEASE" to "FILEFLAGS 0". That information should probably go into toos\RELEASE_CHANGES. The patch is against the cvs as of ~ 1998-08-26 14:30 CEST. //Magnus
* Hi all,Bruce Momjian1998-08-281-2/+2
| | | | | | | | | | | | | | | | | | | | | | | I don't know if this is really related to the initdb problem discussion (haven't followed it enough). But seems so because it fixes a damn problem during index tuple insertion on CREATE TABLE into pg_attribute_relid_attnum_index. Anyway - this bug was really hard to find. During startup the relcache reads in some prepared information about index strategies from a file and then reinitializes the function pointers inside the scanKey data. But for sake it assumed single attribute index tuples (hasn't that changed recently). Thus not all the strategies scanKey entries where initialized properly, resulting in invalid addresses for the btree comparision functions. With the patch at the end the regression tests passed excellent except for the sanity_check that crashed at vacuum and the misc test where the select unique1 from onek2 outputs the two rows in different order. Jan
* From: Magnus Hagander <mha@edu.sollentuna.se>Marc G. Fournier1998-08-272-3/+104
| | | | | | | | | Ok. Here is a patch to make psql work on Win32 (as a console mode application, of course). It requires getopt.c to be in src/utils - works fine with the FreeBSD version of it. Also, the file win32.mak should go into src/bin/psql.
* From: Massimo Dal Zotto <dz@cs.unitn.it>Marc G. Fournier1998-08-251-4/+8
| | | | | | | > these patches define the UNLISTEN sql command. The code already > existed but it was unknown to the parser. Now it can be used > like the listen command. > You must make clean and delete gram.c and parser.h before make.
* With the attached patch, I have verified that long (> 8char anyway)Bruce Momjian1998-08-221-99/+24
| | | | | | | | | | | | | | | | | | | | | usernames and passwords work correctly in both "password" and "crypt" authorization mode. NOTE: at least on my machine, it seems that the crypt() routines ignore the part of the password beyond 8 characters, so there's no security gain from longer passwords in crypt auth mode. But they don't fail. The login-related part of psql has apparently not been touched since roughly the fall of Rome ;-). It was going through huge pushups to get around the lack of username/login parameters to PQsetdb. I don't know when PQsetdbLogin was added to libpq, but it's there now ... so I was able to rip out quite a lot of crufty code while I was at it. It's possible that there are still bogus length limits on username or password in some of the other PostgreSQL user interfaces besides psql/libpq. I will leave it to other folks to check that code. regards, tom lane
* Date: Sun, 16 Aug 1998 14:56:48 -0400Marc G. Fournier1998-08-171-14/+15
| | | | | | | | 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>
* Add new \w write command to psql.Bruce Momjian1998-08-101-37/+61
|
* Make large objects their own relkind type. Fix dups in pg_class_mbBruce Momjian1998-08-061-3/+1
| | | | files. Fix sequence creation hack for relkind type.
* Fix for \d index display.Bruce Momjian1998-08-051-3/+3
|
* Add Indices display to \d command.Bruce Momjian1998-08-041-8/+39
|
* From: t-ishii@sra.co.jpMarc G. Fournier1998-07-261-3/+3
| | | | | | | | | 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).
* Fix compile error. Make transaction/work optional on all transactionBruce Momjian1998-07-262-66/+120
| | | | | statements. More cleanups of psql help. Fix for shift/reduce on UNION in subselect.
* Update psql help syntax to remove <> and uppercaese keywords.Bruce Momjian1998-07-251-151/+140
|
* I really hope that I haven't missed anything in this one...Marc G. Fournier1998-07-241-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | From: t-ishii@sra.co.jp Attached are patches to enhance the multi-byte support. (patches are against 7/18 snapshot) * determine encoding at initdb/createdb rather than compile time Now initdb/createdb has an option to specify the encoding. Also, I modified the syntax of CREATE DATABASE to accept encoding option. See README.mb for more details. For this purpose I have added new column "encoding" to pg_database. Also pg_attribute and pg_class are changed to catch up the modification to pg_database. Actually I haved added pg_database_mb.h, pg_attribute_mb.h and pg_class_mb.h. These are used only when MB is enabled. The reason having separate files is I couldn't find a way to use ifdef or whatever in those files. I have to admit it looks ugly. No way. * support for PGCLIENTENCODING when issuing COPY command commands/copy.c modified. * support for SQL92 syntax "SET NAMES" See gram.y. * support for LATIN2-5 * add UNICODE regression test case * new test suite for MB New directory test/mb added. * clean up source files Basic idea is to have MB's own subdirectory for easier maintenance. These are include/mb and backend/utils/mb.
* Add auto-size to screen to \d? commands. Use UNION to show allBruce Momjian1998-07-182-179/+239
| | | | | \d? results in one query. Add \d? field search feature. Rename MB to MULTIBYTE.
* add mention of DISTINCT ON attrNBruce Momjian1998-07-121-5/+5
|
* From: Tom Lane <tgl@sss.pgh.pa.us>Marc G. Fournier1998-07-091-9/+23
| | | | | | | | | | | | | | | | | | 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.
* Hi, here are the patches to enhance existing MB handling. This timeBruce Momjian1998-06-163-7/+68
| | | | | | | | | | | | | | | | 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-151-29/+1
|
* Fix macros that were not properly surrounded by parens or braces.Bruce Momjian1998-06-151-5/+5
|
* Another \f\ fix for psql.Bruce Momjian1998-05-151-3/+11
|
* Fix to allow \f \ to make spaces as delimiter.Bruce Momjian1998-05-132-3/+14
|
* The attached patch corrects two problems with autoconfiguration ofBruce Momjian1998-05-121-2/+5
| | | | | | | | | | | | | | | | psql in Postgres 6.3.2. Both of these problems were complained of recently in pgsql-questions: 1. In the right circumstances, psql.c will fail to compile due to trying to include a nonexistent <history.h>. (Thread "Compile-time error" around 17 Apr 98.) 2. In other circumstances, psql will compile but does not provide command history capability, even though the underlying readline library supports it. (Various threads, most recently "query repetition in psql" around 29 Apr.) Tom Lane
* Give proper error on psql \copy use.Bruce Momjian1998-05-121-2/+8
|
* What I've done:Bruce Momjian1998-05-061-4/+46
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Fix for missing parens with \g causing psql to get completelyBruce Momjian1998-05-041-1/+4
| | | | confused.
* DESTDIR removed, again.Bruce Momjian1998-04-061-2/+2
|
View Lorry Controller Status