ERROR: invalid memory alloc request size <a_big_number_here>

From: Matteo Beccati <php(at)beccati(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: ERROR: invalid memory alloc request size <a_big_number_here>
Date: 2005-10-27 08:59:30
Message-ID: 436096F2.3060108@beccati.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

I'm using 8.1beta4 on a development server for a rather db-intensive
application. This application has a multiprocess daemon which was
working fairly well in past. After some recent changes I started having
deadlock problems. While investigating to remove what was causing them I
removed some FOR UPDATE clauses (added on 8.0 to prevent other deadlock
situations), hoping that the newly added FK share locks would better
handle the concurrent access. In fact the deadlock errors went away, but
I suddenly started getting some of these:

ERROR: invalid memory alloc request size 4291419108
CONTEXT: SQL statement "SELECT 1 FROM ONLY "public"."gw_users" x WHERE
"u_id" = $1 FOR SHARE OF x"
SQL statement "INSERT INTO gw_log_credits (log_id, u_id,
credit) SELECT currval('gw_log_log_id_seq'), u_id, SUM(credit) FROM
gw_objects_credits WHERE o_id = $1 GROUP BY u_id"
PL/pgSQL function "t_gw_outgoing_a_u" line 8 at SQL statement
SQL statement "UPDATE gw_outgoing SET ok = 't', response = $1
WHERE o_id = $2 "
PL/pgSQL function "gw_queue_ok" line 30 at SQL statement
2

where 4291419108 is a big random number. Please let me know if you need
other details.

Best regards
--
Matteo Beccati
http://phpadsnew.com
http://phppgads.com

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Martijn van Oosterhout 2005-10-27 09:07:38 Re: Having trouble startin off with the code..
Previous Message jtv 2005-10-27 05:26:17 Re: Differences in UTF8 between 8.0 and 8.1