Re: BUG #6335: Weird planner decision with exists (a join b) condition - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #6335: Weird planner decision with exists (a join b) condition
Date
Msg-id 1323871093-sup-479@alvh.no-ip.org
Whole thread Raw
In response to BUG #6335: Weird planner decision with exists (a join b) condition  (maxim.boguk@gmail.com)
Responses Re: BUG #6335: Weird planner decision with exists (a join b) condition
List pgsql-bugs
Excerpts from maxim.boguk's message of mi=C3=A9 dic 14 08:09:38 -0300 2011:

> But once I add second value into IN list plan become completely screwed:

See here:
http://archives.postgresql.org/message-id/1309918036-sup-4092@alvh.no-ip.org
Perhaps it's a similar problem.

Maybe you'd get enthused enough to try to fix the problem?

--=20
=C3=81lvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-bugs by date:

Previous
From: maxim.boguk@gmail.com
Date:
Subject: BUG #6335: Weird planner decision with exists (a join b) condition
Next
From: jlrobins@socialserve.com
Date:
Subject: BUG #6336: SQL stored procedure returing 'int' calling into SRF does not raise error ...