On Thu, Jan 21, 2010 at 9:44 AM, Alvaro Herrera
> Scott Marlowe escribió:
>> 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.
> You mean the RPMs? Yes, I think Devrim publishes debuginfo packages
> which you need to install separately.
Well crap, this one was built from source, and not with debugging.
Gimme a day or so and I'll have it rebuilt with debug and can run a
useful backtrace on it.
In response to
pgsql-performance by date
|Next:||From: Kevin Grittner||Date: 2010-01-21 18:44:26|
|Subject: Re: Slow update query|
|Previous:||From: Alvaro Herrera||Date: 2010-01-21 16:44:40|
|Subject: Re: New server to improve performance on our large and
busy DB - advice?|