Re: BUG #8245: Urgent:Query on slave failing with invalid memory alloc request size 18446744073709537559

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: kapplegate(at)apsalar(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #8245: Urgent:Query on slave failing with invalid memory alloc request size 18446744073709537559
Date: 2013-06-21 18:42:10
Message-ID: 22255.1371840130@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

kapplegate(at)apsalar(dot)com writes:
> One of our queries has started failing randomly on our slaves with
> invalid memory alloc request size 18446744073709537559

It's hard to say much with that amount of information. Is it always the
exact same number? The root cause is probably either corrupted data
(that is, a trashed length word for some variable-width field) or some
internal logic bug that's causing the server to miscompute how much
memory it needs for some transient allocation. You could confirm or
refute the corrupt-data hypothesis by seeing if you can pg_dump each of
the tables referenced by the failing procedure. If pg_dump fails with
the same error then it's corrupt data, else not. If it's a bug, though,
we'd still be needing more info to track it down. Don't suppose you'd
want to change that specific ERROR to a PANIC so we could get a stack
trace :-(

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message javelasco30 2013-06-21 19:06:33 BUG #8248: se presenta una excepcion cuando intento realizar consultas des la aplicacion en netbeasns
Previous Message Tom Lane 2013-06-21 18:03:25 Re: BUG #8247: Duplicate database names - pg_dump backup fails