X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 06B9F9DC987 for ; Tue, 14 Feb 2006 13:50:53 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 75126-06 for ; Tue, 14 Feb 2006 13:50:52 -0400 (AST) 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 D43099DC93D for ; Tue, 14 Feb 2006 13:50:50 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k1EHolRk019987; Tue, 14 Feb 2006 12:50:47 -0500 (EST) To: "Tomeh, Husam" cc: pgsql-performance@postgresql.org Subject: Re: 0ut of Memory Error during Vacuum Analyze In-reply-to: References: Comments: In-reply-to "Tomeh, Husam" message dated "Tue, 14 Feb 2006 08:45:08 -0800" Date: Tue, 14 Feb 2006 12:50:47 -0500 Message-ID: <19986.1139939447@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.109 required=5 tests=[AWL=0.109] X-Spam-Score: 0.109 X-Spam-Level: X-Archive-Number: 200602/172 X-Sequence-Number: 17158 "Tomeh, Husam" writes: > =# vacuum analyze code; > ERROR: out of memory > DETAIL: Failed on request of size 1073741820. That looks a whole lot like a corrupt-data issue. The apparent dependency on maintenance_work_mem is probably illusory --- I suspect some of your trials are selecting the corrupted row to use in the ANALYZE stats, and others are randomly selecting other rows. If you are able to pg_dump the table in question then this theory is wrong, but I'd suggest trying that first. regards, tom lane