Re: Bad Row Count Estimate on View with 8.2 - Mailing list pgsql-performance

From Dave Dutcher
Subject Re: Bad Row Count Estimate on View with 8.2
Date
Msg-id 00d501c7447e$8e227760$8300a8c0@tridecap.com
Whole thread Raw
In response to Re: Bad Row Count Estimate on View with 8.2  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
> From: pgsql-performance-owner@postgresql.org
> [mailto:pgsql-performance-owner@postgresql.org] On Behalf Of Tom Lane
>
> I took another look and think I found the problem: 8.2's new code for
> flattening UNION ALL subqueries into "append relations" is failing to
> initialize all the fields of the appendrel, which confuses
> estimate_num_groups (and perhaps other places).  I think this will fix
> it for you.
>

I gave this a try on our test machine yesterday and it worked.  The planner
was estimating that the group by on the union would return about 300 rows
which is very similar to what 8.1.2 thought.  Actually it returned about
3000 rows, but still it is a good enough estimate to pick a plan which takes
100ms instead of a plan which takes 100 seconds.

Thanks,

Dave



pgsql-performance by date:

Previous
From: Brian Herlihy
Date:
Subject: Re: Querying distinct values from a large table
Next
From: "Luke Lonergan"
Date:
Subject: Re: Querying distinct values from a large table