Re: [COMMITTERS] 'pgsql/src/backend/optimizer/util pathnode.c' - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [COMMITTERS] 'pgsql/src/backend/optimizer/util pathnode.c'
Date
Msg-id 9604.933298455@sss.pgh.pa.us
Whole thread Raw
In response to Re: [COMMITTERS] 'pgsql/src/backend/optimizer/util pathnode.c'  (The Hermit Hacker <scrappy@hub.org>)
List pgsql-hackers
The Hermit Hacker <scrappy@hub.org> writes:
> Further to the Alpha thread, is this something that could safely be put in
> the -stable tree?  

I'm sorry, ignore that comment in the commit log.  6.5 does *not*
have this bug --- I got confused about which postmaster process
I was testing against :-(.  It's just a list-slinging error that
I introduced in my latest round of optimizer hacking.
        regards, tom lane


> On Thu, 29 Jul 1999, Tom Lane wrote:
>> Update of /usr/local/cvsroot/pgsql/src/backend/optimizer/util
>> In directory hub.org:/tmp/cvs-serv38342
>> 
>> Modified Files:
>> pathnode.c 
>> Log Message:
>> Fix coredump seen when doing mergejoin between indexed tables,
>> for example in the regression test database, try
>> select * from tenk1 t1, tenk1 t2 where t1.unique1 = t2.unique2;
>> 6.5 has this same bug ...


pgsql-hackers by date:

Previous
From: The Hermit Hacker
Date:
Subject: Re: [HACKERS] Re: [PORTS] RedHat6.0 & Alpha
Next
From: Ryan Kirkpatrick
Date:
Subject: Re: [PORTS] RedHat6.0 & Alpha