X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 27F1E9DC9E2 for ; Tue, 31 Jan 2006 10:36:11 -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 68750-09 for ; Tue, 31 Jan 2006 10:36:15 -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 CE7009DC82A for ; Tue, 31 Jan 2006 10:36:08 -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 k0VEaCFX003550; Tue, 31 Jan 2006 09:36:12 -0500 (EST) To: "Tomeh, Husam" cc: pgsql-admin@postgresql.org Subject: Re: Vacuum - Out of memory In-reply-to: References: Comments: In-reply-to "Tomeh, Husam" message dated "Mon, 30 Jan 2006 20:09:07 -0800" Date: Tue, 31 Jan 2006 09:36:12 -0500 Message-ID: <3549.1138718172@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.102 required=5 tests=[AWL=0.102] X-Spam-Score: 0.102 X-Spam-Level: X-Archive-Number: 200601/327 X-Sequence-Number: 20415 "Tomeh, Husam" writes: > ThanksTom. I've asked the SA to bounce the server thinking it may be a > memory fragmentation issue on the server. After bouncing the server, I > was able to run vacuum successfully. (Before bouncing the server, I > tried a lower value of maintenance_work_mem of 512MB and vacuum worked > fine which made me feel better the status of data not being corrupted). > Do you agree with me at this point that it's not a data corruption > issue? Thanks again. No, I don't, unless you have fields in the database that *should* be 1-billion-and-change bytes long. regards, tom lane