Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 80B2F1337B55 for ; Mon, 8 Nov 2010 11:05:37 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 86535-10 for ; Mon, 8 Nov 2010 15:05:30 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from spinlock.commandprompt.com (host-215.commandprompt.net [207.173.203.215]) by mail.postgresql.org (Postfix) with ESMTP id 4A1FA1337999 for ; Mon, 8 Nov 2010 11:05:30 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by spinlock.commandprompt.com (Postfix) with ESMTP id B657E348023; Mon, 8 Nov 2010 07:05:30 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at commandprompt.com Received: from spinlock.commandprompt.com ([127.0.0.1]) by localhost (spinlock.commandprompt.com.commandprompt.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BQotvWqsNJwc; Mon, 8 Nov 2010 07:05:28 -0800 (PST) Received: from perhan.alvh.no-ip.org (unknown [190.95.28.71]) by spinlock.commandprompt.com (Postfix) with ESMTPSA id 17D17348022; Mon, 8 Nov 2010 07:05:28 -0800 (PST) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id EE8A36E9BC; Mon, 8 Nov 2010 12:05:24 -0300 (CLST) Content-Type: text/plain; charset=UTF-8 Cc: "pgsql-admin@postgresql.org" Subject: Re: Forced quiesce From: Alvaro Herrera To: "Little, Douglas" In-reply-to: <8585BA53443004458E0BAA6134C5A7FB4773E160@EGEXCMB01.oww.root.lcl> References: <8585BA53443004458E0BAA6134C5A7FB4773E160@EGEXCMB01.oww.root.lcl> Date: Mon, 08 Nov 2010 12:05:24 -0300 Message-Id: <1289228619-sup-7871@alvh.no-ip.org> User-Agent: Sup/git Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201011/61 X-Sequence-Number: 36027 Excerpts from Little, Douglas's message of jue oct 28 09:39:19 -0300 2010: > Hi, > We're having to vacuum full the system tables everyday due to the number of temp table drop/creates. Seems to me that you're solving the wrong problem. I think you should be doing very frequent lazy vacuum (not full) of certain system catalogs to prevent bloat. That way you don't need the maintenance to be done with exclusive locks. -- Álvaro Herrera The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support