Re: BUG #13575: invalid memory request size while storing call arguments into local variables - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: BUG #13575: invalid memory request size while storing call arguments into local variables
Date
Msg-id CAM3SWZSR_=p-VxL_G7rBMExJMnLuFWqU7ODZmSEeceDhiFM9fQ@mail.gmail.com
Whole thread Raw
In response to BUG #13575: invalid memory request size while storing call arguments into local variables  (greg.davidson+pg@gmail.com)
List pgsql-bugs
On Sat, Aug 15, 2015 at 9:01 PM,  <greg.davidson+pg@gmail.com> wrote:
> ERROR:  XX000: invalid memory alloc request size 18446744073642179576

This allocation size is close to 2 ^ 64 (which is
18446744073709551616). Whenever I've seen this before, it tended to be
down to a corrupt length word for some variable-width field.

Can you try using pg_dump on any tables associated with the
problematic queries/procedures? That might confirm that this is some
kind of garden variety corruption.

--
Peter Geoghegan

pgsql-bugs by date:

Previous
From: greg.davidson+pg@gmail.com
Date:
Subject: BUG #13575: invalid memory request size while storing call arguments into local variables
Next
From: nao-anzai@xc.jp.nec.com
Date:
Subject: BUG #13576: a weird behavior of pg_restore command