X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org
Received: from localhost (mx1.hub.org [200.46.208.251])
	by postgresql.org (Postfix) with ESMTP id 9C6839FB0D1
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Sat,  6 May 2006 01:34:04 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024)
	with ESMTP id 17896-07
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Sat,  6 May 2006 01:33:54 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from skunk.mtbrook.bozemanpass.com (unknown [69.145.82.195])
	by postgresql.org (Postfix) with ESMTP id EC3EE9FA886
	for <pgsql-performance@postgresql.org>;
	Sat,  6 May 2006 01:33:52 -0300 (ADT)
Received: from [69.145.82.253] (unknown [69.145.82.253])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by skunk.mtbrook.bozemanpass.com (Postfix) with ESMTP id 35AB655833D
	for <pgsql-performance@postgresql.org>;
	Fri,  5 May 2006 21:33:51 -0700 (PDT)
Message-ID: <445C272F.3060002@boreham.org>
Date: Fri, 05 May 2006 22:33:51 -0600
From: David Boreham <david_list@boreham.org>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: pgsql-performance@postgresql.org
Subject: Re: Memory and/or cache issues?
References: <0C4841B42F87D51195BD00B0D020F5CB044B2608@MORPHEUS>
In-Reply-To: <0C4841B42F87D51195BD00B0D020F5CB044B2608@MORPHEUS>
Content-Type: multipart/alternative;
	boundary="------------020008080201030601020006"
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200605/124
X-Sequence-Number: 18911

This is a multi-part message in MIME format.
--------------020008080201030601020006
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


> 2006-05-04 18:04:58 EDT USER=postgres DB=FIX1 [12427] PORT = [local] 
> ERROR:  invalid memory alloc request size 18446744073709551613

Perhaps I'm off beam here, but any time I've seen an app try to allocate 
a gazillion bytes, it's
due to some code incorrectly calculating the size of something (or more 
commonly, using an
initialized variable as the basis for said calculation).



--------------020008080201030601020006
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<blockquote cite="mid0C4841B42F87D51195BD00B0D020F5CB044B2608@MORPHEUS"
 type="cite">2006-05-04 18:04:58 EDT USER=postgres DB=FIX1 [12427] PORT
= [local] ERROR:&nbsp; invalid memory alloc request size 18446744073709551613<br>
</blockquote>
<font size="2"><font face="Arial">Perhaps I'm off beam here, but any
time I've seen an app try to allocate a gazillion bytes, it's <br>
due to some code incorrectly calculating the size of something (or more
commonly, using an<br>
initialized variable as the basis for said calculation).<br>
<br>
<br>
</font></font>
</body>
</html>

--------------020008080201030601020006--