Re: Memory Errors - Mailing list pgsql-general

From Merlin Moncure
Subject Re: Memory Errors
Date
Msg-id AANLkTi=Y3ZkZLHFHkO43heJGX6E8qr7sgGiC7SfBBrAp@mail.gmail.com
Whole thread Raw
In response to Re: Memory Errors  (Sam Nelson <samn@consistentstate.com>)
List pgsql-general
On Tue, Sep 21, 2010 at 12:57 PM, Sam Nelson <samn@consistentstate.com> wrote:
>> On Thu, Sep 9, 2010 at 8:14 AM, Merlin Moncure <mmoncure@gmail.com> wrote:
>> Naturally people are going to be skeptical of ec2 since you are so
>> abstracted from the hardware.  Maybe all your problems stem from a
>> single explainable incident -- but we definitely want to get to the
>> bottom of this...please keep us updated!
>
> As far as the postgres and EC2 instances go, we're not really sure if anyone
> shut down, created, or migrated them in a weird way, but Kevin (my boss)
> said that it wouldn't surprise him.

<please try to avoid top-posting -- it destroys the context of the conversation>

The shutdown/migration point is key, along with fsync settings and a
description of whatever durability guarantees ec2 gives on the storage
you are using.  It's the difference between this being a non-event and
something much more interesting.  The correct way btw to kill backends
is with pg_ctl, but what you did is not related to data corruption.

merlin

pgsql-general by date:

Previous
From: Alban Hertroys
Date:
Subject: Re: Triggers and locking
Next
From: William Temperley
Date:
Subject: Re: Triggers and locking