Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 014929FB4FE for ; Fri, 31 Aug 2007 22:57:05 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 17530-05 for ; Fri, 31 Aug 2007 22:56:52 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id A81A69F9A81 for ; Fri, 31 Aug 2007 22:56:57 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l811uola005917; Fri, 31 Aug 2007 21:56:50 -0400 (EDT) To: Jeff Frost cc: pgsql-admin@postgresql.org, Simon Riggs Subject: Re: pitr replica dies on startup In-reply-to: References: <3673.1188602373@sss.pgh.pa.us> <5802.1188611110@sss.pgh.pa.us> Comments: In-reply-to Jeff Frost message dated "Fri, 31 Aug 2007 18:49:08 -0700" Date: Fri, 31 Aug 2007 21:56:50 -0400 Message-ID: <5916.1188611810@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/429 X-Sequence-Number: 26760 Jeff Frost writes: > That all seems reasonable enough. Is it in the docs somewhere? I > didn't find anything like this mentioned. If not, could we get it > added as a note? Yeah, it hadn't occurred to anyone to specify this, because we just thought of recovery_command as fetching from a static archive. We clearly need to document the expected semantics better. I'm wondering whether we should discourage people from putting side-effects into the recovery_command, period. You already found out that recovery can ask for the same file more than once, but what if it never asks for a particular file at all? I'm not sure that can happen, just playing devil's advocate. Simon, did you see this thread? What do you think? regards, tom lane