Re: BUG #14438: Wrong row count in the join plan with unique index scan

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: nikolay(dot)nikitin(at)infowatch(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14438: Wrong row count in the join plan with unique index scan
Date: 2016-11-29 23:07:45
Message-ID: 11935.1480460865@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

nikolay(dot)nikitin(at)infowatch(dot)com writes:
> I execute select with "in" condition on the empty table.
> This select works with wrong plan.
> I think the wrong plan is chosen becose the postgres optimizer incorrectly
> calculates row count in the right plan.

I've pushed a patch that should improve matters for such cases.
Thanks for the report!

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message djlopes 2016-11-29 23:28:32 BUG #14440: Error starting postgres
Previous Message Michael Day 2016-11-29 21:39:59 Re: parallel sequential scan returns extraneous rows