From: | Robert L Mathews <lists(at)tigertech(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Crash in vacuum analyze |
Date: | 2001-09-07 05:40:20 |
Message-ID: | 20010907054020.724B6AC97@ns1.tigertech.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
At 9/6/01 6:34 PM, Jeff Boes <jboes(at)nexcerpt(dot)com> wrote:
>In article <999558317(dot)8648(dot)1(dot)camel(at)inspiron(dot)cramers>, "Dave Cramer"
><Dave(at)micro-automation(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-09-07 06:04:03 | Re: Crash in vacuum analyze |
Previous Message | Andy | 2001-09-07 05:14:56 | Re: Great Bridge ceases operations |