From: Tom Lane <tgl@sss.pgh.pa.us>
To: nikolay.nikitin@infowatch.com
Cc: pgsql-bugs@postgresql.org
Subject: Re: BUG #14438: Wrong row count in the join plan with unique index scan
Date: Tue, 29 Nov 2016 18:07:45 -0500
Message-ID: <11935.1480460865@sss.pgh.pa.us> (raw)
In-Reply-To: <20161128182113.6527.58926@wrigleys.postgresql.org>
References: <20161128182113.6527.58926@wrigleys.postgresql.org>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-bugs>
nikolay.nikitin@infowatch.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
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, nikolay.nikitin@infowatch.com
Subject: Re: BUG #14438: Wrong row count in the join plan with unique index scan
In-Reply-To: <11935.1480460865@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox