Fix some more problems with nested append relations.
As of commit a87c72915 (which later got backpatched as far as 9.1),
we're explicitly supporting the notion that append relations can be
nested; this can occur when UNION ALL constructs are nested, or when
a UNION ALL contains a table with inheritance children.
Bug #11457 from Nelson Page, as well as an earlier report from Elvis
Pranskevichus, showed that there were still nasty bugs associated with such
cases: in particular the EquivalenceClass mechanism could try to generate
"join" clauses connecting an appendrel child to some grandparent appendrel,
which would result in assertion failures or bogus plans.
Upon investigation I concluded that all current callers of
find_childrel_appendrelinfo() need to be fixed to explicitly consider
multiple levels of parent appendrels. The most complex fix was in
processing of "broken" EquivalenceClasses, which are ECs for which we have
been unable to generate all the derived equality clauses we would like to
because of missing cross-type equality operators in the underlying btree
operator family. That code path is more or less entirely untested by
the regression tests to date, because no standard opfamilies have such
holes in them. So I wrote a new regression test script to try to exercise
it a bit, which turned out to be quite a worthwhile activity as it exposed
existing bugs in all supported branches.
The present patch is essentially the same as far back as 9.2, which is
where parameterized paths were introduced. In 9.0 and 9.1, we only need
to back-patch a small fragment of commit 5b7b5518d, which fixes failure to
propagate out the original WHERE clauses when a broken EC contains constant
members. (The regression test case results show that these older branches
are noticeably stupider than 9.2+ in terms of the quality of the plans
generated; but we don't really care about plan quality in such cases,
only that the plan not be outright wrong. A more invasive fix in the
older branches would not be a good idea anyway from a plan-stability
standpoint.)
2014-10-02 01:30:24 +02:00
|
|
|
--
|
|
|
|
-- Tests for the planner's "equivalence class" mechanism
|
|
|
|
--
|
|
|
|
-- One thing that's not tested well during normal querying is the logic
|
|
|
|
-- for handling "broken" ECs. This is because an EC can only become broken
|
|
|
|
-- if its underlying btree operator family doesn't include a complete set
|
|
|
|
-- of cross-type equality operators. There are not (and should not be)
|
|
|
|
-- any such families built into Postgres; so we have to hack things up
|
|
|
|
-- to create one. We do this by making two alias types that are really
|
|
|
|
-- int8 (so we need no new C code) and adding only some operators for them
|
|
|
|
-- into the standard integer_ops opfamily.
|
|
|
|
create type int8alias1;
|
|
|
|
create function int8alias1in(cstring) returns int8alias1
|
|
|
|
strict immutable language internal as 'int8in';
|
|
|
|
NOTICE: return type int8alias1 is only a shell
|
|
|
|
create function int8alias1out(int8alias1) returns cstring
|
|
|
|
strict immutable language internal as 'int8out';
|
|
|
|
NOTICE: argument type int8alias1 is only a shell
|
|
|
|
create type int8alias1 (
|
|
|
|
input = int8alias1in,
|
|
|
|
output = int8alias1out,
|
|
|
|
like = int8
|
|
|
|
);
|
|
|
|
create type int8alias2;
|
|
|
|
create function int8alias2in(cstring) returns int8alias2
|
|
|
|
strict immutable language internal as 'int8in';
|
|
|
|
NOTICE: return type int8alias2 is only a shell
|
|
|
|
create function int8alias2out(int8alias2) returns cstring
|
|
|
|
strict immutable language internal as 'int8out';
|
|
|
|
NOTICE: argument type int8alias2 is only a shell
|
|
|
|
create type int8alias2 (
|
|
|
|
input = int8alias2in,
|
|
|
|
output = int8alias2out,
|
|
|
|
like = int8
|
|
|
|
);
|
|
|
|
create cast (int8 as int8alias1) without function;
|
|
|
|
create cast (int8 as int8alias2) without function;
|
|
|
|
create cast (int8alias1 as int8) without function;
|
|
|
|
create cast (int8alias2 as int8) without function;
|
|
|
|
create function int8alias1eq(int8alias1, int8alias1) returns bool
|
|
|
|
strict immutable language internal as 'int8eq';
|
|
|
|
create operator = (
|
|
|
|
procedure = int8alias1eq,
|
|
|
|
leftarg = int8alias1, rightarg = int8alias1,
|
|
|
|
commutator = =,
|
|
|
|
restrict = eqsel, join = eqjoinsel,
|
|
|
|
merges
|
|
|
|
);
|
|
|
|
alter operator family integer_ops using btree add
|
|
|
|
operator 3 = (int8alias1, int8alias1);
|
|
|
|
create function int8alias2eq(int8alias2, int8alias2) returns bool
|
|
|
|
strict immutable language internal as 'int8eq';
|
|
|
|
create operator = (
|
|
|
|
procedure = int8alias2eq,
|
|
|
|
leftarg = int8alias2, rightarg = int8alias2,
|
|
|
|
commutator = =,
|
|
|
|
restrict = eqsel, join = eqjoinsel,
|
|
|
|
merges
|
|
|
|
);
|
|
|
|
alter operator family integer_ops using btree add
|
|
|
|
operator 3 = (int8alias2, int8alias2);
|
|
|
|
create function int8alias1eq(int8, int8alias1) returns bool
|
|
|
|
strict immutable language internal as 'int8eq';
|
|
|
|
create operator = (
|
|
|
|
procedure = int8alias1eq,
|
|
|
|
leftarg = int8, rightarg = int8alias1,
|
|
|
|
restrict = eqsel, join = eqjoinsel,
|
|
|
|
merges
|
|
|
|
);
|
|
|
|
alter operator family integer_ops using btree add
|
|
|
|
operator 3 = (int8, int8alias1);
|
|
|
|
create function int8alias1eq(int8alias1, int8alias2) returns bool
|
|
|
|
strict immutable language internal as 'int8eq';
|
|
|
|
create operator = (
|
|
|
|
procedure = int8alias1eq,
|
|
|
|
leftarg = int8alias1, rightarg = int8alias2,
|
|
|
|
restrict = eqsel, join = eqjoinsel,
|
|
|
|
merges
|
|
|
|
);
|
|
|
|
alter operator family integer_ops using btree add
|
|
|
|
operator 3 = (int8alias1, int8alias2);
|
|
|
|
create function int8alias1lt(int8alias1, int8alias1) returns bool
|
|
|
|
strict immutable language internal as 'int8lt';
|
|
|
|
create operator < (
|
|
|
|
procedure = int8alias1lt,
|
|
|
|
leftarg = int8alias1, rightarg = int8alias1
|
|
|
|
);
|
|
|
|
alter operator family integer_ops using btree add
|
|
|
|
operator 1 < (int8alias1, int8alias1);
|
|
|
|
create function int8alias1cmp(int8, int8alias1) returns int
|
|
|
|
strict immutable language internal as 'btint8cmp';
|
|
|
|
alter operator family integer_ops using btree add
|
|
|
|
function 1 int8alias1cmp (int8, int8alias1);
|
|
|
|
create table ec0 (ff int8 primary key, f1 int8, f2 int8);
|
|
|
|
create table ec1 (ff int8 primary key, f1 int8alias1, f2 int8alias2);
|
|
|
|
create table ec2 (xf int8 primary key, x1 int8alias1, x2 int8alias2);
|
|
|
|
-- for the moment we only want to look at nestloop plans
|
|
|
|
set enable_hashjoin = off;
|
|
|
|
set enable_mergejoin = off;
|
|
|
|
--
|
|
|
|
-- Note that for cases where there's a missing operator, we don't care so
|
|
|
|
-- much whether the plan is ideal as that we don't fail or generate an
|
|
|
|
-- outright incorrect plan.
|
|
|
|
--
|
|
|
|
explain (costs off)
|
|
|
|
select * from ec0 where ff = f1 and f1 = '42'::int8;
|
2015-03-30 20:59:49 +02:00
|
|
|
QUERY PLAN
|
|
|
|
-----------------------------------
|
Fix some more problems with nested append relations.
As of commit a87c72915 (which later got backpatched as far as 9.1),
we're explicitly supporting the notion that append relations can be
nested; this can occur when UNION ALL constructs are nested, or when
a UNION ALL contains a table with inheritance children.
Bug #11457 from Nelson Page, as well as an earlier report from Elvis
Pranskevichus, showed that there were still nasty bugs associated with such
cases: in particular the EquivalenceClass mechanism could try to generate
"join" clauses connecting an appendrel child to some grandparent appendrel,
which would result in assertion failures or bogus plans.
Upon investigation I concluded that all current callers of
find_childrel_appendrelinfo() need to be fixed to explicitly consider
multiple levels of parent appendrels. The most complex fix was in
processing of "broken" EquivalenceClasses, which are ECs for which we have
been unable to generate all the derived equality clauses we would like to
because of missing cross-type equality operators in the underlying btree
operator family. That code path is more or less entirely untested by
the regression tests to date, because no standard opfamilies have such
holes in them. So I wrote a new regression test script to try to exercise
it a bit, which turned out to be quite a worthwhile activity as it exposed
existing bugs in all supported branches.
The present patch is essentially the same as far back as 9.2, which is
where parameterized paths were introduced. In 9.0 and 9.1, we only need
to back-patch a small fragment of commit 5b7b5518d, which fixes failure to
propagate out the original WHERE clauses when a broken EC contains constant
members. (The regression test case results show that these older branches
are noticeably stupider than 9.2+ in terms of the quality of the plans
generated; but we don't really care about plan quality in such cases,
only that the plan not be outright wrong. A more invasive fix in the
older branches would not be a good idea anyway from a plan-stability
standpoint.)
2014-10-02 01:30:24 +02:00
|
|
|
Index Scan using ec0_pkey on ec0
|
2015-03-30 20:59:49 +02:00
|
|
|
Index Cond: (ff = '42'::bigint)
|
|
|
|
Filter: (f1 = '42'::bigint)
|
Fix some more problems with nested append relations.
As of commit a87c72915 (which later got backpatched as far as 9.1),
we're explicitly supporting the notion that append relations can be
nested; this can occur when UNION ALL constructs are nested, or when
a UNION ALL contains a table with inheritance children.
Bug #11457 from Nelson Page, as well as an earlier report from Elvis
Pranskevichus, showed that there were still nasty bugs associated with such
cases: in particular the EquivalenceClass mechanism could try to generate
"join" clauses connecting an appendrel child to some grandparent appendrel,
which would result in assertion failures or bogus plans.
Upon investigation I concluded that all current callers of
find_childrel_appendrelinfo() need to be fixed to explicitly consider
multiple levels of parent appendrels. The most complex fix was in
processing of "broken" EquivalenceClasses, which are ECs for which we have
been unable to generate all the derived equality clauses we would like to
because of missing cross-type equality operators in the underlying btree
operator family. That code path is more or less entirely untested by
the regression tests to date, because no standard opfamilies have such
holes in them. So I wrote a new regression test script to try to exercise
it a bit, which turned out to be quite a worthwhile activity as it exposed
existing bugs in all supported branches.
The present patch is essentially the same as far back as 9.2, which is
where parameterized paths were introduced. In 9.0 and 9.1, we only need
to back-patch a small fragment of commit 5b7b5518d, which fixes failure to
propagate out the original WHERE clauses when a broken EC contains constant
members. (The regression test case results show that these older branches
are noticeably stupider than 9.2+ in terms of the quality of the plans
generated; but we don't really care about plan quality in such cases,
only that the plan not be outright wrong. A more invasive fix in the
older branches would not be a good idea anyway from a plan-stability
standpoint.)
2014-10-02 01:30:24 +02:00
|
|
|
(3 rows)
|
|
|
|
|
|
|
|
explain (costs off)
|
|
|
|
select * from ec0 where ff = f1 and f1 = '42'::int8alias1;
|
|
|
|
QUERY PLAN
|
|
|
|
---------------------------------------
|
|
|
|
Index Scan using ec0_pkey on ec0
|
|
|
|
Index Cond: (ff = '42'::int8alias1)
|
|
|
|
Filter: (f1 = '42'::int8alias1)
|
|
|
|
(3 rows)
|
|
|
|
|
|
|
|
explain (costs off)
|
|
|
|
select * from ec1 where ff = f1 and f1 = '42'::int8alias1;
|
|
|
|
QUERY PLAN
|
|
|
|
---------------------------------------
|
|
|
|
Index Scan using ec1_pkey on ec1
|
|
|
|
Index Cond: (ff = '42'::int8alias1)
|
|
|
|
Filter: (f1 = '42'::int8alias1)
|
|
|
|
(3 rows)
|
|
|
|
|
|
|
|
explain (costs off)
|
|
|
|
select * from ec1 where ff = f1 and f1 = '42'::int8alias2;
|
|
|
|
QUERY PLAN
|
|
|
|
---------------------------------------------------
|
|
|
|
Seq Scan on ec1
|
|
|
|
Filter: ((ff = f1) AND (f1 = '42'::int8alias2))
|
|
|
|
(2 rows)
|
|
|
|
|
|
|
|
explain (costs off)
|
|
|
|
select * from ec1, ec2 where ff = x1 and ff = '42'::int8;
|
2015-03-30 20:59:49 +02:00
|
|
|
QUERY PLAN
|
|
|
|
-------------------------------------------------------------------
|
Fix some more problems with nested append relations.
As of commit a87c72915 (which later got backpatched as far as 9.1),
we're explicitly supporting the notion that append relations can be
nested; this can occur when UNION ALL constructs are nested, or when
a UNION ALL contains a table with inheritance children.
Bug #11457 from Nelson Page, as well as an earlier report from Elvis
Pranskevichus, showed that there were still nasty bugs associated with such
cases: in particular the EquivalenceClass mechanism could try to generate
"join" clauses connecting an appendrel child to some grandparent appendrel,
which would result in assertion failures or bogus plans.
Upon investigation I concluded that all current callers of
find_childrel_appendrelinfo() need to be fixed to explicitly consider
multiple levels of parent appendrels. The most complex fix was in
processing of "broken" EquivalenceClasses, which are ECs for which we have
been unable to generate all the derived equality clauses we would like to
because of missing cross-type equality operators in the underlying btree
operator family. That code path is more or less entirely untested by
the regression tests to date, because no standard opfamilies have such
holes in them. So I wrote a new regression test script to try to exercise
it a bit, which turned out to be quite a worthwhile activity as it exposed
existing bugs in all supported branches.
The present patch is essentially the same as far back as 9.2, which is
where parameterized paths were introduced. In 9.0 and 9.1, we only need
to back-patch a small fragment of commit 5b7b5518d, which fixes failure to
propagate out the original WHERE clauses when a broken EC contains constant
members. (The regression test case results show that these older branches
are noticeably stupider than 9.2+ in terms of the quality of the plans
generated; but we don't really care about plan quality in such cases,
only that the plan not be outright wrong. A more invasive fix in the
older branches would not be a good idea anyway from a plan-stability
standpoint.)
2014-10-02 01:30:24 +02:00
|
|
|
Nested Loop
|
|
|
|
Join Filter: (ec1.ff = ec2.x1)
|
|
|
|
-> Index Scan using ec1_pkey on ec1
|
2015-03-30 20:59:49 +02:00
|
|
|
Index Cond: ((ff = '42'::bigint) AND (ff = '42'::bigint))
|
Fix some more problems with nested append relations.
As of commit a87c72915 (which later got backpatched as far as 9.1),
we're explicitly supporting the notion that append relations can be
nested; this can occur when UNION ALL constructs are nested, or when
a UNION ALL contains a table with inheritance children.
Bug #11457 from Nelson Page, as well as an earlier report from Elvis
Pranskevichus, showed that there were still nasty bugs associated with such
cases: in particular the EquivalenceClass mechanism could try to generate
"join" clauses connecting an appendrel child to some grandparent appendrel,
which would result in assertion failures or bogus plans.
Upon investigation I concluded that all current callers of
find_childrel_appendrelinfo() need to be fixed to explicitly consider
multiple levels of parent appendrels. The most complex fix was in
processing of "broken" EquivalenceClasses, which are ECs for which we have
been unable to generate all the derived equality clauses we would like to
because of missing cross-type equality operators in the underlying btree
operator family. That code path is more or less entirely untested by
the regression tests to date, because no standard opfamilies have such
holes in them. So I wrote a new regression test script to try to exercise
it a bit, which turned out to be quite a worthwhile activity as it exposed
existing bugs in all supported branches.
The present patch is essentially the same as far back as 9.2, which is
where parameterized paths were introduced. In 9.0 and 9.1, we only need
to back-patch a small fragment of commit 5b7b5518d, which fixes failure to
propagate out the original WHERE clauses when a broken EC contains constant
members. (The regression test case results show that these older branches
are noticeably stupider than 9.2+ in terms of the quality of the plans
generated; but we don't really care about plan quality in such cases,
only that the plan not be outright wrong. A more invasive fix in the
older branches would not be a good idea anyway from a plan-stability
standpoint.)
2014-10-02 01:30:24 +02:00
|
|
|
-> Seq Scan on ec2
|
|
|
|
(5 rows)
|
|
|
|
|
|
|
|
explain (costs off)
|
|
|
|
select * from ec1, ec2 where ff = x1 and ff = '42'::int8alias1;
|
|
|
|
QUERY PLAN
|
|
|
|
---------------------------------------------
|
|
|
|
Nested Loop
|
|
|
|
-> Index Scan using ec1_pkey on ec1
|
|
|
|
Index Cond: (ff = '42'::int8alias1)
|
|
|
|
-> Seq Scan on ec2
|
|
|
|
Filter: (x1 = '42'::int8alias1)
|
|
|
|
(5 rows)
|
|
|
|
|
|
|
|
explain (costs off)
|
|
|
|
select * from ec1, ec2 where ff = x1 and '42'::int8 = x1;
|
2015-03-30 20:59:49 +02:00
|
|
|
QUERY PLAN
|
|
|
|
-----------------------------------------
|
Fix some more problems with nested append relations.
As of commit a87c72915 (which later got backpatched as far as 9.1),
we're explicitly supporting the notion that append relations can be
nested; this can occur when UNION ALL constructs are nested, or when
a UNION ALL contains a table with inheritance children.
Bug #11457 from Nelson Page, as well as an earlier report from Elvis
Pranskevichus, showed that there were still nasty bugs associated with such
cases: in particular the EquivalenceClass mechanism could try to generate
"join" clauses connecting an appendrel child to some grandparent appendrel,
which would result in assertion failures or bogus plans.
Upon investigation I concluded that all current callers of
find_childrel_appendrelinfo() need to be fixed to explicitly consider
multiple levels of parent appendrels. The most complex fix was in
processing of "broken" EquivalenceClasses, which are ECs for which we have
been unable to generate all the derived equality clauses we would like to
because of missing cross-type equality operators in the underlying btree
operator family. That code path is more or less entirely untested by
the regression tests to date, because no standard opfamilies have such
holes in them. So I wrote a new regression test script to try to exercise
it a bit, which turned out to be quite a worthwhile activity as it exposed
existing bugs in all supported branches.
The present patch is essentially the same as far back as 9.2, which is
where parameterized paths were introduced. In 9.0 and 9.1, we only need
to back-patch a small fragment of commit 5b7b5518d, which fixes failure to
propagate out the original WHERE clauses when a broken EC contains constant
members. (The regression test case results show that these older branches
are noticeably stupider than 9.2+ in terms of the quality of the plans
generated; but we don't really care about plan quality in such cases,
only that the plan not be outright wrong. A more invasive fix in the
older branches would not be a good idea anyway from a plan-stability
standpoint.)
2014-10-02 01:30:24 +02:00
|
|
|
Nested Loop
|
|
|
|
Join Filter: (ec1.ff = ec2.x1)
|
|
|
|
-> Index Scan using ec1_pkey on ec1
|
2015-03-30 20:59:49 +02:00
|
|
|
Index Cond: (ff = '42'::bigint)
|
Fix some more problems with nested append relations.
As of commit a87c72915 (which later got backpatched as far as 9.1),
we're explicitly supporting the notion that append relations can be
nested; this can occur when UNION ALL constructs are nested, or when
a UNION ALL contains a table with inheritance children.
Bug #11457 from Nelson Page, as well as an earlier report from Elvis
Pranskevichus, showed that there were still nasty bugs associated with such
cases: in particular the EquivalenceClass mechanism could try to generate
"join" clauses connecting an appendrel child to some grandparent appendrel,
which would result in assertion failures or bogus plans.
Upon investigation I concluded that all current callers of
find_childrel_appendrelinfo() need to be fixed to explicitly consider
multiple levels of parent appendrels. The most complex fix was in
processing of "broken" EquivalenceClasses, which are ECs for which we have
been unable to generate all the derived equality clauses we would like to
because of missing cross-type equality operators in the underlying btree
operator family. That code path is more or less entirely untested by
the regression tests to date, because no standard opfamilies have such
holes in them. So I wrote a new regression test script to try to exercise
it a bit, which turned out to be quite a worthwhile activity as it exposed
existing bugs in all supported branches.
The present patch is essentially the same as far back as 9.2, which is
where parameterized paths were introduced. In 9.0 and 9.1, we only need
to back-patch a small fragment of commit 5b7b5518d, which fixes failure to
propagate out the original WHERE clauses when a broken EC contains constant
members. (The regression test case results show that these older branches
are noticeably stupider than 9.2+ in terms of the quality of the plans
generated; but we don't really care about plan quality in such cases,
only that the plan not be outright wrong. A more invasive fix in the
older branches would not be a good idea anyway from a plan-stability
standpoint.)
2014-10-02 01:30:24 +02:00
|
|
|
-> Seq Scan on ec2
|
2015-03-30 20:59:49 +02:00
|
|
|
Filter: ('42'::bigint = x1)
|
Fix some more problems with nested append relations.
As of commit a87c72915 (which later got backpatched as far as 9.1),
we're explicitly supporting the notion that append relations can be
nested; this can occur when UNION ALL constructs are nested, or when
a UNION ALL contains a table with inheritance children.
Bug #11457 from Nelson Page, as well as an earlier report from Elvis
Pranskevichus, showed that there were still nasty bugs associated with such
cases: in particular the EquivalenceClass mechanism could try to generate
"join" clauses connecting an appendrel child to some grandparent appendrel,
which would result in assertion failures or bogus plans.
Upon investigation I concluded that all current callers of
find_childrel_appendrelinfo() need to be fixed to explicitly consider
multiple levels of parent appendrels. The most complex fix was in
processing of "broken" EquivalenceClasses, which are ECs for which we have
been unable to generate all the derived equality clauses we would like to
because of missing cross-type equality operators in the underlying btree
operator family. That code path is more or less entirely untested by
the regression tests to date, because no standard opfamilies have such
holes in them. So I wrote a new regression test script to try to exercise
it a bit, which turned out to be quite a worthwhile activity as it exposed
existing bugs in all supported branches.
The present patch is essentially the same as far back as 9.2, which is
where parameterized paths were introduced. In 9.0 and 9.1, we only need
to back-patch a small fragment of commit 5b7b5518d, which fixes failure to
propagate out the original WHERE clauses when a broken EC contains constant
members. (The regression test case results show that these older branches
are noticeably stupider than 9.2+ in terms of the quality of the plans
generated; but we don't really care about plan quality in such cases,
only that the plan not be outright wrong. A more invasive fix in the
older branches would not be a good idea anyway from a plan-stability
standpoint.)
2014-10-02 01:30:24 +02:00
|
|
|
(6 rows)
|
|
|
|
|
|
|
|
explain (costs off)
|
|
|
|
select * from ec1, ec2 where ff = x1 and x1 = '42'::int8alias1;
|
|
|
|
QUERY PLAN
|
|
|
|
---------------------------------------------
|
|
|
|
Nested Loop
|
|
|
|
-> Index Scan using ec1_pkey on ec1
|
|
|
|
Index Cond: (ff = '42'::int8alias1)
|
|
|
|
-> Seq Scan on ec2
|
|
|
|
Filter: (x1 = '42'::int8alias1)
|
|
|
|
(5 rows)
|
|
|
|
|
|
|
|
explain (costs off)
|
|
|
|
select * from ec1, ec2 where ff = x1 and x1 = '42'::int8alias2;
|
|
|
|
QUERY PLAN
|
|
|
|
-----------------------------------------
|
|
|
|
Nested Loop
|
|
|
|
-> Seq Scan on ec2
|
|
|
|
Filter: (x1 = '42'::int8alias2)
|
|
|
|
-> Index Scan using ec1_pkey on ec1
|
|
|
|
Index Cond: (ff = ec2.x1)
|
|
|
|
(5 rows)
|
|
|
|
|
|
|
|
create unique index ec1_expr1 on ec1((ff + 1));
|
|
|
|
create unique index ec1_expr2 on ec1((ff + 2 + 1));
|
|
|
|
create unique index ec1_expr3 on ec1((ff + 3 + 1));
|
|
|
|
create unique index ec1_expr4 on ec1((ff + 4));
|
|
|
|
explain (costs off)
|
|
|
|
select * from ec1,
|
|
|
|
(select ff + 1 as x from
|
|
|
|
(select ff + 2 as ff from ec1
|
|
|
|
union all
|
|
|
|
select ff + 3 as ff from ec1) ss0
|
|
|
|
union all
|
|
|
|
select ff + 4 as x from ec1) as ss1
|
|
|
|
where ss1.x = ec1.f1 and ec1.ff = 42::int8;
|
|
|
|
QUERY PLAN
|
|
|
|
-----------------------------------------------------
|
|
|
|
Nested Loop
|
|
|
|
-> Index Scan using ec1_pkey on ec1
|
2015-03-30 20:59:49 +02:00
|
|
|
Index Cond: (ff = '42'::bigint)
|
Fix some more problems with nested append relations.
As of commit a87c72915 (which later got backpatched as far as 9.1),
we're explicitly supporting the notion that append relations can be
nested; this can occur when UNION ALL constructs are nested, or when
a UNION ALL contains a table with inheritance children.
Bug #11457 from Nelson Page, as well as an earlier report from Elvis
Pranskevichus, showed that there were still nasty bugs associated with such
cases: in particular the EquivalenceClass mechanism could try to generate
"join" clauses connecting an appendrel child to some grandparent appendrel,
which would result in assertion failures or bogus plans.
Upon investigation I concluded that all current callers of
find_childrel_appendrelinfo() need to be fixed to explicitly consider
multiple levels of parent appendrels. The most complex fix was in
processing of "broken" EquivalenceClasses, which are ECs for which we have
been unable to generate all the derived equality clauses we would like to
because of missing cross-type equality operators in the underlying btree
operator family. That code path is more or less entirely untested by
the regression tests to date, because no standard opfamilies have such
holes in them. So I wrote a new regression test script to try to exercise
it a bit, which turned out to be quite a worthwhile activity as it exposed
existing bugs in all supported branches.
The present patch is essentially the same as far back as 9.2, which is
where parameterized paths were introduced. In 9.0 and 9.1, we only need
to back-patch a small fragment of commit 5b7b5518d, which fixes failure to
propagate out the original WHERE clauses when a broken EC contains constant
members. (The regression test case results show that these older branches
are noticeably stupider than 9.2+ in terms of the quality of the plans
generated; but we don't really care about plan quality in such cases,
only that the plan not be outright wrong. A more invasive fix in the
older branches would not be a good idea anyway from a plan-stability
standpoint.)
2014-10-02 01:30:24 +02:00
|
|
|
-> Append
|
|
|
|
-> Index Scan using ec1_expr2 on ec1 ec1_1
|
|
|
|
Index Cond: (((ff + 2) + 1) = ec1.f1)
|
|
|
|
-> Index Scan using ec1_expr3 on ec1 ec1_2
|
|
|
|
Index Cond: (((ff + 3) + 1) = ec1.f1)
|
|
|
|
-> Index Scan using ec1_expr4 on ec1 ec1_3
|
|
|
|
Index Cond: ((ff + 4) = ec1.f1)
|
|
|
|
(10 rows)
|
|
|
|
|
|
|
|
explain (costs off)
|
|
|
|
select * from ec1,
|
|
|
|
(select ff + 1 as x from
|
|
|
|
(select ff + 2 as ff from ec1
|
|
|
|
union all
|
|
|
|
select ff + 3 as ff from ec1) ss0
|
|
|
|
union all
|
|
|
|
select ff + 4 as x from ec1) as ss1
|
|
|
|
where ss1.x = ec1.f1 and ec1.ff = 42::int8 and ec1.ff = ec1.f1;
|
2015-03-30 20:59:49 +02:00
|
|
|
QUERY PLAN
|
|
|
|
-------------------------------------------------------------------
|
Fix some more problems with nested append relations.
As of commit a87c72915 (which later got backpatched as far as 9.1),
we're explicitly supporting the notion that append relations can be
nested; this can occur when UNION ALL constructs are nested, or when
a UNION ALL contains a table with inheritance children.
Bug #11457 from Nelson Page, as well as an earlier report from Elvis
Pranskevichus, showed that there were still nasty bugs associated with such
cases: in particular the EquivalenceClass mechanism could try to generate
"join" clauses connecting an appendrel child to some grandparent appendrel,
which would result in assertion failures or bogus plans.
Upon investigation I concluded that all current callers of
find_childrel_appendrelinfo() need to be fixed to explicitly consider
multiple levels of parent appendrels. The most complex fix was in
processing of "broken" EquivalenceClasses, which are ECs for which we have
been unable to generate all the derived equality clauses we would like to
because of missing cross-type equality operators in the underlying btree
operator family. That code path is more or less entirely untested by
the regression tests to date, because no standard opfamilies have such
holes in them. So I wrote a new regression test script to try to exercise
it a bit, which turned out to be quite a worthwhile activity as it exposed
existing bugs in all supported branches.
The present patch is essentially the same as far back as 9.2, which is
where parameterized paths were introduced. In 9.0 and 9.1, we only need
to back-patch a small fragment of commit 5b7b5518d, which fixes failure to
propagate out the original WHERE clauses when a broken EC contains constant
members. (The regression test case results show that these older branches
are noticeably stupider than 9.2+ in terms of the quality of the plans
generated; but we don't really care about plan quality in such cases,
only that the plan not be outright wrong. A more invasive fix in the
older branches would not be a good idea anyway from a plan-stability
standpoint.)
2014-10-02 01:30:24 +02:00
|
|
|
Nested Loop
|
|
|
|
Join Filter: ((((ec1_1.ff + 2) + 1)) = ec1.f1)
|
|
|
|
-> Index Scan using ec1_pkey on ec1
|
2015-03-30 20:59:49 +02:00
|
|
|
Index Cond: ((ff = '42'::bigint) AND (ff = '42'::bigint))
|
Fix some more problems with nested append relations.
As of commit a87c72915 (which later got backpatched as far as 9.1),
we're explicitly supporting the notion that append relations can be
nested; this can occur when UNION ALL constructs are nested, or when
a UNION ALL contains a table with inheritance children.
Bug #11457 from Nelson Page, as well as an earlier report from Elvis
Pranskevichus, showed that there were still nasty bugs associated with such
cases: in particular the EquivalenceClass mechanism could try to generate
"join" clauses connecting an appendrel child to some grandparent appendrel,
which would result in assertion failures or bogus plans.
Upon investigation I concluded that all current callers of
find_childrel_appendrelinfo() need to be fixed to explicitly consider
multiple levels of parent appendrels. The most complex fix was in
processing of "broken" EquivalenceClasses, which are ECs for which we have
been unable to generate all the derived equality clauses we would like to
because of missing cross-type equality operators in the underlying btree
operator family. That code path is more or less entirely untested by
the regression tests to date, because no standard opfamilies have such
holes in them. So I wrote a new regression test script to try to exercise
it a bit, which turned out to be quite a worthwhile activity as it exposed
existing bugs in all supported branches.
The present patch is essentially the same as far back as 9.2, which is
where parameterized paths were introduced. In 9.0 and 9.1, we only need
to back-patch a small fragment of commit 5b7b5518d, which fixes failure to
propagate out the original WHERE clauses when a broken EC contains constant
members. (The regression test case results show that these older branches
are noticeably stupider than 9.2+ in terms of the quality of the plans
generated; but we don't really care about plan quality in such cases,
only that the plan not be outright wrong. A more invasive fix in the
older branches would not be a good idea anyway from a plan-stability
standpoint.)
2014-10-02 01:30:24 +02:00
|
|
|
Filter: (ff = f1)
|
|
|
|
-> Append
|
|
|
|
-> Index Scan using ec1_expr2 on ec1 ec1_1
|
2015-03-30 20:59:49 +02:00
|
|
|
Index Cond: (((ff + 2) + 1) = '42'::bigint)
|
Fix some more problems with nested append relations.
As of commit a87c72915 (which later got backpatched as far as 9.1),
we're explicitly supporting the notion that append relations can be
nested; this can occur when UNION ALL constructs are nested, or when
a UNION ALL contains a table with inheritance children.
Bug #11457 from Nelson Page, as well as an earlier report from Elvis
Pranskevichus, showed that there were still nasty bugs associated with such
cases: in particular the EquivalenceClass mechanism could try to generate
"join" clauses connecting an appendrel child to some grandparent appendrel,
which would result in assertion failures or bogus plans.
Upon investigation I concluded that all current callers of
find_childrel_appendrelinfo() need to be fixed to explicitly consider
multiple levels of parent appendrels. The most complex fix was in
processing of "broken" EquivalenceClasses, which are ECs for which we have
been unable to generate all the derived equality clauses we would like to
because of missing cross-type equality operators in the underlying btree
operator family. That code path is more or less entirely untested by
the regression tests to date, because no standard opfamilies have such
holes in them. So I wrote a new regression test script to try to exercise
it a bit, which turned out to be quite a worthwhile activity as it exposed
existing bugs in all supported branches.
The present patch is essentially the same as far back as 9.2, which is
where parameterized paths were introduced. In 9.0 and 9.1, we only need
to back-patch a small fragment of commit 5b7b5518d, which fixes failure to
propagate out the original WHERE clauses when a broken EC contains constant
members. (The regression test case results show that these older branches
are noticeably stupider than 9.2+ in terms of the quality of the plans
generated; but we don't really care about plan quality in such cases,
only that the plan not be outright wrong. A more invasive fix in the
older branches would not be a good idea anyway from a plan-stability
standpoint.)
2014-10-02 01:30:24 +02:00
|
|
|
-> Index Scan using ec1_expr3 on ec1 ec1_2
|
2015-03-30 20:59:49 +02:00
|
|
|
Index Cond: (((ff + 3) + 1) = '42'::bigint)
|
Fix some more problems with nested append relations.
As of commit a87c72915 (which later got backpatched as far as 9.1),
we're explicitly supporting the notion that append relations can be
nested; this can occur when UNION ALL constructs are nested, or when
a UNION ALL contains a table with inheritance children.
Bug #11457 from Nelson Page, as well as an earlier report from Elvis
Pranskevichus, showed that there were still nasty bugs associated with such
cases: in particular the EquivalenceClass mechanism could try to generate
"join" clauses connecting an appendrel child to some grandparent appendrel,
which would result in assertion failures or bogus plans.
Upon investigation I concluded that all current callers of
find_childrel_appendrelinfo() need to be fixed to explicitly consider
multiple levels of parent appendrels. The most complex fix was in
processing of "broken" EquivalenceClasses, which are ECs for which we have
been unable to generate all the derived equality clauses we would like to
because of missing cross-type equality operators in the underlying btree
operator family. That code path is more or less entirely untested by
the regression tests to date, because no standard opfamilies have such
holes in them. So I wrote a new regression test script to try to exercise
it a bit, which turned out to be quite a worthwhile activity as it exposed
existing bugs in all supported branches.
The present patch is essentially the same as far back as 9.2, which is
where parameterized paths were introduced. In 9.0 and 9.1, we only need
to back-patch a small fragment of commit 5b7b5518d, which fixes failure to
propagate out the original WHERE clauses when a broken EC contains constant
members. (The regression test case results show that these older branches
are noticeably stupider than 9.2+ in terms of the quality of the plans
generated; but we don't really care about plan quality in such cases,
only that the plan not be outright wrong. A more invasive fix in the
older branches would not be a good idea anyway from a plan-stability
standpoint.)
2014-10-02 01:30:24 +02:00
|
|
|
-> Index Scan using ec1_expr4 on ec1 ec1_3
|
2015-03-30 20:59:49 +02:00
|
|
|
Index Cond: ((ff + 4) = '42'::bigint)
|
Fix some more problems with nested append relations.
As of commit a87c72915 (which later got backpatched as far as 9.1),
we're explicitly supporting the notion that append relations can be
nested; this can occur when UNION ALL constructs are nested, or when
a UNION ALL contains a table with inheritance children.
Bug #11457 from Nelson Page, as well as an earlier report from Elvis
Pranskevichus, showed that there were still nasty bugs associated with such
cases: in particular the EquivalenceClass mechanism could try to generate
"join" clauses connecting an appendrel child to some grandparent appendrel,
which would result in assertion failures or bogus plans.
Upon investigation I concluded that all current callers of
find_childrel_appendrelinfo() need to be fixed to explicitly consider
multiple levels of parent appendrels. The most complex fix was in
processing of "broken" EquivalenceClasses, which are ECs for which we have
been unable to generate all the derived equality clauses we would like to
because of missing cross-type equality operators in the underlying btree
operator family. That code path is more or less entirely untested by
the regression tests to date, because no standard opfamilies have such
holes in them. So I wrote a new regression test script to try to exercise
it a bit, which turned out to be quite a worthwhile activity as it exposed
existing bugs in all supported branches.
The present patch is essentially the same as far back as 9.2, which is
where parameterized paths were introduced. In 9.0 and 9.1, we only need
to back-patch a small fragment of commit 5b7b5518d, which fixes failure to
propagate out the original WHERE clauses when a broken EC contains constant
members. (The regression test case results show that these older branches
are noticeably stupider than 9.2+ in terms of the quality of the plans
generated; but we don't really care about plan quality in such cases,
only that the plan not be outright wrong. A more invasive fix in the
older branches would not be a good idea anyway from a plan-stability
standpoint.)
2014-10-02 01:30:24 +02:00
|
|
|
(12 rows)
|
|
|
|
|
|
|
|
explain (costs off)
|
|
|
|
select * from ec1,
|
|
|
|
(select ff + 1 as x from
|
|
|
|
(select ff + 2 as ff from ec1
|
|
|
|
union all
|
|
|
|
select ff + 3 as ff from ec1) ss0
|
|
|
|
union all
|
|
|
|
select ff + 4 as x from ec1) as ss1,
|
|
|
|
(select ff + 1 as x from
|
|
|
|
(select ff + 2 as ff from ec1
|
|
|
|
union all
|
|
|
|
select ff + 3 as ff from ec1) ss0
|
|
|
|
union all
|
|
|
|
select ff + 4 as x from ec1) as ss2
|
|
|
|
where ss1.x = ec1.f1 and ss1.x = ss2.x and ec1.ff = 42::int8;
|
|
|
|
QUERY PLAN
|
|
|
|
---------------------------------------------------------------------
|
|
|
|
Nested Loop
|
|
|
|
-> Nested Loop
|
|
|
|
-> Index Scan using ec1_pkey on ec1
|
2015-03-30 20:59:49 +02:00
|
|
|
Index Cond: (ff = '42'::bigint)
|
Fix some more problems with nested append relations.
As of commit a87c72915 (which later got backpatched as far as 9.1),
we're explicitly supporting the notion that append relations can be
nested; this can occur when UNION ALL constructs are nested, or when
a UNION ALL contains a table with inheritance children.
Bug #11457 from Nelson Page, as well as an earlier report from Elvis
Pranskevichus, showed that there were still nasty bugs associated with such
cases: in particular the EquivalenceClass mechanism could try to generate
"join" clauses connecting an appendrel child to some grandparent appendrel,
which would result in assertion failures or bogus plans.
Upon investigation I concluded that all current callers of
find_childrel_appendrelinfo() need to be fixed to explicitly consider
multiple levels of parent appendrels. The most complex fix was in
processing of "broken" EquivalenceClasses, which are ECs for which we have
been unable to generate all the derived equality clauses we would like to
because of missing cross-type equality operators in the underlying btree
operator family. That code path is more or less entirely untested by
the regression tests to date, because no standard opfamilies have such
holes in them. So I wrote a new regression test script to try to exercise
it a bit, which turned out to be quite a worthwhile activity as it exposed
existing bugs in all supported branches.
The present patch is essentially the same as far back as 9.2, which is
where parameterized paths were introduced. In 9.0 and 9.1, we only need
to back-patch a small fragment of commit 5b7b5518d, which fixes failure to
propagate out the original WHERE clauses when a broken EC contains constant
members. (The regression test case results show that these older branches
are noticeably stupider than 9.2+ in terms of the quality of the plans
generated; but we don't really care about plan quality in such cases,
only that the plan not be outright wrong. A more invasive fix in the
older branches would not be a good idea anyway from a plan-stability
standpoint.)
2014-10-02 01:30:24 +02:00
|
|
|
-> Append
|
|
|
|
-> Index Scan using ec1_expr2 on ec1 ec1_1
|
|
|
|
Index Cond: (((ff + 2) + 1) = ec1.f1)
|
|
|
|
-> Index Scan using ec1_expr3 on ec1 ec1_2
|
|
|
|
Index Cond: (((ff + 3) + 1) = ec1.f1)
|
|
|
|
-> Index Scan using ec1_expr4 on ec1 ec1_3
|
|
|
|
Index Cond: ((ff + 4) = ec1.f1)
|
|
|
|
-> Append
|
|
|
|
-> Index Scan using ec1_expr2 on ec1 ec1_4
|
|
|
|
Index Cond: (((ff + 2) + 1) = (((ec1_1.ff + 2) + 1)))
|
|
|
|
-> Index Scan using ec1_expr3 on ec1 ec1_5
|
|
|
|
Index Cond: (((ff + 3) + 1) = (((ec1_1.ff + 2) + 1)))
|
|
|
|
-> Index Scan using ec1_expr4 on ec1 ec1_6
|
|
|
|
Index Cond: ((ff + 4) = (((ec1_1.ff + 2) + 1)))
|
|
|
|
(18 rows)
|
|
|
|
|
|
|
|
-- let's try that as a mergejoin
|
|
|
|
set enable_mergejoin = on;
|
|
|
|
set enable_nestloop = off;
|
|
|
|
explain (costs off)
|
|
|
|
select * from ec1,
|
|
|
|
(select ff + 1 as x from
|
|
|
|
(select ff + 2 as ff from ec1
|
|
|
|
union all
|
|
|
|
select ff + 3 as ff from ec1) ss0
|
|
|
|
union all
|
|
|
|
select ff + 4 as x from ec1) as ss1,
|
|
|
|
(select ff + 1 as x from
|
|
|
|
(select ff + 2 as ff from ec1
|
|
|
|
union all
|
|
|
|
select ff + 3 as ff from ec1) ss0
|
|
|
|
union all
|
|
|
|
select ff + 4 as x from ec1) as ss2
|
|
|
|
where ss1.x = ec1.f1 and ss1.x = ss2.x and ec1.ff = 42::int8;
|
|
|
|
QUERY PLAN
|
|
|
|
-----------------------------------------------------------------
|
|
|
|
Merge Join
|
|
|
|
Merge Cond: ((((ec1_4.ff + 2) + 1)) = (((ec1_1.ff + 2) + 1)))
|
|
|
|
-> Merge Append
|
|
|
|
Sort Key: (((ec1_4.ff + 2) + 1))
|
|
|
|
-> Index Scan using ec1_expr2 on ec1 ec1_4
|
|
|
|
-> Index Scan using ec1_expr3 on ec1 ec1_5
|
|
|
|
-> Index Scan using ec1_expr4 on ec1 ec1_6
|
|
|
|
-> Materialize
|
|
|
|
-> Merge Join
|
|
|
|
Merge Cond: ((((ec1_1.ff + 2) + 1)) = ec1.f1)
|
|
|
|
-> Merge Append
|
|
|
|
Sort Key: (((ec1_1.ff + 2) + 1))
|
|
|
|
-> Index Scan using ec1_expr2 on ec1 ec1_1
|
|
|
|
-> Index Scan using ec1_expr3 on ec1 ec1_2
|
|
|
|
-> Index Scan using ec1_expr4 on ec1 ec1_3
|
|
|
|
-> Materialize
|
|
|
|
-> Sort
|
2015-01-17 00:18:52 +01:00
|
|
|
Sort Key: ec1.f1 USING <
|
Fix some more problems with nested append relations.
As of commit a87c72915 (which later got backpatched as far as 9.1),
we're explicitly supporting the notion that append relations can be
nested; this can occur when UNION ALL constructs are nested, or when
a UNION ALL contains a table with inheritance children.
Bug #11457 from Nelson Page, as well as an earlier report from Elvis
Pranskevichus, showed that there were still nasty bugs associated with such
cases: in particular the EquivalenceClass mechanism could try to generate
"join" clauses connecting an appendrel child to some grandparent appendrel,
which would result in assertion failures or bogus plans.
Upon investigation I concluded that all current callers of
find_childrel_appendrelinfo() need to be fixed to explicitly consider
multiple levels of parent appendrels. The most complex fix was in
processing of "broken" EquivalenceClasses, which are ECs for which we have
been unable to generate all the derived equality clauses we would like to
because of missing cross-type equality operators in the underlying btree
operator family. That code path is more or less entirely untested by
the regression tests to date, because no standard opfamilies have such
holes in them. So I wrote a new regression test script to try to exercise
it a bit, which turned out to be quite a worthwhile activity as it exposed
existing bugs in all supported branches.
The present patch is essentially the same as far back as 9.2, which is
where parameterized paths were introduced. In 9.0 and 9.1, we only need
to back-patch a small fragment of commit 5b7b5518d, which fixes failure to
propagate out the original WHERE clauses when a broken EC contains constant
members. (The regression test case results show that these older branches
are noticeably stupider than 9.2+ in terms of the quality of the plans
generated; but we don't really care about plan quality in such cases,
only that the plan not be outright wrong. A more invasive fix in the
older branches would not be a good idea anyway from a plan-stability
standpoint.)
2014-10-02 01:30:24 +02:00
|
|
|
-> Index Scan using ec1_pkey on ec1
|
2015-03-30 20:59:49 +02:00
|
|
|
Index Cond: (ff = '42'::bigint)
|
Fix some more problems with nested append relations.
As of commit a87c72915 (which later got backpatched as far as 9.1),
we're explicitly supporting the notion that append relations can be
nested; this can occur when UNION ALL constructs are nested, or when
a UNION ALL contains a table with inheritance children.
Bug #11457 from Nelson Page, as well as an earlier report from Elvis
Pranskevichus, showed that there were still nasty bugs associated with such
cases: in particular the EquivalenceClass mechanism could try to generate
"join" clauses connecting an appendrel child to some grandparent appendrel,
which would result in assertion failures or bogus plans.
Upon investigation I concluded that all current callers of
find_childrel_appendrelinfo() need to be fixed to explicitly consider
multiple levels of parent appendrels. The most complex fix was in
processing of "broken" EquivalenceClasses, which are ECs for which we have
been unable to generate all the derived equality clauses we would like to
because of missing cross-type equality operators in the underlying btree
operator family. That code path is more or less entirely untested by
the regression tests to date, because no standard opfamilies have such
holes in them. So I wrote a new regression test script to try to exercise
it a bit, which turned out to be quite a worthwhile activity as it exposed
existing bugs in all supported branches.
The present patch is essentially the same as far back as 9.2, which is
where parameterized paths were introduced. In 9.0 and 9.1, we only need
to back-patch a small fragment of commit 5b7b5518d, which fixes failure to
propagate out the original WHERE clauses when a broken EC contains constant
members. (The regression test case results show that these older branches
are noticeably stupider than 9.2+ in terms of the quality of the plans
generated; but we don't really care about plan quality in such cases,
only that the plan not be outright wrong. A more invasive fix in the
older branches would not be a good idea anyway from a plan-stability
standpoint.)
2014-10-02 01:30:24 +02:00
|
|
|
(20 rows)
|
|
|
|
|
|
|
|
-- check partially indexed scan
|
|
|
|
set enable_nestloop = on;
|
|
|
|
set enable_mergejoin = off;
|
|
|
|
drop index ec1_expr3;
|
|
|
|
explain (costs off)
|
|
|
|
select * from ec1,
|
|
|
|
(select ff + 1 as x from
|
|
|
|
(select ff + 2 as ff from ec1
|
|
|
|
union all
|
|
|
|
select ff + 3 as ff from ec1) ss0
|
|
|
|
union all
|
|
|
|
select ff + 4 as x from ec1) as ss1
|
|
|
|
where ss1.x = ec1.f1 and ec1.ff = 42::int8;
|
|
|
|
QUERY PLAN
|
|
|
|
-----------------------------------------------------
|
|
|
|
Nested Loop
|
|
|
|
-> Index Scan using ec1_pkey on ec1
|
2015-03-30 20:59:49 +02:00
|
|
|
Index Cond: (ff = '42'::bigint)
|
Fix some more problems with nested append relations.
As of commit a87c72915 (which later got backpatched as far as 9.1),
we're explicitly supporting the notion that append relations can be
nested; this can occur when UNION ALL constructs are nested, or when
a UNION ALL contains a table with inheritance children.
Bug #11457 from Nelson Page, as well as an earlier report from Elvis
Pranskevichus, showed that there were still nasty bugs associated with such
cases: in particular the EquivalenceClass mechanism could try to generate
"join" clauses connecting an appendrel child to some grandparent appendrel,
which would result in assertion failures or bogus plans.
Upon investigation I concluded that all current callers of
find_childrel_appendrelinfo() need to be fixed to explicitly consider
multiple levels of parent appendrels. The most complex fix was in
processing of "broken" EquivalenceClasses, which are ECs for which we have
been unable to generate all the derived equality clauses we would like to
because of missing cross-type equality operators in the underlying btree
operator family. That code path is more or less entirely untested by
the regression tests to date, because no standard opfamilies have such
holes in them. So I wrote a new regression test script to try to exercise
it a bit, which turned out to be quite a worthwhile activity as it exposed
existing bugs in all supported branches.
The present patch is essentially the same as far back as 9.2, which is
where parameterized paths were introduced. In 9.0 and 9.1, we only need
to back-patch a small fragment of commit 5b7b5518d, which fixes failure to
propagate out the original WHERE clauses when a broken EC contains constant
members. (The regression test case results show that these older branches
are noticeably stupider than 9.2+ in terms of the quality of the plans
generated; but we don't really care about plan quality in such cases,
only that the plan not be outright wrong. A more invasive fix in the
older branches would not be a good idea anyway from a plan-stability
standpoint.)
2014-10-02 01:30:24 +02:00
|
|
|
-> Append
|
|
|
|
-> Index Scan using ec1_expr2 on ec1 ec1_1
|
|
|
|
Index Cond: (((ff + 2) + 1) = ec1.f1)
|
|
|
|
-> Seq Scan on ec1 ec1_2
|
|
|
|
Filter: (((ff + 3) + 1) = ec1.f1)
|
|
|
|
-> Index Scan using ec1_expr4 on ec1 ec1_3
|
|
|
|
Index Cond: ((ff + 4) = ec1.f1)
|
|
|
|
(10 rows)
|
|
|
|
|
|
|
|
-- let's try that as a mergejoin
|
|
|
|
set enable_mergejoin = on;
|
|
|
|
set enable_nestloop = off;
|
|
|
|
explain (costs off)
|
|
|
|
select * from ec1,
|
|
|
|
(select ff + 1 as x from
|
|
|
|
(select ff + 2 as ff from ec1
|
|
|
|
union all
|
|
|
|
select ff + 3 as ff from ec1) ss0
|
|
|
|
union all
|
|
|
|
select ff + 4 as x from ec1) as ss1
|
|
|
|
where ss1.x = ec1.f1 and ec1.ff = 42::int8;
|
|
|
|
QUERY PLAN
|
|
|
|
-----------------------------------------------------
|
|
|
|
Merge Join
|
|
|
|
Merge Cond: ((((ec1_1.ff + 2) + 1)) = ec1.f1)
|
|
|
|
-> Merge Append
|
|
|
|
Sort Key: (((ec1_1.ff + 2) + 1))
|
|
|
|
-> Index Scan using ec1_expr2 on ec1 ec1_1
|
|
|
|
-> Sort
|
|
|
|
Sort Key: (((ec1_2.ff + 3) + 1))
|
|
|
|
-> Seq Scan on ec1 ec1_2
|
|
|
|
-> Index Scan using ec1_expr4 on ec1 ec1_3
|
|
|
|
-> Materialize
|
|
|
|
-> Sort
|
2015-01-17 00:18:52 +01:00
|
|
|
Sort Key: ec1.f1 USING <
|
Fix some more problems with nested append relations.
As of commit a87c72915 (which later got backpatched as far as 9.1),
we're explicitly supporting the notion that append relations can be
nested; this can occur when UNION ALL constructs are nested, or when
a UNION ALL contains a table with inheritance children.
Bug #11457 from Nelson Page, as well as an earlier report from Elvis
Pranskevichus, showed that there were still nasty bugs associated with such
cases: in particular the EquivalenceClass mechanism could try to generate
"join" clauses connecting an appendrel child to some grandparent appendrel,
which would result in assertion failures or bogus plans.
Upon investigation I concluded that all current callers of
find_childrel_appendrelinfo() need to be fixed to explicitly consider
multiple levels of parent appendrels. The most complex fix was in
processing of "broken" EquivalenceClasses, which are ECs for which we have
been unable to generate all the derived equality clauses we would like to
because of missing cross-type equality operators in the underlying btree
operator family. That code path is more or less entirely untested by
the regression tests to date, because no standard opfamilies have such
holes in them. So I wrote a new regression test script to try to exercise
it a bit, which turned out to be quite a worthwhile activity as it exposed
existing bugs in all supported branches.
The present patch is essentially the same as far back as 9.2, which is
where parameterized paths were introduced. In 9.0 and 9.1, we only need
to back-patch a small fragment of commit 5b7b5518d, which fixes failure to
propagate out the original WHERE clauses when a broken EC contains constant
members. (The regression test case results show that these older branches
are noticeably stupider than 9.2+ in terms of the quality of the plans
generated; but we don't really care about plan quality in such cases,
only that the plan not be outright wrong. A more invasive fix in the
older branches would not be a good idea anyway from a plan-stability
standpoint.)
2014-10-02 01:30:24 +02:00
|
|
|
-> Index Scan using ec1_pkey on ec1
|
2015-03-30 20:59:49 +02:00
|
|
|
Index Cond: (ff = '42'::bigint)
|
Fix some more problems with nested append relations.
As of commit a87c72915 (which later got backpatched as far as 9.1),
we're explicitly supporting the notion that append relations can be
nested; this can occur when UNION ALL constructs are nested, or when
a UNION ALL contains a table with inheritance children.
Bug #11457 from Nelson Page, as well as an earlier report from Elvis
Pranskevichus, showed that there were still nasty bugs associated with such
cases: in particular the EquivalenceClass mechanism could try to generate
"join" clauses connecting an appendrel child to some grandparent appendrel,
which would result in assertion failures or bogus plans.
Upon investigation I concluded that all current callers of
find_childrel_appendrelinfo() need to be fixed to explicitly consider
multiple levels of parent appendrels. The most complex fix was in
processing of "broken" EquivalenceClasses, which are ECs for which we have
been unable to generate all the derived equality clauses we would like to
because of missing cross-type equality operators in the underlying btree
operator family. That code path is more or less entirely untested by
the regression tests to date, because no standard opfamilies have such
holes in them. So I wrote a new regression test script to try to exercise
it a bit, which turned out to be quite a worthwhile activity as it exposed
existing bugs in all supported branches.
The present patch is essentially the same as far back as 9.2, which is
where parameterized paths were introduced. In 9.0 and 9.1, we only need
to back-patch a small fragment of commit 5b7b5518d, which fixes failure to
propagate out the original WHERE clauses when a broken EC contains constant
members. (The regression test case results show that these older branches
are noticeably stupider than 9.2+ in terms of the quality of the plans
generated; but we don't really care about plan quality in such cases,
only that the plan not be outright wrong. A more invasive fix in the
older branches would not be a good idea anyway from a plan-stability
standpoint.)
2014-10-02 01:30:24 +02:00
|
|
|
(14 rows)
|
|
|
|
|