On Wed, Sep 8, 2010 at 6:55 PM, Sam Nelson <samn@xxxxxxxxxxxxxxxxxxx> wrote: > Even if the corruption wasn't a result of that, we weren't too excited about > the process being there to begin with. We thought there had to be a better > solution than just killing the processes. So we had a discussion about the > intent of that script and my boss dealt with something that solved the same > problem without killing queries, then had them stop that daemon and we have > been working with that database to make sure it doesn't go screwy again. No > new corruption has shown up since stopping that daemon. > That memory allocation issue looked drastically different from the toast > value errors, though, so it seemed like a separate problem. But now it's > looking like more corruption. > --- > We're requesting that they do a few things (this is their production > database, so we usually don't alter any data unless they ask us to), > including deleting those rows. My memory is insufficient, so there's a good > chance that I'll forget to post back to the mailing list with the results, > but I'll try to remember to do so. > Thank you for the help - I'm sure I'll be back soon with many more > questions. Any information on repeatable data corruption, whether it is ec2 improperly flushing data on instance resets, postgres misbehaving under atypical conditions, or bad interactions between ec2 and postgres is highly valuable. The only cases of 'understandable' data corruption are hardware failures, sync issues (either fsync off, or fsync not honored by hardware), torn pages on non journaling file systems, etc. 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! merlin -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
