Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 17416658E60 for ; Wed, 13 Jan 2010 19:05:01 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 92090-03-5 for ; Wed, 13 Jan 2010 23:04:44 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-pz0-f201.google.com (mail-pz0-f201.google.com [209.85.222.201]) by mail.postgresql.org (Postfix) with ESMTP id 0160965A330 for ; Wed, 13 Jan 2010 18:13:06 -0400 (AST) Received: by pzk39 with SMTP id 39so4565486pzk.15 for ; Wed, 13 Jan 2010 14:13:05 -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=/XViYtSxAPmoxxhEZjb9QFOA3H8tbgMuDuqNYqk9OPE=; b=j9Jc0Tfy5gV9GNX61W5R1JPJqlBp3haVmgXb53EO522h2+xgfmVo097r5a5ImLnt04 AWXnQXpjeRsoE7rAltYt+F2E73BIZ/VfvArgzVCKAaoUB+IHBA4QAVqQ3jhZWtkEFVdm Woekb+LiyNQeN8IlqeNjOT2JqSMFJncdvCRio= 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=qU9w0RLjdjaNgaDz4LBXORRs4rdJUAp2Jugzxyroujg2RgiC0epkVn1jL1YWf9UMjR Ihvwp+RjXfWhdX4MQvxoa7PR1F7Pql8QhcTdhO9i2SuKbcpAhCwwpYjGjumNpBkQJp0I OQDGA5iXtS2PDHr3+h4BbCIpi5nCYdfbOYp0s= MIME-Version: 1.0 Received: by 10.115.101.5 with SMTP id d5mr332040wam.98.1263420785309; Wed, 13 Jan 2010 14:13:05 -0800 (PST) In-Reply-To: <4B4DBDBD.10304@enterprisedb.com> References: <4B4DB022.4070209@enterprisedb.com> <3f0b79eb1001130357n6abc8466q6556daf2ab3c3fe2@mail.gmail.com> <4B4DBDBD.10304@enterprisedb.com> Date: Thu, 14 Jan 2010 07:13:05 +0900 Message-ID: <3f0b79eb1001131413v4ccc8ac1jf25a1f75cf71d5ce@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=-1.834 tagged_above=-10 required=5 tests=AWL=0.765, BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201001/1406 X-Sequence-Number: 154627 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? 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? Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center