mirror of
https://github.com/postgres/postgres.git
synced 2025-11-19 13:42:17 +03:00
Fix up planner infrastructure to support LATERAL properly.
This patch takes care of a number of problems having to do with failure to choose valid join orders and incorrect handling of lateral references pulled up from subqueries. Notable changes: * Add a LateralJoinInfo data structure similar to SpecialJoinInfo, to represent join ordering constraints created by lateral references. (I first considered extending the SpecialJoinInfo structure, but the semantics are different enough that a separate data structure seems better.) Extend join_is_legal() and related functions to prevent trying to form unworkable joins, and to ensure that we will consider joins that satisfy lateral references even if the joins would be clauseless. * Fill in the infrastructure needed for the last few types of relation scan paths to support parameterization. We'd have wanted this eventually anyway, but it is necessary now because a relation that gets pulled up out of a UNION ALL subquery may acquire a reltargetlist containing lateral references, meaning that its paths *have* to be parameterized whether or not we have any code that can push join quals down into the scan. * Compute data about lateral references early in query_planner(), and save in RelOptInfo nodes, to avoid repetitive calculations later. * Assorted corner-case bug fixes. There's probably still some bugs left, but this is a lot closer to being real than it was before.
This commit is contained in:
@@ -194,6 +194,15 @@ static Const *string_to_const(const char *str, Oid datatype);
|
||||
* 'rel' is the relation for which we want to generate index paths
|
||||
*
|
||||
* Note: check_partial_indexes() must have been run previously for this rel.
|
||||
*
|
||||
* Note: in corner cases involving LATERAL appendrel children, it's possible
|
||||
* that rel->lateral_relids is nonempty. Currently, we include lateral_relids
|
||||
* into the parameterization reported for each path, but don't take it into
|
||||
* account otherwise. The fact that any such rels *must* be available as
|
||||
* parameter sources perhaps should influence our choices of index quals ...
|
||||
* but for now, it doesn't seem worth troubling over. In particular, comments
|
||||
* below about "unparameterized" paths should be read as meaning
|
||||
* "unparameterized so far as the indexquals are concerned".
|
||||
*/
|
||||
void
|
||||
create_index_paths(PlannerInfo *root, RelOptInfo *rel)
|
||||
@@ -304,7 +313,8 @@ create_index_paths(PlannerInfo *root, RelOptInfo *rel)
|
||||
BitmapHeapPath *bpath;
|
||||
|
||||
bitmapqual = choose_bitmap_and(root, rel, bitindexpaths);
|
||||
bpath = create_bitmap_heap_path(root, rel, bitmapqual, NULL, 1.0);
|
||||
bpath = create_bitmap_heap_path(root, rel, bitmapqual,
|
||||
rel->lateral_relids, 1.0);
|
||||
add_path(rel, (Path *) bpath);
|
||||
}
|
||||
|
||||
@@ -735,12 +745,13 @@ build_index_paths(PlannerInfo *root, RelOptInfo *rel,
|
||||
* clause.
|
||||
*
|
||||
* We also build a Relids set showing which outer rels are required by the
|
||||
* selected clauses.
|
||||
* selected clauses. Any lateral_relids are included in that, but not
|
||||
* otherwise accounted for.
|
||||
*/
|
||||
index_clauses = NIL;
|
||||
clause_columns = NIL;
|
||||
found_clause = false;
|
||||
outer_relids = NULL;
|
||||
outer_relids = bms_copy(rel->lateral_relids);
|
||||
for (indexcol = 0; indexcol < index->ncolumns; indexcol++)
|
||||
{
|
||||
ListCell *lc;
|
||||
|
||||
Reference in New Issue
Block a user