Re: ERROR: unexpected chunk number 0 (expected 1) for toast value 76753264 in pg_toast_10920100

Hi,

Thanks for the responses.

> "One lesson I learned from the BSD camp when dealing with random freezes and panics : when all else fails to give an answer it is time to start blaming my hardware. Are those tablespaces on any cheap SSD's ?”

The tablespaces are not sat on SSD’s. Something I had also considered.

Tom - I can provide a jar that I have been using to replicate the issue. Whats the best transport method to send it over?

Best wishes,
Harry

> On 7 Jun 2017, at 16:27, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Harry Ambrose <harry(dot)ambrose(at)gmail(dot)com> writes:
>> I have been following the updates to the 9.4 branch hoping a fix will appear, but sadly no luck yet. I have manually replicated the issue on 9.4.4, 9.4.10 and 9.4.12. My replication steps are:
>
> This is a very interesting report, but you didn't actually provide a
> reproducer, just a handwavy outline. If you submit a script that
> makes this happen, we will most definitely look into it. But
> people aren't going to be excited about trying to reverse-engineer
> a test case out of a vague description.
>
>> I also found the following has been reported:
>> https://www.postgresql.org/message-id/20161201165505.4360.28203@wrigleys.postgresql.org
>
> That person never came back with a self-contained test case, either.
>
> https://wiki.postgresql.org/wiki/Guide_to_reporting_problems
>
> regards, tom lane