Re: Huge overestimation in rows expected results in bad plan - Mailing list pgsql-performance

From Tom Lane
Subject Re: Huge overestimation in rows expected results in bad plan
Date
Msg-id 20388.1289345380@sss.pgh.pa.us
Whole thread Raw
In response to Huge overestimation in rows expected results in bad plan  (bricklen <bricklen@gmail.com>)
Responses Re: Huge overestimation in rows expected results in bad plan  (bricklen <bricklen@gmail.com>)
List pgsql-performance
bricklen <bricklen@gmail.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

pgsql-performance by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: anti-join chosen even when slower than old plan
Next
From: bricklen
Date:
Subject: Re: Huge overestimation in rows expected results in bad plan