aboutsummaryrefslogtreecommitdiff
path: root/src/backend/nodes/readfuncs.c
Commit message (Collapse)AuthorAge
...
* Clean up messy clause-selectivity code in clausesel.c; repair bugTom Lane1999-07-24
| | | | | | | | | | | | | | | | | | | | identified by Hiroshi (incorrect cost attributed to OR clauses after multiple passes through set_rest_selec()). I think the code was trying to allow selectivities of OR subclauses to be passed in from outside, but noplace was actually passing any useful data, and set_rest_selec() was passing wrong data. Restructure representation of "indexqual" in IndexPath nodes so that it is the same as for indxqual in completed IndexScan nodes: namely, a toplevel list with an entry for each pass of the index scan, having sublists that are implicitly-ANDed index qual conditions for that pass. You don't want to know what the old representation was :-( Improve documentation of OR-clause indexscan functions. Remove useless 'notclause' field from RestrictInfo nodes. (This might force an initdb for anyone who has stored rules containing RestrictInfos, but I do not think that RestrictInfo ever appears in completed plans.)
* Move some system includes into c.h, and remove duplicates.Bruce Momjian1999-07-17
|
* Final cleanup.Bruce Momjian1999-07-16
|
* Remove unused #includes in *.c files.Bruce Momjian1999-07-15
|
* Clean up #include in /include directory. Add scripts for checking includes.Bruce Momjian1999-07-15
|
* Remove S*I comments from Stephan.Bruce Momjian1999-07-13
|
* pgindent run over code.Bruce Momjian1999-05-25
|
* Remove no-longer-used fields in Hash and HashJoin nodes.Tom Lane1999-05-18
|
* Change resjunk to a boolean.Bruce Momjian1999-05-17
|
* Replaced targetlist entry in GroupClause by reference numberJan Wieck1999-05-12
| | | | | | | in Resdom and GroupClause so changing of resno's doesn't confuse the grouping any more. Jan
* Executor no longer cares about mergejoinop, mergerightorder, mergeleftorder,Tom Lane1999-03-01
| | | | | | | | | so remove them from MergeJoin node. Hack together a partial solution for commuted mergejoin operators --- yesterday a mergejoin int4 = int8 would crash if the planner decided to commute it, today it works. The planner's representation of mergejoins really needs a rewrite though. Also, further testing of mergejoin ops in opr_sanity regress test.
* Fix bushy plans. Cleanup.Bruce Momjian1999-02-18
|
* otherrels is now unjoined_relsBruce Momjian1999-02-15
|
* Change my-function-name-- to my_function_name, and optimizer renames.Bruce Momjian1999-02-13
|
* JoinPath -> NestPath for nested loop.Bruce Momjian1999-02-12
|
* Fix optimizer and make faster.Bruce Momjian1999-02-12
|
* More optimizer speedups.Bruce Momjian1999-02-11
|
* Rename Path.keys to Path.pathkeys. Too many 'keys' used for other things.Bruce Momjian1999-02-10
|
* Rename Temp to Noname for noname tables.Bruce Momjian1999-02-09
|
* Major optimizer improvement for joining a large number of tables.Bruce Momjian1999-02-09
|
* Optimizer cleanup.Bruce Momjian1999-02-08
|
* Optimizer cleanup.Bruce Momjian1999-02-05
|
* More optimizer cleanups.Bruce Momjian1999-02-04
|
* More optimizer renaming HInfo -> HashInfo.Bruce Momjian1999-02-04
|
* Cleanup of source files where 'return' or 'var =' is alone on a line.Bruce Momjian1999-02-03
|
* Optimizer rename ClauseInfo -> RestrictInfo. Update optimizer README.Bruce Momjian1999-02-03
|
* Add TEMP tables/indexes. Add COPY pfree(). Other cleanups.Bruce Momjian1999-02-02
|
* Rename Aggreg to Aggref.Bruce Momjian1999-01-24
|
* FOR UPDATE is in parser & rules.Vadim B. Mikheev1999-01-21
|
* 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
* Add support for the CASE statement in the rewrite handling.Thomas G. Lockhart1998-12-14
| | | | | | Allows (at least some) rules and views. Still some trouble (crashes) with target CASE columns spanning tables, but lots now works.
* Fix using indices in OR.Vadim B. Mikheev1998-11-22
| | | | EXPLAIN all indices used.
* Add LIMIT syntax for Jan.Bruce Momjian1998-10-22
|
* OK, folks, here is the pgindent output.Bruce Momjian1998-09-01
|
* Renaming cleanup, no pgindent yet.Bruce Momjian1998-09-01
|
* MergeSort was sometimes called mergejoin and was confusing. NowBruce Momjian1998-08-04
| | | | it is now only mergejoin.
* Allow index use with OR clauses.Bruce Momjian1998-08-01
|
* Rename Rel to RelOptInfo.Bruce Momjian1998-07-18
|
* Fix explain for union and inheritance. Rename Append structureBruce Momjian1998-07-15
| | | | members to be clearer. Fix cost computation for these.
* Major man page update from Tom Lane. cBruce Momjian1998-07-14
|
* Remove un-needed braces around single statements.Bruce Momjian1998-06-15
|
* FIx confusion over SORT and SORTCLAUSE in node handling.Bruce Momjian1998-04-27
|
* pgindent run before 6.3 release, with Thomas' requested changes.Bruce Momjian1998-02-26
|
* Add handling for new RangeTblEntry column name.Bruce Momjian1998-02-21
|
* Constlen can be -1, so make it a signed type.Bruce Momjian1998-02-21
|
* Support for subselects.Vadim B. Mikheev1998-02-13
| | | | (Have to re-visit readfuncs.c)
* Pass around typmod as int16.Bruce Momjian1998-02-10
|
* Pass attypmod through to executor by adding to Var and Resdom.Bruce Momjian1998-02-10
|
* Add Var.varlevelup to code. More parser cleanup.Bruce Momjian1998-01-20
|
* Parser cleanup.Bruce Momjian1998-01-20
| | | | Add lock to i386 asm.
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-12 07:37:58 +0000