fix cost subqueryscan wrong parallel cost - Mailing list pgsql-hackers

From bucoo@sohu.com
Subject fix cost subqueryscan wrong parallel cost
Date
Msg-id 202204121457159307248@sohu.com
Whole thread Raw
Responses Re: fix cost subqueryscan wrong parallel cost  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
The cost_subqueryscan function does not judge whether it is parallel.
regress
-- Incremental sort vs. set operations with varno 0
set enable_hashagg to off;
explain (costs off) select * from t union select * from t order by 1,3;
                        QUERY PLAN                        
----------------------------------------------------------
 Incremental Sort
   Sort Key: t.a, t.c
   Presorted Key: t.a
   ->  Unique
         ->  Sort
               Sort Key: t.a, t.b, t.c
               ->  Append
                     ->  Gather
                           Workers Planned: 2
                           ->  Parallel Seq Scan on t
                     ->  Gather
                           Workers Planned: 2
                           ->  Parallel Seq Scan on t t_1
to
 Incremental Sort
   Sort Key: t.a, t.c
   Presorted Key: t.a
   ->  Unique
         ->  Sort
               Sort Key: t.a, t.b, t.c
               ->  Gather
                     Workers Planned: 2
                     ->  Parallel Append
                           ->  Parallel Seq Scan on t
                           ->  Parallel Seq Scan on t t_1
Obviously the latter is less expensive


bucoo@sohu.com
Attachment

pgsql-hackers by date:

Previous
From: vignesh C
Date:
Subject: Re: Handle infinite recursion in logical replication setup
Next
From: Alvaro Herrera
Date:
Subject: Re: MERGE bug report