aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* Another SELECT speedup: extract OIDs of column print functionsTom Lane1999-01-27
| | | | | only once per SELECT, not once per tuple. 10% here, 10% there, pretty soon you're talking about real speedups ...
* More agg cleanup.Bruce Momjian1999-01-26
|
* primary key support cleanups from D'Arcy...Marc G. Fournier1999-01-26
|
* pgindent file.Bruce Momjian1999-01-26
|
* From: Peter T Mount <peter@retep.org.uk>Marc G. Fournier1999-01-25
| | | | | | | | | This implements some of the JDBC2 methods, fixes a bug introduced into the JDBC1 portion of the driver, and introduces a new example, showing how to use the CORBA ORB thats in Java2 with JDBC. The Tar file contains the new files, the diff the changes to the others. CHANGELOG is separate as I forgot to make a .orig ;-)
* Agg/Aggreg cleanup and datetime.sql patch.Bruce Momjian1999-01-25
|
* SELECT FOR UPDATE is implemented...Vadim B. Mikheev1999-01-25
|
* Tighten coding of fmgr_isbuiltin() ... managed to speed it upTom Lane1999-01-25
| | | | by about 10% which seems to be good for half a percent or so of a SELECT.
* Tighten coding of inner loops in nocachegetattr ...Tom Lane1999-01-24
| | | | seems to have improved speed of routine by 5% or so ...
* Use heap_attisnull, rather than heap_getattr, for a smallTom Lane1999-01-24
| | | | but useful speedup.
* Replace typtoout() and gettypelem() with a single routine,Tom Lane1999-01-24
| | | | | | so that fetching an attribute value needs only one SearchSysCacheTuple call instead of two redundant searches. This speeds up a large SELECT by about ten percent, and probably will help GROUP BY and SELECT DISTINCT too.
* Fix a couple little problems with signed vs. unsignedTom Lane1999-01-24
| | | | characters ...
* Rename Aggreg to Aggref.Bruce Momjian1999-01-24
|
* Improper addition of NaN/Infinity recognition to float8in()Tom Lane1999-01-24
| | | | | | | was causing it not to detect out-of-range float values, as evidenced by failure of float8 regression test. I corrected that logic and also modified expected float8 results to account for new error message generated for out-of-range inputs.
* Remove unused Choose node.Bruce Momjian1999-01-23
|
* Add explicit buffering in backend libpq, to compensate forTom Lane1999-01-23
| | | | buffering lost by not going through stdio anymore for client I/O.
* Fix unportable test syntax in regression script.Tom Lane1999-01-23
|
* Fix for intersect FOR UPDATE check.Bruce Momjian1999-01-22
|
* Relcache Size fix.Bruce Momjian1999-01-22
|
* Fix for Size sizeof in cache code.Bruce Momjian1999-01-22
|
* |From: "D'Arcy" "J.M." Cain <darcy@druid.net>Marc G. Fournier1999-01-22
| | | | | | | |The following patch just prevents a warning from being generated because |the data type isn't specified.
* It seems that SPI_prepare() doesn't work well in some cases.Bruce Momjian1999-01-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Pawel Pierscionek [pawel@astercity.net] reported about the following case 1([SQL] drop table in pgsql). Michael Contzen [mcontzen@dohle.com] reported about the following case 2(PL/PGSQL bug using aggregates). You can find it from pgsql-hackers archive. 1. PL/pgSQL can't execute UTILITY commands. SPI_prepare() doesn't copy(save) the utilityStmt member of Query type nodes,because copyObject() is not implemented for nodes of (Create/Destroy etc)Stmt type. 2. Aggregates in PL/pgSQL cause wrong results. ... It's a list including Aggreg type nodes which exist in TargetList(i.e Aggreg type nodes are common to aggs member list and TargetList). AFAIC the common pointer is not copied to the same pointer by copyObject() function. In my patch I reconstruct aggs member node from new(copied) Agg type node. Is it proper to use set_agg_tlist_references() function to reconstruct aggs member node for Agg type nodes ? Thanks. Hiroshi Inoue Inoue@tpf.co.jp
* Here is a new version of my patch for allowing pg_dump to DROP schemaBruce Momjian1999-01-21
| | | | | | | | | | | | | | | | | | | elements prior to CREATEing new ones. It is under control of the -c command line option (with the default being status quo). The DROP TRIGGER portion still needs implementation. Anyone able to help clarify what exactly the CREATE TRIGGER portion does so I can fix this? Again, I have tried this with tables/indexes/sequences, but do not have other schema elements in my database. As a result, I am not 100% convinced that I got the syntax correct in all cases (but think I did, nonetheless). If anyone can check the other cases, I'd appreciate it. Cheers, Brook [I added manual page and sgml additions for the new -c option.]
* The following patch finishes primary key support. Previously, whenBruce Momjian1999-01-21
| | | | | | | | | | | | | | | | | | | | a field was labelled as a primary key, the system automatically created a unique index on the field. This patch extends it so that the index has the indisprimary field set. You can pull a list of primary keys with the followiing select. SELECT pg_class.relname, pg_attribute.attname FROM pg_class, pg_attribute, pg_index WHERE pg_class.oid = pg_attribute.attrelid AND pg_class.oid = pg_index.indrelid AND pg_index.indkey[0] = pg_attribute.attnum AND pg_index.indisunique = 't'; There is nothing in this patch that modifies the template database to set the indisprimary attribute for system tables. Should they be changed or should we only be concerned with user tables? D'Arcy
* From: Michael Meskes <Michael.Meskes@usa.net>Marc G. Fournier1999-01-21
| | | | See attached file. Now accepts "exec sql whenever sqlwarning".
* Copy RowMark node (it's for (-:)) FOR UPDATE).Vadim B. Mikheev1999-01-21
|
* FOR UPDATE is in parser & rules.Vadim B. Mikheev1999-01-21
|
* Update gram.c.Bruce Momjian1999-01-20
|
* Add Intersect check.Bruce Momjian1999-01-20
|
* Fix "Y-2K" problem with two-digit BC dates being corrected by two millenia.Thomas G. Lockhart1999-01-20
| | | | | | They are not corrected now. Allow the date type to accept BC dates. Share more date/time validation declarations through dt.h.
* Clean up leap year support and date/time validation.Thomas G. Lockhart1999-01-20
| | | | Move declarations to allow sharing between modules.
* Add a set of braces to clarify conditional nesting.Thomas G. Lockhart1999-01-20
| | | | gcc complained about ambiguities.
* Okay, I've updated the ecpg parser yet again. Unfortunately it has oneBruce Momjian1999-01-18
| | | | | | | | | | | | | | | | | | remaining shift/reduce conflict. But the very same conflict is in gram.y, so I don't dig into it very much now. Anyway, I just saw that there were minor changes made to ecpg by others. Now I like that but I would prefer if I was told about that. Otherwise my version numbering and Changelog maintaining might break. Or simply change these too. :-) Also I had to add #include <errno.h> to backend/libpq/pqcomprim.c to be able to compile postgresql. Patch is attached. Since my resubscription process is still not finished yet, I still send them here. Michael
* Add missing Windows files.Bruce Momjian1999-01-18
|
* Fix cfor typos.Bruce Momjian1999-01-18
|
* Fix for typo in gram.yBruce Momjian1999-01-18
|
* Hi!Bruce Momjian1999-01-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | INTERSECT and EXCEPT is available for postgresql-v6.4! The patch against v6.4 is included at the end of the current text (in uuencoded form!) I also included the text of my Master's Thesis. (a postscript version). I hope that you find something of it useful and would be happy if parts of it find their way into the PostgreSQL documentation project (If so, tell me, then I send the sources of the document!) The contents of the document are: -) The first chapter might be of less interest as it gives only an overview on SQL. -) The second chapter gives a description on much of PostgreSQL's features (like user defined types etc. and how to use these features) -) The third chapter starts with an overview of PostgreSQL's internal structure with focus on the stages a query has to pass (i.e. parser, planner/optimizer, executor). Then a detailed description of the implementation of the Having clause and the Intersect/Except logic is given. Originally I worked on v6.3.2 but never found time enough to prepare and post a patch. Now I applied the changes to v6.4 to get Intersect and Except working with the new version. Chapter 3 of my documentation deals with the changes against v6.3.2, so keep that in mind when comparing the parts of the code printed there with the patched sources of v6.4. Here are some remarks on the patch. There are some things that have still to be done but at the moment I don't have time to do them myself. (I'm doing my military service at the moment) Sorry for that :-( -) I used a rewrite technique for the implementation of the Except/Intersect logic which rewrites the query to a semantically equivalent query before it is handed to the rewrite system (for views, rules etc.), planner, executor etc. -) In v6.3.2 the types of the attributes of two select statements connected by the UNION keyword had to match 100%. In v6.4 the types only need to be familiar (i.e. int and float can be mixed). Since this feature did not exist when I worked on Intersect/Except it does not work correctly for Except/Intersect queries WHEN USED IN COMBINATION WITH UNIONS! (i.e. sometimes the wrong type is used for the resulting table. This is because until now the types of the attributes of the first select statement have been used for the resulting table. When Intersects and/or Excepts are used in combination with Unions it might happen, that the first select statement of the original query appears at another position in the query which will be executed. The reason for this is the technique used for the implementation of Except/Intersect which does a query rewrite!) NOTE: It is NOT broken for pure UNION queries and pure INTERSECT/EXCEPT queries!!! -) I had to add the field intersect_clause to some data structures but did not find time to implement printfuncs for the new field. This does NOT break the debug modes but when an Except/Intersect is used the query debug output will be the already rewritten query. -) Massive changes to the grammar rules for SELECT and INSERT statements have been necessary (see comments in gram.y and documentation for deatails) in order to be able to use mixed queries like (SELECT ... UNION (SELECT ... EXCEPT SELECT)) INTERSECT SELECT...; -) When using UNION/EXCEPT/INTERSECT you will get: NOTICE: equal: "Don't know if nodes of type xxx are equal". I did not have time to add comparsion support for all the needed nodes, but the default behaviour of the function equal met my requirements. I did not dare to supress this message! That's the reason why the regression test for union will fail: These messages are also included in the union.out file! -) Somebody of you changed the union_planner() function for v6.4 (I copied the targetlist to new_tlist and that was removed and replaced by a cleanup of the original targetlist). These chnages violated some having queries executed against views so I changed it back again. I did not have time to examine the differences between the two versions but now it works :-) If you want to find out, try the file queries/view_having.sql on both versions and compare the results . Two queries won't produce a correct result with your version. regards Stefan
* Clean up trivial compiler warning from gcc.Tom Lane1999-01-17
|
* Reverse out yesterday's patch from Horak Daniel, sinceTom Lane1999-01-17
| | | | | | it fails to compile on any machine without a <features.h> header. If this header is actually necessary on Windows, perhaps an #if test is in order.
* Keep Tcl from getting confused if backend closes connectionTom Lane1999-01-17
| | | | when a notify is installed.
* TCL_ARRAYS option patches from Massimo Dal ZottoTom Lane1999-01-17
|
* Add missing variable, per Massimo.Tom Lane1999-01-17
|
* fixes to lock debugging macros from Massimo Dal ZottoTom Lane1999-01-17
|
* Add description of ELOG_TIMESTAMPS and USE_SYSLOG options,Tom Lane1999-01-17
| | | | per Massimo Dal Zotto.
* Win32 new files.Bruce Momjian1999-01-17
|
* Apply Win32 patch from Horak Daniel.Bruce Momjian1999-01-17
|
* As the email posted to the announce and interfaces list, attached is a tarBruce Momjian1999-01-17
| | | | | | | | | | | | | | | | | | | | file containing the latest version of the JDBC driver, allowing it to be compiled and used under JDK 1.2 and later. NB: None (well almost none) of the new methods actually do anything. This release only handles getting it to compile and run. Now this is done, I'll start working on implementing the new stuff. Now this tar file replaces everything under src/interfaces/jdbc. I had to do it this way, rather than diffs, because most of the classes under the postgresql subdirectory have moved to a new directory under that one, to enable the support of the two JDBC standards. Here's a list of files in the tar file. Any file not listed here (in the postgresql directory) will have to be deleted, otherwise it could cause the driver to fail: Peter Mount
* Improve error message when connect() call fails:Tom Lane1999-01-17
| | | | report kernel's errno value.
* Fix for missing NAN.Bruce Momjian1999-01-17
|
* Add configure test to see whether vsnprintf() is present,Tom Lane1999-01-17
| | | | | separately from snprintf() --- HPUX, for one, has snprintf but not vsnprintf. Fix a minor typo in snprintf.c, too.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-03 03:34:13 +0000