X-Original-To: pgsql-hackers-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 4AE439FB266 for ; Fri, 15 Sep 2006 07:33:07 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 42942-09 for ; Fri, 15 Sep 2006 10:32:58 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.logix-tt.com (mail.logix-tt.com [212.211.145.186]) by postgresql.org (Postfix) with ESMTP id 7610D9FB1EA for ; Fri, 15 Sep 2006 07:32:58 -0300 (ADT) Received: from kingfisher.intern.logix-tt.com (84-72-188-217.dclient.hispeed.ch [84.72.188.217]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.logix-tt.com (Postfix) with ESMTP id E84EA6597B for ; Fri, 15 Sep 2006 12:35:13 +0200 (CEST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by kingfisher.intern.logix-tt.com (Postfix) with ESMTP id B8DCE181C1C09 for ; Fri, 15 Sep 2006 12:33:00 +0200 (CEST) Message-ID: <450A815C.6000709@logix-tt.com> Date: Fri, 15 Sep 2006 12:33:00 +0200 From: Markus Schaber Organization: Logical Tracking and Tracing International AG, Switzerland User-Agent: Thunderbird 1.5.0.5 (X11/20060812) MIME-Version: 1.0 To: pgsql-hackers@postgresql.org Subject: Re: [ADMIN] Vacuum error on database postgres 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> In-Reply-To: <3024.1158266129@sss.pgh.pa.us> X-Enigmail-Version: 0.94.0.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enig52FD956AECF5A54D3762494F" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.135 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200609/1225 X-Sequence-Number: 90754 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig52FD956AECF5A54D3762494F Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Hi, Tom, Tom Lane wrote: > We could add another LockTagType just for ANALYZE, but that seems like > rather a lot of infrastructure to support an extremely narrow corner > case, namely two people doing database-wide ANALYZE at the same time > inside transaction blocks. (If they do it outside a transaction block > then the ANALYZE is divided into multiple xacts and so doesn't try to > hold locks on multiple tables concurrently. autovacuum won't try to do= > that either.)=20 Is there any reason to allow ANALYZE run insinde a transaction at all? Markus --=20 Markus Schaber | Logical Tracking&Tracing International AG Dipl. Inf. | Software Development GIS Fight against software patents in Europe! www.ffii.org www.nosoftwarepatents.org --------------enig52FD956AECF5A54D3762494F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFCoFcyHQIGEs7eeARA71rAKCPLfUbYoVD9YqZvILXpFdvvuyCyACgtD2w p1IXkO9YfI8MhRKcRBmjVn4= =FhJ1 -----END PGP SIGNATURE----- --------------enig52FD956AECF5A54D3762494F--