Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 9AFFE2E0318 for ; Mon, 17 Mar 2008 17:11:17 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 11504-10 for ; Mon, 17 Mar 2008 17:11:04 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 7AD292E014F for ; Mon, 17 Mar 2008 17:11:06 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m2HKB44Q025850; Mon, 17 Mar 2008 16:11:04 -0400 (EDT) To: Jessica Richard cc: pgsql-admin@postgresql.org Subject: Re: invalid memory alloc request In-reply-to: <366983.2304.qm@web56404.mail.re3.yahoo.com> References: <366983.2304.qm@web56404.mail.re3.yahoo.com> Comments: In-reply-to Jessica Richard message dated "Mon, 17 Mar 2008 08:07:37 -0700" Date: Mon, 17 Mar 2008 16:11:04 -0400 Message-ID: <25849.1205784664@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/129 X-Sequence-Number: 28612 Jessica Richard writes: > Can't execute statement: ERROR: > invalid memory alloc request size 18446744072762367400 > It is running on Postgres 8.2.4, and the database size is less than 2G. > T he requested memory size is ridiculous high, does any one know what is causing this? Data corruption, likely ... I do recall that we fixed a couple of bugs recently that could result in silly results in memory-space-needed calculations, but AFAIR they were in maintenance commands like VACUUM FULL, and couldn't be triggered by a plain INSERT. Still, it wouldn't hurt to try an update to 8.2.6 (or 8.2.7, fresh off the presses). regards, tom lane