9 Commits (f92e8a4b5ee6a22252cbba012d629f5cefef913f)

Author	SHA1	Message	Date
Bruce Momjian	511db38ace	Update copyright for 2009.	17 years ago
Bruce Momjian	9098ab9e32	Update copyrights in source tree to 2008.	18 years ago
Tom Lane	eab6b8b27e	Turn the rangetable used by the executor into a flat list, and avoid storing ... useless substructure for its RangeTblEntry nodes. (I chose to keep using the same struct node type and just zero out the link fields for unneeded info, rather than making a separate ExecRangeTblEntry type --- it seemed too fragile to have two different rangetable representations.) Along the way, put subplans into a list in the toplevel PlannedStmt node, and have SubPlan nodes refer to them by list index instead of direct pointers. Vadim wanted to do that years ago, but I never understood what he was on about until now. It makes things a *whole* lot more robust, because we can stop worrying about duplicate processing of subplans during expression tree traversals. That's been a constant source of bugs, and it's finally gone. There are some consequent simplifications yet to be made, like not using a separate EState for subplans in the executor, but I'll tackle that later.	19 years ago
Tom Lane	b8c3267792	Put function expressions and values lists into FunctionScan and ValuesScan ... plan nodes, so that the executor does not need to get these items from the range table at runtime. This will avoid needing to include these fields in the compact range table I'm expecting to make the executor use.	19 years ago
Bruce Momjian	29dccf5fe0	Update CVS HEAD for 2007 copyright. Back branches are typically not ... back-stamped for this.	19 years ago
Tom Lane	68996463d4	Repair bug #2839: the various ExecReScan functions need to reset ... ps_TupFromTlist in plan nodes that make use of it. This was being done correctly in join nodes and Result nodes but not in any relation-scan nodes. Bug would lead to bogus results if a set-returning function appeared in the targetlist of a subquery that could be rescanned after partial execution, for example a subquery within EXISTS(). Bug has been around forever :-( ... surprising it wasn't reported before.	19 years ago
Bruce Momjian	f99a569a2e	pgindent run for 8.2.	20 years ago
Tom Lane	0dfb595d7a	Arrange for ValuesScan to keep per-sublist expression eval state in a ... temporary context that can be reset when advancing to the next sublist. This is faster and more thorough at recovering space than the previous method; moreover it will do the right thing if something in the sublist tries to register an expression context callback.	20 years ago
Joe Conway	9caafda579	Add support for multi-row VALUES clauses as part of INSERT statements ... (e.g. "INSERT ... VALUES (...), (...), ...") and elsewhere as allowed by the spec. (e.g. similar to a FROM clause subselect). initdb required. Joe Conway and Tom Lane.	20 years ago