I'm honestly not sure what I mean by that -- we didn't write that process.
I don't even know the intent of that process; they first told us that it
exists yesterday. I'll ask my boss to ask them for more details about it in
the morning.
We'll talk with 'em and see if they've done anything weird
Sam Nelson writes:
>> 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.
> They haven't done anything li
Sorry, I forgot to mention that we also tried reindexing the toast table.
On Thu, Aug 19, 2010 at 1:20 PM, Scott Marlowe wrote:
> SNIP
>
> 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
On Thu, Aug 19, 2010 at 11:26 AM, Sam Nelson 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 terr
Sam Nelson writes:
> 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
> their production box. We verified that it was only a problem with one row,
> tried to fix it with updates, and ended up deleti
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
their production box. We verified that it was only a problem with one row,
tried to fix it with updates, and ended up deleting the
