X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 852089FB1BE for ; Wed, 2 Aug 2006 01:48:18 -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 95650-09 for ; Wed, 2 Aug 2006 01:48:09 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by postgresql.org (Postfix) with ESMTP id DE2C89FA2A7 for ; Wed, 2 Aug 2006 01:48:08 -0300 (ADT) Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1]) by tigger.fuhr.org (8.13.7/8.13.7) with ESMTP id k724ltAA000425 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 1 Aug 2006 22:47:58 -0600 (MDT) Received: from winnie.fuhr.org (localhost [127.0.0.1]) by winnie.fuhr.org (8.13.6/8.13.6) with ESMTP id k724lt0n002191; Tue, 1 Aug 2006 22:47:55 -0600 (MDT) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.6/8.13.6/Submit) id k724ltNi002190; Tue, 1 Aug 2006 22:47:55 -0600 (MDT) (envelope-from mfuhr) Date: Tue, 1 Aug 2006 22:47:55 -0600 From: Michael Fuhr To: Tom Lane Cc: adey , "pgsql-admin@postgresql.org" , PostgreSQL Admin , postgresql-l Subject: Re: What's using all my RAM? Message-ID: <20060802044755.GA2152@winnie.fuhr.org> References: <1c66bda80608012109x125180eeh38674c853ea50434@mail.gmail.com> <9130.1154493467@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9130.1154493467@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.353 tagged_above=0 required=5 tests=AWL, SPF_PASS X-Spam-Level: X-Archive-Number: 200608/21 X-Sequence-Number: 22565 On Wed, Aug 02, 2006 at 12:37:47AM -0400, Tom Lane wrote: > adey writes: > > Please could someone tell me how to discover what is using all of my RAM? > > I am trying to run a vacuum against Postgres, but it fails immediately > > with:- > > > "ERROR: out of memory > > DETAIL: Failed on request of size 1073741820." > > I'd bet lunch that this is a corrupt-data problem, not an out-of-memory > problem --- specifically, a bad value in a field length word. See the > archives for many prior examples. 1073741820 = 3ffffffc = 00111111111111111111111111111100 That doesn't explain anything but it's an interesting-looking number. -- Michael Fuhr