postgresql - postgresql mirror

	Commit message (Collapse)	Author	Age
*	Update copyright to 2002.	Bruce Momjian	2002-06-20
\|
*	First pass at set-returning-functions in FROM, by Joe Conway with	Tom Lane	2002-05-12
\| \| \| \| \| \|	some kibitzing from Tom Lane. Not everything works yet, and there's no documentation or regression test, but let's commit this so Joe doesn't need to cope with tracking changes in so many files ...
*	pgindent run on all C files. Java run to follow. initdb/regression	Bruce Momjian	2001-10-25
\| \| \| \|	tests pass.
*	EXPLAIN ANALYZE feature to measure and show actual runtimes and tuple	Tom Lane	2001-09-18
\| \| \| \| \|	counts alongside the planner's estimates. By Martijn van Oosterhout, with some further work by Tom Lane.
*	Cause ExecCountSlots() accounting to bear some relationship to reality.	Tom Lane	2001-05-27
\| \| \| \|	Rather surprising we hadn't seen bug reports about this ...
*	Remove unnecessary EvalPlanQual support code --- since this plan node	Tom Lane	2001-05-15
\| \| \| \| \| \|	type never scans a relation directly, it can't be an EPQ target. Explicitly drop subplan's tuple table to ensure we have no buffer pin leaks.
*	Append and SubqueryScan nodes were not passing changed-parameter signals down	Tom Lane	2001-05-08
\| \| \| \| \| \| \| \| \|	to their children, leading to misbehavior if they had any children that paid attention to chgParam (most plan node types don't). Append's bug has been there a long time, but nobody had noticed because it used to be difficult to create a query where an Append would be used below the top level of a plan; so there were never any parameters getting passed down. SubqueryScan is new in 7.1 ... and I'd modeled its behavior on Append :-(
*	Remove dashes in comments that don't need them, rewrap with pgindent.	Bruce Momjian	2001-03-22
\|
*	pgindent run. Make it all clean.	Bruce Momjian	2001-03-22
\|
*	Clean up handling of tuple descriptors so that result-tuple descriptors	Tom Lane	2001-01-29
\| \| \| \| \| \| \| \|	allocated by plan nodes are not leaked at end of query. This doesn't really matter for normal queries, but it sure does for queries invoked repetitively inside SQL functions. Clean up some other grotty code associated with tupdescs, and fix a few other memory leaks exposed by tests with simple SQL functions.
*	Change Copyright from PostgreSQL, Inc to PostgreSQL Global Development Group.	Bruce Momjian	2001-01-24
\|
*	Reimplementation of UNION/INTERSECT/EXCEPT. INTERSECT/EXCEPT now meet the	Tom Lane	2000-10-05
\| \| \| \| \| \| \| \| \| \| \|	SQL92 semantics, including support for ALL option. All three can be used in subqueries and views. DISTINCT and ORDER BY work now in views, too. This rewrite fixes many problems with cross-datatype UNIONs and INSERT/SELECT where the SELECT yields different datatypes than the INSERT needs. I did that by making UNION subqueries and SELECT in INSERT be treated like subselects-in-FROM, thereby allowing an extra level of targetlist where the datatype conversions can be inserted safely. INITDB NEEDED!
*	Subselects in FROM clause, per ISO syntax: FROM (SELECT ...) [AS] alias.	Tom Lane	2000-09-29
	(Don't forget that an alias is required.) Views reimplemented as expanding to subselect-in-FROM. Grouping, aggregates, DISTINCT in views actually work now (he says optimistically). No UNION support in subselects/views yet, but I have some ideas about that. Rule-related permissions checking moved out of rewriter and into executor. INITDB REQUIRED!