On Thu, Mar 15, 2018 at 8:16 AM, Andy Halsall wrote:
> Thanks for the advice. I re-indexed and reloaded a pg_dumpall into a spare
> server - no errors. Will run pg_catcheck asap.
You can also run amcheck. Get the version targeting earlier Postgres
releases off Github (there are packages for most
Thanks for the advice. I re-indexed and reloaded a pg_dumpall into a spare
server - no errors. Will run pg_catcheck asap.
regards,
Andy
Andy Halsall writes:
> db=# select * from x where col_a = 4675635;
> col_a | col_b | col_c | col_d | col_e |
>last_modifi
Andy Halsall writes:
> db=# select * from x where col_a = 4675635;
> col_a | col_b | col_c | col_d | col_e |
> last_modified
> +-+-+---+---+---
> | | |
Following a number of kernel crashes due to memory corruption, we experienced
"ERROR: invalid memory alloc request size 8589934587" from pg_dump. We assume
because of corruption to a PostgreSQL page due to the same memory problems
causing the crashes. Fortunately this was low impact - we could r
