At 9/6/01 6:34 PM, Jeff Boes <jboes@nexcerpt.com> wrote:
>In article <999558317.8648.1.camel@inspiron.cramers>, "Dave Cramer"
><Dave@micro-automation.net> wrote:
>
>> There is a bug in the glibc library that causes this. I think there is
>> some documentation on the list about it.
>
>Anybody have a pointer to more info about this? How do I determine if
>this affects my system? (I'm having problems similar to this with VACUUM
>ANALYZE on one particular, long-row table.)
That sounds like it's probably it (especially if you can do a normal
vacuum with no trouble). If you're using glibc version 2.2.2 or earlier,
your machine is vulnerable.
The solution is to upgrade to glibc 2.2.3 or later.
--
Robert L Mathews, Tiger Technologies