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:32:52
Message-ID: Pine.LNX.4.33.0201021432330.17882-100000@visor.corp.nextbus.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

OOps, never mind about the triggers. But, I will keep trying to induce the
problem for you.

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

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-01-02 22:36:51 Re: bug in join?
Previous Message Laurette Cisneros 2002-01-02 22:31:45 Re: bug in join?