Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 60AEE633881 for ; Mon, 5 Oct 2009 11:19:19 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 71410-01 for ; Mon, 5 Oct 2009 14:19:11 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 5BEC86323EB for ; Mon, 5 Oct 2009 11:19:11 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id n95EJ5VF006951; Mon, 5 Oct 2009 10:19:05 -0400 (EDT) To: Simon Riggs cc: Heikki Linnakangas , pgsql-hackers Subject: Re: Hot Standby on git In-reply-to: <1254743455.4691.153.camel@ebony.2ndQuadrant> References: <1253958559.4449.833.camel@ebony.2ndQuadrant> <4ABF4522.6060601@enterprisedb.com> <1254743455.4691.153.camel@ebony.2ndQuadrant> Comments: In-reply-to Simon Riggs message dated "Mon, 05 Oct 2009 12:50:55 +0100" Date: Mon, 05 Oct 2009 10:19:05 -0400 Message-ID: <6950.1254752345@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 200910/325 X-Sequence-Number: 147137 Simon Riggs writes: > I don't see how that helps at all. The objective of lock counters was to > know if we can skip acquiring an LWlock on all lock partitions. This > change keeps the lock counters yet acquires the locks we were trying to > avoid. This change needs some justification since it is not a bug fix. [ scratches head ... ] Why is hot standby messing with this sort of thing at all? It sounds like a performance optimization that should be considered separately, and *later*. regards, tom lane