| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Sam Nelson <samn(at)consistentstate(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Missing Toast Chunk |
| Date: | 2010-08-19 19:20:58 |
| Message-ID: | AANLkTinktrhiCgkzPRMTpSyLLoqsfqXFavOecjSG71xj@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Aug 19, 2010 at 11:26 AM, Sam Nelson <samn(at)consistentstate(dot)com> wrote:
> Good morning, list.
> We've got a bit of a problem on a customer's production box. We got a
> "missing chunk number 0 for toast value N" (N being a number) this week on
SNIP
> So the question is, what could be causing this? It's not so terrible a deal
> that we found that error in their database once, but this happened again
> right after we fixed it. Could it be ruby? The customer's application(s)?
> Some weirdness with Amazon EC2 and/or debian? A bug in postgres, itself?
It's almost certainly not ruby's fault. Have they done anything
strange like kill the instance and restart it without letting the db
shut down? I'd tend to suspect Amazon's fsyncing is amiss and they
did something that triggered it.
--
To understand recursion, one must first understand recursion.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Miguel Vaz | 2010-08-19 19:35:50 | searchable book database |
| Previous Message | Tom Lane | 2010-08-19 19:12:55 | Re: Missing Toast Chunk |