From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | The Hermit Hacker <scrappy(at)hub(dot)org> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [COMMITTERS] 'pgsql/src/backend/optimizer/util pathnode.c' |
Date: | 1999-07-30 01:34:15 |
Message-ID: | 9604.933298455@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
The Hermit Hacker <scrappy(at)hub(dot)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 ...
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1999-07-30 01:36:40 | Re: [PORTS] RedHat6.0 & Alpha |
Previous Message | The Hermit Hacker | 1999-07-30 01:30:10 | Re: [PORTS] RedHat6.0 & Alpha |