Re: Interpreting postgres execution plan along with AND/OR precedence

2023-01-18 Thread Erik Wienhold
> On 18/01/2023 18:03 CET Dirschel, Steve > wrote: > > The plan changes: > > Sort (cost=9382.94..9382.97 rows=12 width=169) > Sort Key: lmq1.priority DESC, lmq1.request_time > -> Bitmap Heap Scan on lm_queue lmq1 (cost=4572.59..9382.73 rows=12 width=169) > Recheck Cond: ((client_name)::text = 'WL

Re: Interpreting postgres execution plan along with AND/OR precedence

2023-01-18 Thread Erik Wienhold
> On 18/01/2023 18:56 CET Tom Lane wrote: > > "Dirschel, Steve" writes: > > Filter: ... (alternatives: SubPlan 1 or hashed SubPlan 2) ... > > SubPlan 1 > >-> Index Scan using ix_lm_cc on lm_queue lmq2 > > (cost=0.40..177.93 rows=1 width=0) > > Ind

Re: Interpreting postgres execution plan along with AND/OR precedence

2023-01-18 Thread Tom Lane
"Dirschel, Steve" writes: > Filter: ... (alternatives: SubPlan 1 or hashed SubPlan 2) ... > SubPlan 1 >-> Index Scan using ix_lm_cc on lm_queue lmq2 (cost=0.40..177.93 > rows=1 width=0) > Index Cond: ((collection_name)::text = > (lmq1.collection_n

Interpreting postgres execution plan along with AND/OR precedence

2023-01-18 Thread Dirschel, Steve
Table definition: Table "load.lm_queue" Column | Type | Collation | Nullable | Default ++---+--+- guid