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 7B37C9FA509 for ; Fri, 5 May 2006 10:25:39 -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 36802-06 for ; Fri, 5 May 2006 10:25:35 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 392209FA372 for ; Fri, 5 May 2006 10:25:34 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k45DPKOl019908; Fri, 5 May 2006 09:25:20 -0400 (EDT) To: "mcelroy, tim" cc: pgsql-performance@postgresql.org Subject: Re: Memory and/or cache issues? In-reply-to: <0C4841B42F87D51195BD00B0D020F5CB044B2608@MORPHEUS> References: <0C4841B42F87D51195BD00B0D020F5CB044B2608@MORPHEUS> Comments: In-reply-to "mcelroy, tim" message dated "Fri, 05 May 2006 07:49:32 -0400" Date: Fri, 05 May 2006 09:25:20 -0400 Message-ID: <19907.1146835520@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/105 X-Sequence-Number: 18892 "mcelroy, tim" writes: > pg_dump: ERROR: invalid memory alloc request size 18446744073709551613 That looks more like a corrupt-data problem than anything directly to do with having or not having enough memory. regards, tom lane