Re: [COMMITTERS] 'pgsql/src/backend/optimizer/util pathnode.c'
Further to the Alpha thread, is this something that could safely be put in
the -stable tree?
On Thu, 29 Jul 1999, Tom Lane wrote:
Update of /usr/local/cvsroot/pgsql/src/backend/optimizer/util
In directory hub.org:/tmp/cvs-serv38342Modified 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 ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
Import Notes
Reply to msg id not found: 199907300056.UAA38346@hub.org
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
Show quoted text
On Thu, 29 Jul 1999, Tom Lane wrote:
Update of /usr/local/cvsroot/pgsql/src/backend/optimizer/util
In directory hub.org:/tmp/cvs-serv38342Modified 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 ...
Import Notes
Reply to msg id not found: YourmessageofThu29Jul1999222930-0300Pine.BSF.4.10.9907292227470.65827-100000@thelab.hub.org | Resolved by subject fallback