invalid memory alloc request size

From: Ben Chobot <bench(at)silentmedia(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: invalid memory alloc request size
Date: 2011-12-26 16:08:23
Message-ID: 9826EAE5-296D-4C31-B0F3-0B3C1995AF82@silentmedia.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Yesterday I had a problem on a 64-bit 9.1.1 install:

# select version();
version
----------------------------------------------------------------------------------------------------------------
PostgreSQL 9.1.1 on x86_64-pc-linux-gnu, compiled by gcc-4.6.real (Ubuntu/Linaro 4.6.1-9ubuntu3) 4.6.1, 64-bit
(1 row)

The logs showed this anomaly:

2011-12-25T19:33:18+00:00 pgdb2-vpc postgres[27546]: [74474-1] ERROR: invalid memory alloc request size 18446744073709551613
2011-12-25T19:33:18+00:00 pgdb2-vpc postgres[27546]: [74474-2] STATEMENT: SELECT * FROM "asset_user_accesses" WHERE ("asset_user_accesses"."asset_code" = 'assignments:course_141208' AND "asset_user_accesses"."user_id" = 618503) LIMIT 1;

Googling around, it sounds like this is often due to table corruption, which would be unfortunate, but usually seems to be repeatable. I can re-run that query without issue, and in fact can select * from the entire table without issue. I do see the row was updated a few minutes after this error, so is it wishful thinking that vacuum came around and successfully removed the old, corrupted row version?

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Raymond O'Donnell 2011-12-26 22:25:21 Re: Re: Unable to connect to PostgreSQL server : Could not get socket error status
Previous Message Aman Gupta 2011-12-26 14:32:55 Re: postgresql triggers - defining a global resource (java)