X-Original-To: pgsql-hackers-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 1D30D9FB1EA for ; Fri, 15 Sep 2006 09:45:23 -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 63956-08 for ; Fri, 15 Sep 2006 09:45:15 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from localhost.localdomain (unknown [62.232.55.118]) by postgresql.org (Postfix) with ESMTP id B6E879FB1E4 for ; Fri, 15 Sep 2006 09:45:14 -0300 (ADT) Received: from localhost ([127.0.0.1] helo=localhost.localdomain) by localhost.localdomain with esmtp (Exim 4.62) (envelope-from ) id 1GOD47-0005q2-KK; Fri, 15 Sep 2006 13:45:07 +0100 From: Gregory Stark To: Markus Schaber Cc: pgsql-hackers@postgresql.org Subject: Re: [ADMIN] Vacuum error on database postgres In-Reply-To: <450A815C.6000709@logix-tt.com> (Markus Schaber's message of "Fri, 15 Sep 2006 12:33:00 +0200") Organization: EnterpriseDB References: <44F82150.5000809@pnlassociates.com> <4001.1157121669@sss.pgh.pa.us> <27602.1158238299@sss.pgh.pa.us> <45095CDD.8090704@squeakycode.net> <29469.1158247230@sss.pgh.pa.us> <45097CF4.7040409@commandprompt.com> <3024.1158266129@sss.pgh.pa.us> <450A815C.6000709@logix-tt.com> X-Draft-From: ("nnimap+webmail.enterprisedb.com:Inbox" 2694) Date: Fri, 15 Sep 2006 13:45:07 +0100 Message-ID: <87ac51qox8.fsf@enterprisedb.com> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.064 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200609/1234 X-Sequence-Number: 90763 Markus Schaber writes: > Is there any reason to allow ANALYZE run insinde a transaction at all? I had a script to run explain over a set of queries, then run analyze, then run explain again and check the plans for unexpected changes. It would roll back the analyze if any production queries had changed plans and email the diff to the DBA to review. Actually I never finished the script but that was the plan :) -- Gregory Stark EnterpriseDB http://www.enterprisedb.com