Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id AFD73633B20 for ; Thu, 1 Oct 2009 12:48:48 -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 01573-10 for ; Thu, 1 Oct 2009 15:48:41 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by mail.postgresql.org (Postfix) with SMTP id 572F56352A8 for ; Thu, 1 Oct 2009 12:48:40 -0300 (ADT) Received: from source ([209.85.219.218]) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP ID DSNKSsTPUec22ZzaIbXvuPMtYduxzzXuRnfZ@postini.com; Thu, 01 Oct 2009 08:48:40 PDT Received: by mail-ew0-f218.google.com with SMTP id 18so431504ewy.43 for ; Thu, 01 Oct 2009 08:48:33 -0700 (PDT) Received: by 10.211.173.11 with SMTP id a11mr1505014ebp.42.1254412112868; Thu, 01 Oct 2009 08:48:32 -0700 (PDT) Received: from ?192.168.1.117? ([88.195.103.165]) by mx.google.com with ESMTPS id 7sm68902eyg.19.2009.10.01.08.48.30 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 01 Oct 2009 08:48:31 -0700 (PDT) Message-ID: <4AC4CF4D.1000809@enterprisedb.com> Date: Thu, 01 Oct 2009 18:48:29 +0300 From: Heikki Linnakangas Organization: EnterpriseDB User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090706) MIME-Version: 1.0 To: Simon Riggs CC: pgsql-hackers Subject: Re: Hot Standby on git References: <1253958559.4449.833.camel@ebony.2ndQuadrant> <4AC49281.2040302@enterprisedb.com> <1254407967.17864.229.camel@ebony.2ndQuadrant> In-Reply-To: <1254407967.17864.229.camel@ebony.2ndQuadrant> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-6.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4 X-Spam-Level: X-Archive-Number: 200910/59 X-Sequence-Number: 146871 Simon Riggs wrote: > Hmm, yes. ISTM that I'm still calculating latestRunningXid the old way > while assuming it is calculated the new way. The new way is just to grab > nextXid since we have XidGenLock and do TransactionIdRetreat() on it. Ok, good, that's what I thought too. I'll fix that. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com