aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* New pgindent.Bruce Momjian1998-08-09
|
* cleanups.Bruce Momjian1998-08-09
|
* 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
* OPTIMIZER_DEBUG additions.Bruce Momjian1998-08-07
|
* Make large objects their own relkind type. Fix dups in pg_class_mbBruce Momjian1998-08-06
| | | | files. Fix sequence creation hack for relkind type.
* flowchart updateBruce Momjian1998-08-05
|
* flowchart updateBruce Momjian1998-08-05
|
* Fix for \d index display.Bruce Momjian1998-08-05
|
* From: David Hartwig <daybee@bellatlantic.net>Marc G. Fournier1998-08-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I have attached a patch to allow GROUP BY and/or ORDER BY function or expressions. Note worthy items: 1. The expression or function need not be in the target list. Example: SELECT name FROM foo GROUP BY lower(name); 2. Simplified the grammar to use expressions only. 3. Cleaned up earlier patch in this area to make use of existing utility functions. 3. Reduced some of the members in the SortGroupBy parse node. The original data members were redundant with the new expression node. (MUST do a "make clean" now) 4. Added a new parse node "JoinUsing". The JOIN USING clause was overloading this SortGroupBy structure. With the afore mentioned reduction of members, the two clauses lost all their commonality. 5. A bug still exist where, if a function or expression is GROUPed BY, and an aggregate function does not include a attribute from the expression or function, the backend crashes. (or something like that) The bug pre-dates this patch. Example: SELECT lower(a) AS lowcase, count(b) FROM foo GROUP BY lowcase; *** BOOM *** --Also when not in target list SELECT count(b) FROM foo GROUP BY lower(a); *** BOOM AGAIN ***
* From: Dr. Michael Meskes <meskes@online-club.de>Marc G. Fournier1998-08-05
| | | | So this should finally get cursors working. There was an ugly bug in it.
* OR processing cleanup.Bruce Momjian1998-08-04
|
* Add Indices display to \d command.Bruce Momjian1998-08-04
|
* Fix encoding grammer problem.Bruce Momjian1998-08-04
|
* MergeSort was sometimes called mergejoin and was confusing. NowBruce Momjian1998-08-04
| | | | it is now only mergejoin.
* EXPLAIN VERBOSE prints the plan, and now pretty-prints the plan toBruce Momjian1998-08-04
| | | | the postmaster log file.
* Make EXPLAIN show output more clearly.Bruce Momjian1998-08-04
|
* Update flow chart.Bruce Momjian1998-08-04
|
* Update mark/reset index code for multiple indexes, (OR code).Bruce Momjian1998-08-03
| | | | Thanks for Vadim for fixes.
* Fix typo in man pages.Bruce Momjian1998-08-03
|
* Cleanup of OR processing.Bruce Momjian1998-08-03
|
* Allows the following query to succeed: "SELECT NULL ORDER BY 1;"Thomas G. Lockhart1998-08-02
| | | | | | | | | | There are three or four cases in transformSortClause() and I had fixed only one case for UNION. A second case is now fixed, in the same way; I assigned INT4OID to the column type for the "won't actually happen" sort. Didn't want to skip the code entirely, since the backend needs to _try_ a sort to get the NULLs right. I'm not certain under what circumstances the other cases are invoked and these are not yet fixed up, though perhaps they don't need to be...
* Fix for OR handling with multiple indexes.Bruce Momjian1998-08-02
|
* run autoconfBruce Momjian1998-08-02
|
* Fix MULTIBYTE typo.Bruce Momjian1998-08-02
|
* Fix duplicate inside initdb.shBruce Momjian1998-08-01
|
* Cleanup of OR fix.Bruce Momjian1998-08-01
|
* Allow index use with OR clauses.Bruce Momjian1998-08-01
|
* Adrian Hall reported a problem to me that snprintf() doesn't exist in, atMarc G. Fournier1998-08-01
| | | | | | | | least, Solaris 2.5.1. We use it in backend/utils/adt/int8.c. Add a check to configure so that we see if it exists or not, and, if not, compile in snprintf.c from backend/port, which was taken from, and falls under the same Berkeley license as us, the FreeBSD libc/stdio ...
* Lmgr cleanup, new locking modes for LLL.Vadim B. Mikheev1998-08-01
|
* Matching clauses to functional indices was broken, now fixed.Vadim B. Mikheev1998-07-31
|
* Fix scan adjustment.Vadim B. Mikheev1998-07-30
|
* Use Snapshot in heap access methods.Vadim B. Mikheev1998-07-27
|
* Missed a few files in the last round of commits from Tatsuo, as wellMarc G. Fournier1998-07-27
| | | | as needed to run autoconf ...
* From: t-ishii@sra.co.jpMarc G. Fournier1998-07-26
| | | | | | | | | 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).
* I missed addding initdb.sh ...Marc G. Fournier1998-07-26
|
* Update flowchart. Add arrow.Bruce Momjian1998-07-26
|
* Fix compile error. Make transaction/work optional on all transactionBruce Momjian1998-07-26
| | | | | 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-25
|
* Add mention of actual SQL command to create*/destroy* commands.Bruce Momjian1998-07-24
|
* Add mention of SQL commands to create/destroy man pages.Bruce Momjian1998-07-24
|
* Add mention of psql and template1 to create*, destroy* commandBruce Momjian1998-07-24
| | | | manual pages.
* Fix HAVING patch missing cast.Bruce Momjian1998-07-24
|
* I'm sorry, but I think I introduced a little bug with my last patch.Bruce Momjian1998-07-24
| | | | | | | | | | | Everyone using an [NOT] EXISTS subquery will have noticed that already. The bug is in "subselect.c" in the function "SS_process_sublinks()". Here the whole function as it *SHOULD BE*: Stephan
* I really hope that I haven't missed anything in this one...Marc G. Fournier1998-07-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Version 06-30-0248Byron Nikolaidis1998-07-22
|
* Fix _lo_commit: core if LO memmory context was not created (LO were not used?)Vadim B. Mikheev1998-07-22
|
* VariableCache (next XID generator) is placed in shmem.Vadim B. Mikheev1998-07-21
|
* Update.Bruce Momjian1998-07-21
|
* Update.Bruce Momjian1998-07-21
|
* Theses buffer leaks are caused by indexes that are kept open betweenBruce Momjian1998-07-21
| | | | | | | | | | | | | | | | | | | | | calls. Outside a transaction, the backend detects them as buffer leaks; it sends a NOTICE, and frees them. This sometimes cause a segmentation fault (at least on Linux). These indexes are initialized on the first lo_read/lo_write/lo_tell call, and (normally) closed on a lo_close call. Thus the buffer leaks appear when lo direct access functions are used, and not with lo_import/lo_export functions (libpq version calls lo_close before ending the command, and the backend version uses another path). The included patches (against recent snapshot, and against 6.3.2) cause indexes to be closed on transaction end (that is on explicit 'END' statment, or on command termination outside trasaction blocks), thus preventing the buffer leaks while increasing performance inside transactions. Some (all?) 'classic' memory leaks are also removed. I hope it will be ok. --- Pascal ANDRE, graduated from Ecole Centrale Paris andre@via.ecp.fr
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-28 15:56:42 +0000