From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Sam Nelson <samn(at)consistentstate(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Memory Errors |
Date: | 2010-09-21 18:13:30 |
Message-ID: | AANLkTi=Y3ZkZLHFHkO43heJGX6E8qr7sgGiC7SfBBrAp@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Sep 21, 2010 at 12:57 PM, Sam Nelson <samn(at)consistentstate(dot)com> wrote:
>> On Thu, Sep 9, 2010 at 8:14 AM, Merlin Moncure <mmoncure(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | William Temperley | 2010-09-21 18:20:04 | Re: Triggers and locking |
Previous Message | Alban Hertroys | 2010-09-21 17:39:48 | Re: Triggers and locking |