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 EAA259FB2BD for ; Fri, 15 Sep 2006 10:41:21 -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 71525-05 for ; Fri, 15 Sep 2006 10:41:10 -0300 (ADT) 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 9DBF99FB2A8 for ; Fri, 15 Sep 2006 10:41:10 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k8FDf1Ek023984; Fri, 15 Sep 2006 09:41:01 -0400 (EDT) To: Martijn van Oosterhout cc: Jeff Davis , andy , Alvaro Herrera , pgsql-hackers@postgreSQL.org Subject: Re: [ADMIN] Vacuum error on database postgres In-reply-to: <20060915094055.GD1608@svana.org> 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> <1158271045.29889.143.camel@dogma.v10.wvs> <16508.1158272742@sss.pgh.pa.us> <20060915094055.GD1608@svana.org> Comments: In-reply-to Martijn van Oosterhout message dated "Fri, 15 Sep 2006 11:40:55 +0200" Date: Fri, 15 Sep 2006 09:41:01 -0400 Message-ID: <23983.1158327661@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.106 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200609/1235 X-Sequence-Number: 90764 Martijn van Oosterhout writes: > For stuff run from autovacuum, would it be reasonable for the > automatically run version to just abort if it sees someone doing the > same thing? Not especially --- there's no guarantee that the other guy is going to commit at all. And autovac is only holding one lock at a time so it's not a factor in the deadlock issue anyway. regards, tom lane