Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Stamp copyrights for year 2011. | Bruce Momjian | 2011-01-01 |
| | |||
* | Remove cvs keywords from all files. | Magnus Hagander | 2010-09-20 |
| | |||
* | Make NestLoop plan nodes pass outer-relation variables into their inner | Tom Lane | 2010-07-12 |
| | | | | | | | | | | | | relation using the general PARAM_EXEC executor parameter mechanism, rather than the ad-hoc kluge of passing the outer tuple down through ExecReScan. The previous method was hard to understand and could never be extended to handle parameters coming from multiple join levels. This patch doesn't change the set of possible plans nor have any significant performance effect, but it's necessary infrastructure for future generalization of the concept of an inner indexscan plan. ExecReScan's second parameter is now unused, so it's removed. | ||
* | Update copyright for the year 2010. | Bruce Momjian | 2010-01-02 |
| | |||
* | Move the handling of SELECT FOR UPDATE locking and rechecking out of | Tom Lane | 2009-10-12 |
execMain.c and into a new plan node type LockRows. Like the recent change to put table updating into a ModifyTable plan node, this increases planning flexibility by allowing the operations to occur below the top level of the plan tree. It's necessary in any case to restore the previous behavior of having FOR UPDATE locking occur before ModifyTable does. This partially refactors EvalPlanQual to allow multiple rows-under-test to be inserted into the EPQ machinery before starting an EPQ test query. That isn't sufficient to fix EPQ's general bogosity in the face of plans that return multiple rows per test row, though. Since this patch is mostly about getting some plan node infrastructure in place and not about fixing ten-year-old bugs, I will leave EPQ improvements for another day. Another behavioral change that we could now think about is doing FOR UPDATE before LIMIT, but that too seems like it should be treated as a followon patch. |