From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Carlo Stonebanks <stonec(dot)register(at)sympatico(dot)ca>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: New server to improve performance on our large and busy DB - advice? |
Date: | 2010-01-21 16:41:19 |
Message-ID: | dcc563d11001210841v45ee9330oca0489ec79be0266@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thu, Jan 21, 2010 at 8:51 AM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> Scott Marlowe escribió:
>> On Thu, Jan 14, 2010 at 12:17 PM, Carlo Stonebanks
>> <stonec(dot)register(at)sympatico(dot)ca> wrote:
>
>> > 4) Is this the right PG version for our needs?
>>
>> 8.3 is very stable. Update to the latest. 8.4 seems good, but I've
>> had, and still am having, problems with it crashing in production.
>> Not often, maybe once every couple of months, but just enough that I'm
>> not ready to try and use it there yet. And I can't force the same
>> failure in testing, at least not yet.
>
> uh. Is there a report of the crash somewhere with details, say stack
> traces and such?
No, the only server that does this is in production as our stats db
and when it happens it usually gets restarted immediately. It does
this about once every two months. Do the PGDG releases have debugging
symbols and what not? I'll see about having a stack trace ready to
run for the next time it does this.
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2010-01-21 16:44:40 | Re: New server to improve performance on our large and busy DB - advice? |
Previous Message | Pierre Frédéric Caillaud | 2010-01-21 16:36:47 | Re: ext4 finally doing the right thing |