| From: | Oleg Broytmann <phd(at)sun(dot)med(dot)ru> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] VACUUM ANALYZE problem on linux |
| Date: | 1999-03-21 15:42:59 |
| Message-ID: | Pine.SOL2.3.96.SK.990321183501.6838A-100000@sun.med.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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(at)earthling(dot)net
Programmers don't die, they just GOSUB without RETURN.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oleg Broytmann | 1999-03-21 15:50:29 | Re: [HACKERS] VACUUM ANALYZE problem on linux |
| Previous Message | Tom Lane | 1999-03-21 15:40:28 | Re: [HACKERS] CVS target for docs |