Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id C5389632448 for ; Thu, 4 Mar 2010 08:01:33 -0400 (AST) 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 72059-09 for ; Thu, 4 Mar 2010 12:01:22 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-yw0-f181.google.com (mail-yw0-f181.google.com [209.85.211.181]) by mail.postgresql.org (Postfix) with ESMTP id 65760632661 for ; Thu, 4 Mar 2010 08:00:39 -0400 (AST) Received: by ywh11 with SMTP id 11so1160312ywh.28 for ; Thu, 04 Mar 2010 04:00:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=GPR/IFnJAu360EeJXuDdRSejzczsf7hb6c2ESXNbRUc=; b=TKdSXVCAT2SEUTNKJIRoJQA9trlByqW8Ms6dR5T2PfcNjI+9HFu8mtkMEeOmcgix/B C8hFb52Z28eHSxNSXbpaGkOh422bCq5xMBRANpGDLtVGWwzUFTF9VlOiU25ZGRc1eSyE xcIsVIJFDIxoJQN3gY5Jp3tRnSxXTK00zS3RY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=XCpMy5JkLCywSAbBrdmC+B+8k0q8RQL9H+jQrZ9YRpt6sECWnG/FUZ2NBmPxC9pDKf IkHZ/w5FLa37taYtj1R8A1GZMKhW9AH1wa1U21TAJhDsipJ6I/nLoalxAgN4tu6q8B/l knp/F1yMgk1PcB7qKIw1QYPmrNq46wRvupSCI= MIME-Version: 1.0 Received: by 10.101.134.15 with SMTP id l15mr6012646ann.215.1267704033181; Thu, 04 Mar 2010 04:00:33 -0800 (PST) In-Reply-To: <3f0b79eb1001131413v4ccc8ac1jf25a1f75cf71d5ce@mail.gmail.com> References: <4B4DB022.4070209@enterprisedb.com> <3f0b79eb1001130357n6abc8466q6556daf2ab3c3fe2@mail.gmail.com> <4B4DBDBD.10304@enterprisedb.com> <3f0b79eb1001131413v4ccc8ac1jf25a1f75cf71d5ce@mail.gmail.com> Date: Thu, 4 Mar 2010 21:00:33 +0900 Message-ID: <3f0b79eb1003040400w41ced642ua37a0031850c3a5@mail.gmail.com> Subject: Re: Incrementally Updated Backups and restartpoints From: Fujii Masao To: Heikki Linnakangas Cc: PostgreSQL-development Content-Type: text/plain; charset=ISO-8859-1 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: 201003/212 X-Sequence-Number: 158988 Hi, I thought of this issue again since the related question arrived. http://archives.postgresql.org/pgsql-admin/2010-03/msg00036.php On Thu, Jan 14, 2010 at 7:13 AM, Fujii Masao wrote: > On Wed, Jan 13, 2010 at 9:34 PM, Heikki Linnakangas > wrote: >> No, that's not an issue. We only wait for the backup-end record if we >> haven't seen yet since we started recovery from the base backup. >> Assuming the standby had reached that point already before the new >> backup from the standby started, backupStartLoc is zero in the control file. > > OK. That assumption should be documented? This comment is meaningless. Sorry for noise. > And, when we start an archive recovery from the backup from the standby, > we seem to reach a safe starting point before database has actually become > consistent. It's because backupStartLoc is zero. Isn't this an issue? This issue seems to still happen. So should this be fixed for 9.0? Or only writing a note in document is enough for 9.0? I'm leaning towards the latter. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center