"David Rowley" writes:
> I thought about this after sending my reply to this last night. I remembered
> when I created my test case I had to add the other tables to get the nest
> loop behaviour. I'm not sure your guess about the multicolumn selectivity
> issue is correct. I re-tested with the fol
Tom Lane Wrote:
> "David Rowley" writes:
> > My report contained a full re-creation script to reproduce the problem
> and
> > tonight I'm having the same problem with CVS Head. To my untrained eye
> it
> > looks like the planner is not properly pushing down the row count.
>
> It looks more like a
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> Sent: 10 February 2009 22:30
> To: David Rowley
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Bug #4284
>
> "David Rowley" writes:
> > My report contained a full re-creation script to reproduce the
"David Rowley" writes:
> My report contained a full re-creation script to reproduce the problem and
> tonight I'm having the same problem with CVS Head. To my untrained eye it
> looks like the planner is not properly pushing down the row count.
It looks more like a multicolumn selectivity issue
I had an email today about an old bug that I reported back in July 2008.
http://archives.postgresql.org/pgsql-bugs/2008-07/msg00026.php
I didn't receive any response at the time and I didn't really follow it up.
My report contained a full re-creation script to reproduce the problem and
