Re: Huge overestimation in rows expected results in bad plan

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: bricklen <bricklen(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Huge overestimation in rows expected results in bad plan
Date: 2010-11-09 23:29:40
Message-ID: 20388.1289345380@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

bricklen <bricklen(at)gmail(dot)com> writes:
> I have a query that is getting a pretty bad plan due to a massively
> incorrect count of expected rows.

The query doesn't seem to match the plan. Where is that OR (c.id =
38441828354::bigint) condition coming from?

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message bricklen 2010-11-09 23:39:24 Re: Huge overestimation in rows expected results in bad plan
Previous Message Kevin Grittner 2010-11-09 23:24:48 Re: anti-join chosen even when slower than old plan