Re: BUG #13575: invalid memory request size while storing call arguments into local variables

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: greg(dot)davidson+pg(at)gmail(dot)com
Cc: pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13575: invalid memory request size while storing call arguments into local variables
Date: 2015-08-17 00:55:12
Message-ID: CAM3SWZSR_=p-VxL_G7rBMExJMnLuFWqU7ODZmSEeceDhiFM9fQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, Aug 15, 2015 at 9:01 PM, <greg(dot)davidson+pg(at)gmail(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message nao-anzai 2015-08-17 08:24:43 BUG #13576: a weird behavior of pg_restore command
Previous Message greg.davidson+pg 2015-08-16 04:01:11 BUG #13575: invalid memory request size while storing call arguments into local variables