Skip site navigation (1) Skip section navigation (2)

Re: bug in join?

From: Laurette Cisneros <laurette(at)nextbus(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: bug in join?
Date: 2002-01-02 22:31:45
Message-ID: Pine.LNX.4.33.0201021431080.17257-100000@visor.corp.nextbus.com (view raw or flat)
Thread:
Lists: 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(at)nextbus(dot)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


In response to

Responses

pgsql-hackers by date

Next:From: Laurette CisnerosDate: 2002-01-02 22:32:52
Subject: Re: bug in join?
Previous:From: Tom LaneDate: 2002-01-02 22:29:56
Subject: Re: bug in join?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group