summaryrefslogtreecommitdiff
path: root/src/backend/nodes
AgeCommit message (Collapse)Author
1999-03-23Remove Tee code, move to _deadcode.Bruce Momjian
1999-03-03Partial fix for copied-plan bugs reported by Hiroshi Inoue:Tom Lane
_copyResult didn't copy subPlan structure completely. _copyAgg is still busted, apparently because of changes from EXCEPT/INTERSECT patch (get_agg_tlist_references is no longer sufficient to find all aggregates). No time to look at that tonight, however.
1999-03-01Executor no longer cares about mergejoinop, mergerightorder, mergeleftorder,Tom Lane
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.
1999-02-23Add a few other parser-only nodes for debugging help.Thomas G. Lockhart
Define the JoinExpr node.
1999-02-23Rearrange order of subdirectory creation to help generate parse.hThomas G. Lockhart
file early enough to use in nodes/. Try to be more complete for rules on generating parse.h, but it still does not work any better than before. Should be able to make correctly if parser/gram.y is updated even without a "make clean" but so far not there yet.
1999-02-22comments cleanup.Bruce Momjian
1999-02-22ifdef out append().Bruce Momjian
1999-02-22more cleanupBruce Momjian
1999-02-22Final optimizer cleanups.Bruce Momjian
1999-02-22fix compile problem.Bruce Momjian
1999-02-21pathkeys.c cleanup.Bruce Momjian
1999-02-20pathkeys fixesBruce Momjian
1999-02-18Fix bushy plans. Cleanup.Bruce Momjian
1999-02-15otherrels is now unjoined_relsBruce Momjian
1999-02-15Remove duplicate geqo functions, and more optimizer cleanupBruce Momjian
1999-02-13Change my-function-name-- to my_function_name, and optimizer renames.Bruce Momjian
1999-02-12JoinPath -> NestPath for nested loop.Bruce Momjian
1999-02-12Fix optimizer and make faster.Bruce Momjian
1999-02-11More optimizer speedups.Bruce Momjian
1999-02-10Optmizer cleanupBruce Momjian
1999-02-10Rename Path.keys to Path.pathkeys. Too many 'keys' used for other things.Bruce Momjian
1999-02-09Rename Temp to Noname for noname tables.Bruce Momjian
1999-02-09Major optimizer improvement for joining a large number of tables.Bruce Momjian
1999-02-08Optimizer cleanup.Bruce Momjian
1999-02-07Add equality checking for T_Query so that we don't getTom Lane
complaints in UNION regress test. Probably still need some more node types to be handled here, but I'm done for the day...
1999-02-06Optimizer cleanup.Bruce Momjian
1999-02-06New alloc set code using a memory block pool for small allocations.Jan Wieck
Jan
1999-02-05Optimizer cleanup.Bruce Momjian
1999-02-04More optimizer cleanups.Bruce Momjian
1999-02-04More optimizer renaming HInfo -> HashInfo.Bruce Momjian
1999-02-03Cleanup of source files where 'return' or 'var =' is alone on a line.Bruce Momjian
1999-02-03Optimizer rename ClauseInfo -> RestrictInfo. Update optimizer README.Bruce Momjian
1999-02-02SET_ARGS cleanupBruce Momjian
1999-02-02Add TEMP tables/indexes. Add COPY pfree(). Other cleanups.Bruce Momjian
1999-01-29READ COMMITTED isolevel is implemented and is default now.Vadim B. Mikheev
1999-01-27Another SELECT speedup: extract OIDs of column print functionsTom Lane
only once per SELECT, not once per tuple. 10% here, 10% there, pretty soon you're talking about real speedups ...
1999-01-25Agg/Aggreg cleanup and datetime.sql patch.Bruce Momjian
1999-01-24Rename Aggreg to Aggref.Bruce Momjian
1999-01-21It seems that SPI_prepare() doesn't work well in some cases.Bruce Momjian
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
1999-01-21Copy RowMark node (it's for (-:)) FOR UPDATE).Vadim B. Mikheev
1999-01-21FOR UPDATE is in parser & rules.Vadim B. Mikheev
1999-01-18Hi!Bruce Momjian
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
1998-12-20finished cleaning up outnodes.c ...Marc G. Fournier
1998-12-18Fixed nodeToString() to put out "<>" for NULL strings again.Jan Wieck
More cleanups to appendStringInfo() usage in node/outfuncs.c. Jan
1998-12-17From: Keith Parks <emkxp01@mtcc.demon.co.uk>Marc G. Fournier
Looks like :vartypmod got transmuted to %vartypmod in an editing session.
1998-12-15More cleanups ... this is one big file *sigh*Marc G. Fournier
1998-12-15Correct some typos...Marc G. Fournier
1998-12-15More cleanups of appendStringInfo() function calls...Marc G. Fournier
1998-12-14more cleanups...of note, appendStringInfo now performs like sprintf(),Marc G. Fournier
where you state a format and arguments. the old behavior required each appendStringInfo to have to have a sprintf() before it if any formatting was required. Also shortened several instances where there were multiple appendStringInfo() calls in a row, doing nothing more then adding one more word to the String, instead of doing them all in one call.
1998-12-14Many more cleanups...Marc G. Fournier
generated by cgit v1.2.3 (git 2.46.0) at 2025-08-22 09:34:16 +0000