Hello!
> > To remind of the problem - I have a problem running VACUUM ANALYZE on a
> > glibc2 linux (Debian 2.0). On solaris it is Ok (and I got a report it is Ok
> > on HP-UX).
I have upgradede Debian 2.0 to 2.1 and the problem mysteriously gone
away!
I am using the word "mysteriously" because:
-- I have not upgraded kernel (yet) - I am still running 2.0.34
-- I have not upgraded glibc2 - both 2.0 and 2.1 are based upon libc-2.0.7
-- I have not upgraded nor recompiled postgres.
Yes, this fix my problem, but what next? It seems suspicious to me, so I
can expect other glibc2-related problems. BTW, I already reported yet another problem with glibc2 - bug with
complex join (actually, not so complex - 4 tables). I overcame the error by
rewriting the query into correlated subquery with EXISTS. I'll test if
Debian upgrade "mysteriously" fix the problem too.
Oleg.
---- Oleg Broytmann http://members.xoom.com/phd2/ phd2@earthling.net Programmers don't die, they
justGOSUB without RETURN.
