Re: bug in join? - Mailing list pgsql-hackers

From Laurette Cisneros
Subject Re: bug in join?
Date
Msg-id Pine.LNX.4.33.0201021431080.17257-100000@visor.corp.nextbus.com
Whole thread Raw
In response to Re: bug in join?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: bug in join?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Will keep trying.  I also noticed that several triggers were dropped when I
dropped the table. I need to add these back and see if they make a
difference.

More as I have it...

L.
On Wed, 2 Jan 2002, Tom Lane wrote:

> Laurette Cisneros <laurette@nextbus.com> writes:
> > I will keep trying to recreate it for you.
>
> You could just try
>
>     analyze b;
>     analyze d;
>     explain select * from b,d where b.address = d.address;
>
> and repeat until you see the error from EXPLAIN.  Since ANALYZE takes
> a random sampling these days, successive loops will in fact produce
> slightly different results, and you may be able to recreate the
> erroneous state eventually.
>
> The math in eqjoinsel() is not entirely trivial, but I thought I had
> convinced myself it was okay.  I need to see a failing example to
> figure out what's wrong with it.
>
>             regards, tom lane
>

-- 
Laurette Cisneros
(510) 420-3137
NextBus Information Systems, Inc.
www.nextbus.com
Passenger Information Everywhere



pgsql-hackers by date:

Previous
From: Laurette Cisneros
Date:
Subject: Re: bug in join?
Next
From: Tom Lane
Date:
Subject: Re: bug in join?