Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 2A01D632266 for ; Mon, 5 Jan 2009 12:38:59 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 10962-04-4 for ; Mon, 5 Jan 2009 12:38:55 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.235]) by mail.postgresql.org (Postfix) with ESMTP id 8989463225E for ; Mon, 5 Jan 2009 12:38:52 -0400 (AST) Received: by rv-out-0506.google.com with SMTP id b25so8695750rvf.43 for ; Mon, 05 Jan 2009 08:38:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=5qowRcSdn0tO0xFVKPArLek9UfxxrUhbvNsGjqN4p/Q=; b=sEd4VPys2ORYq52sPGrBHCn85IVbLmNGvLjLVxEor7rQXFgQmmnjh7n9N8oVSc436r 7HKCgbIch79VpN1h/YaP/HCOWpZyvPUoqWPJpFY3Aauu5+b/gO4SzfG8Qp+2O+At+Nvm 8j9EyErq/t6ci9z/6yhjs/PsAzv8Zmaxqgv2U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=Yfon95ANIKa7ikRI0Y+6+L6ugxGJ3eteQ1uH9MK+OIn7oE+iD1RX8v2AMOjmMRTYxO EcH6VqmEhmqogTtd5MstFAeRZXgzG1nvTl8vK01rnmn6bO3Q/qpzJZ/FhKay0XXt6wYd 39RfnH+xdiJHyynR88rR7VY7X1aGuoHr4/2hs= Received: by 10.114.37.1 with SMTP id k1mr13896983wak.172.1231173531110; Mon, 05 Jan 2009 08:38:51 -0800 (PST) Received: by 10.114.135.4 with HTTP; Mon, 5 Jan 2009 08:38:51 -0800 (PST) Message-ID: Date: Mon, 5 Jan 2009 09:38:51 -0700 From: "Scott Marlowe" To: "Ygor Degani" Subject: Re: error vacuum full Cc: pgsql-admin@postgresql.org In-Reply-To: <4bb7c9f80901050517l3743891ax93ad672a07054b14@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4bb7c9f80901050517l3743891ax93ad672a07054b14@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200901/15 X-Sequence-Number: 31062 On Mon, Jan 5, 2009 at 6:17 AM, Ygor Degani wrote: > I use postgres-8.3.5. My database has 168 GB in size. Whenever i try to do > vacuum full happens the following error: > > WARNING: terminating connection because of crash of another server process > DETAIL: The postmaster has commanded this server process to roll back the > current transaction and exit, because another server process exited > abnormally and possibly corrupted shared memory. > HINT: In a moment you should be able to reconnect to the database and > repeat your command. > vacuumdb: vacuuming of database "acotel_brazil_vas" failed: server closed > the connection unexpectedly > This probably means the server terminated abnormally > before or while processing the request. > > If i have autovacuum enabled, Do i need to do vacuum full? You have two problems. One is you're running vacuum full regularly, which you shouldn't need, and which can cause bloated indexes. Normal autovacuum should handle your database fine unless you're deleting a huge part of a table over and over. As to why it's crashing, that's another story. Anything in the system logs about the oom killer kicking in? Have you got work_mem set to something huge? maintenance work mem really huge? shared_buffers, etc? What have you changed from stock in postgresql.conf?