Re: Native DB replication for PG

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Greg Smith <greg(at)2ndquadrant(dot)com>
Cc: jd(at)commandprompt(dot)com, "Gauthier, Dave" <dave(dot)gauthier(at)intel(dot)com>, "rod(at)iol(dot)ie" <rod(at)iol(dot)ie>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Native DB replication for PG
Date: 2010-05-01 07:17:53
Message-ID: z2ldcc563d11005010017kde2ccac8ka038e1d284f9c463@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sat, May 1, 2010 at 12:59 AM, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:
> Scott Marlowe wrote:
>>
>> I tested 8.4 what I thought was fairly hardly last year only
>> to have 8.4.1 die under the same load that 8.3 handled without a
>> problem, and reverted to the known working version putting testing
>> 8.4.1 on hold.
>>
>> So to ME, the choice is a fully functional 8.3 installation that has
>> NO problems with free space map because of configuration choices, or
>> an 8.4 with a known (to me) issue of crashing and dying.
>>
>
> FYI, since December of 2009 (release of 8.4.2) there have been 10 bugs fixed
> with the word "crash" in their description, as well as 7 memory leaks that
> could potentially lead to crash.  Even six months ago I was still hesitant
> to push 8.4 toward production systems; the number of bugs shaken out in the
> last two releases has been substantial.

Exactly, which is why I posted a followup saying I knew it was quite
possible the bug had been fixed. But hope is not a method, so until I
can test to be sure the problem I was hitting was one of the ones
fixed, I'll keep production on 8.3 for now. Because for me, it's
proven itself reliable over ~2 years of very heavy use.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Devrim GÜNDÜZ 2010-05-01 07:27:18 Re: Native DB replication for PG
Previous Message Greg Smith 2010-05-01 07:00:56 Re: Inheritance efficiency