Re: 7k records into Sort node, 4.5m out? - Mailing list pgsql-performance

From Tomas Vondra
Subject Re: 7k records into Sort node, 4.5m out?
Date
Msg-id dda48e8e4cd63cc6f98f9eca78016c05.squirrel@sq.gransy.com
Whole thread Raw
In response to 7k records into Sort node, 4.5m out?  (Christophe Pettus <xof@thebuild.com>)
Responses Re: 7k records into Sort node, 4.5m out?
List pgsql-performance
On 14 Srpen 2012, 3:15, Christophe Pettus wrote:
> Consider this EXPLAIN ANALYZE output:
>
>     http://explain.depesz.com/s/TCi
>
> Note the Bitmap Heap Scan at the bottom claims to be producing 7094 rows,
> and the Sort above it expects to be processing 7330 rows (the same number
> the Bitmap Heap Scan expected to produce)... but the sort is actually
> producing 4512231 rows, which the sort time would indicate is what really
> happened.  How can this be?

Hi,

notice there's a merge join right above the sort. If there are duplicate
values in the first table (charlie in the explain plans), the matching
rows from the sort will be read repeatedly (re-scanned) and thus counted
multiple times.

Tomas



pgsql-performance by date:

Previous
From: Christophe Pettus
Date:
Subject: 7k records into Sort node, 4.5m out?
Next
From: Christophe Pettus
Date:
Subject: Re: 7k records into Sort node, 4.5m out?