aboutsummaryrefslogtreecommitdiff
path: root/src/include/executor
Commit message (Collapse)AuthorAge
* Move some system includes into c.h, and remove duplicates.Bruce Momjian1999-07-17
|
* More cleanupBruce Momjian1999-07-16
|
* Change #include's to use <> and "" as appropriate.Bruce Momjian1999-07-15
|
* Clean up #include in /include directory. Add scripts for checking includes.Bruce Momjian1999-07-15
|
* Cleanup of /include #include's, for 6.6 only.Bruce Momjian1999-07-14
|
* Remove S*I comments from Stephan.Bruce Momjian1999-07-13
|
* Remove QUERY_LIMIT and documenation on same. Change _ALIGN to TYPEALIGNBruce Momjian1999-06-17
| | | | for Irix.
* Another pgindent run. Sorry folks.Bruce Momjian1999-05-25
|
* pgindent run over code.Bruce Momjian1999-05-25
|
* Rewrite hash join to use simple linked lists instead of aTom Lane1999-05-18
| | | | | | | fixed-size hashtable. This should prevent 'hashtable out of memory' errors, unless you really do run out of memory. Note: target size for hashtable is now taken from -S postmaster switch, not -B, since it is local memory in the backend rather than shared memory.
* Rip out QueryTreeList structure, root and branch. QuerytreeTom Lane1999-05-13
| | | | | | | | | | lists are now plain old garden-variety Lists, allocated with palloc, rather than specialized expansible-array data allocated with malloc. This substantially simplifies their handling and eliminates several sources of memory leakage. Several basic types of erroneous queries (syntax error, attempt to insert a duplicate key into a unique index) now demonstrably leak zero bytes per query.
* Update hash and join routines to use fd.c's new temp-fileTom Lane1999-05-09
| | | | code, instead of not-very-bulletproof stuff they had before.
* Fix some nasty coredump bugs in hashjoin. This code was justTom Lane1999-05-06
| | | | | | | | | | about certain to fail anytime it decided the relation to be hashed was too big to fit in memory --- the code for 'batching' a series of hashjoins had multiple errors. I've fixed the easier problems. A remaining big problem is that you can get 'hashtable out of memory' if the code's guesstimate about how much overflow space it will need turns out wrong. That will require much more extensive revisions to fix, so I'm committing these fixes now before I start on that problem.
* Add missing function prototypes to stifle gcc warnings.Tom Lane1999-04-16
|
* Remove Tee code, move to _deadcode.Bruce Momjian1999-03-23
|
* Changes to fix/improve the dynamic loading on NTMarc G. Fournier1999-03-09
| | | | From: Horak Daniel <horak@mmp.plzen-city.cz>
* Bring debugging print statement declarations up to date.Thomas G. Lockhart1999-02-23
| | | | | Comment-out the #undef default declarations to allow the parameters to be set on the compiler command line.
* Add constants for outer join states in executor.Thomas G. Lockhart1999-02-23
|
* Fix typos in comments.Thomas G. Lockhart1999-02-23
|
* From: Tatsuo Ishii <t-ishii@sra.co.jp>Marc G. Fournier1999-02-21
| | | | | | 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-13
|
* Optimizer cleanup.Bruce Momjian1999-02-12
|
* Added LIMIT/OFFSET functionality including new regression test for it.Jan Wieck1999-02-08
| | | | | | | Removed CURRENT keyword for rule queries and changed rules regression accordingly. CURRENT has beed announced to disappear in v6.5. Jan
* Changed ExecConstraints() and ExecRelCheck() to cache the constraintsJan Wieck1999-02-07
| | | | | | | | | qualification expression trees in the execution state. Prevents from memory exhaustion on INSERT, UPDATE or COPY to tables that have CHECK constraints. Speedup against the variant using freeObject() is more than factor 2. Jan
* Speedup of PL/pgSQL by calling ExecEvalExpr() directlyJan Wieck1999-01-27
| | | | | | instead of SPI_execp() for simple expressions. Jan
* 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
* New HeapTuple structure/interface.Vadim B. Mikheev1998-11-27
|
* New QUERY_LIMIT set command.Bruce Momjian1998-10-14
|
* Make functions static or ifdef NOT_USED. Prevent pg_version creation.Bruce Momjian1998-10-08
|
* OK, folks, here is the pgindent output.Bruce Momjian1998-09-01
|
* Renaming cleanup, no pgindent yet.Bruce Momjian1998-09-01
|
* Use Snapshot in heap access methods.Vadim B. Mikheev1998-07-27
|
* Patch for ReScan of Group.Bruce Momjian1998-07-16
|
* Allow UNION/UNION ALL in subselects.Bruce Momjian1998-07-15
|
* Fix macros that were not properly surrounded by parens or braces.Bruce Momjian1998-06-15
|
* Inline some small functions called for every row.Bruce Momjian1998-04-24
|
* ExecReScan for MergeJoin.Vadim B. Mikheev1998-02-27
|
* pgindent run before 6.3 release, with Thomas' requested changes.Bruce Momjian1998-02-26
|
* ExecReScan for Unique & Sort nodes.Vadim B. Mikheev1998-02-23
|
* Subselects...Vadim B. Mikheev1998-02-13
|
* Pass attypmod through to executor by adding to Var and Resdom.Bruce Momjian1998-02-10
|
* Fix prototypes so they don't look like function definitions.Bruce Momjian1998-01-24
|
* Fix for SELECT INTO TABLE for varchar().Bruce Momjian1998-01-19
|
* Cleanup of prototypes. FIx for PQtrace start/stop several times.Bruce Momjian1998-01-14
|
* Add pg_type.h to include list to regain declaration of type OID assignments.Thomas G. Lockhart1997-11-30
| | | | | Lost these when some include files were reorganized. Regression test could not compile.
* Make parser functions static where possible.Bruce Momjian1997-11-26
|
* Cleanup up include files.Bruce Momjian1997-11-26
|
* Cleanup up include files.Bruce Momjian1997-11-26
|
* Break parser functions into smaller files, group together.Bruce Momjian1997-11-25
|
* Remove all time travel stuff. Small parser cleanup.Bruce Momjian1997-11-20
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-07 08:31:06 +0000