I'm wondering if we can keep the per-child quals in AppendRelInfos, and
then apply these quals when we create RelOptInfos for the children of an
appendrel, specifically in expand_appendrel_subquery().
I have a go at this and it can fix the origin problem.
EXPLAIN (COSTS OFF)
WITH
targets AS (
SELECT 'bike' AS vehicle, id, dealer_name, frame_size FROM bikes WHERE
frame_size = 52
UNION ALL
SELECT 'car' AS vehicle, id, dealer_name, null::int AS frame_size FROM
cars
)
SELECT
dealers.name dealer,
targets.vehicle,
targets.idFROM
dealers
JOIN targets
ON
dealers.name = targets.dealer_name
WHERE
dealers.id IN (54,12,456);
QUERY PLAN
--------------------------------------------------------------
Nested Loop
-> Index Scan using dealers_pkey on dealers
Index Cond: (id = ANY ('{54,12,456}'::integer[]))
-> Append
-> Bitmap Heap Scan on bikes
Recheck Cond: (dealer_name =
dealers.name)
Filter: (frame_size = 52)
-> Bitmap Index Scan on bikes_dealer_name_idx
Index Cond: (dealer_name =
dealers.name)
-> Bitmap Heap Scan on cars
Recheck Cond: (dealer_name =
dealers.name)
-> Bitmap Index Scan on cars_dealer_name_idx
Index Cond: (dealer_name =
dealers.name)
(13 rows)
However, when applying the per-child quals in expand_appendrel_subquery,
I cannot find a way to make these quals go through the EC machinery.
And that would cause us to miss some optimal paths, such as
EXPLAIN (COSTS OFF)
SELECT 'bike' AS vehicle, id, dealer_name, frame_size FROM bikes WHERE
frame_size = 52 and frame_size = id
UNION ALL
SELECT 'car' AS vehicle, id, dealer_name, null::int AS frame_size FROM
cars;
QUERY PLAN
-----------------------------------------------------------
Append
-> Seq Scan on bikes
Filter: ((frame_size = 52) AND (frame_size = id))
-> Seq Scan on cars
(4 rows)
We should have been able to get '
bikes.id = 52' from '(frame_size = 52)
AND (frame_size = id)', and then use index scan on 'bikes', but ...
Maybe we can achieve that with more efforts, but I'm not sure if this is
worthwhile. Any thoughts?
Thanks
Richard
