<div dir="ltr">On Fri, Mar 29, 2013 at 9:59 PM, Simon Riggs <span dir="ltr"><<a href="mailto:simon@2ndquadrant.com"
target="_blank">simon@2ndquadrant.com</a>></span>wrote:<br /><div class="gmail_extra"><div
class="gmail_quote"><blockquoteclass="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex"><divclass="im">On 29 March 2013 01:17, Michael Paquier <<a
href="mailto:michael.paquier@gmail.com">michael.paquier@gmail.com</a>>wrote:<br /> > On Fri, Mar 29, 2013 at
12:48AM, Simon Riggs <<a href="mailto:simon@2ndquadrant.com">simon@2ndquadrant.com</a>> wrote:<br /></div> Early
discussionshad difficulties because of the lack of config<br /> directories, include_if_exists and this patch. We now
havethe<br /> technical capability to meet every request. Circumstances have changed<br /> and outcomes may change
also.<br/></blockquote>Thanks for the clarifications. The following questions are still unanswered:<br /></div><div
class="gmail_quote">1)If recovery.trigger and recovery.conf are specified. To which one the priority is given?<br
/></div><divclass="gmail_quote">2) If both recovery.trigger and recovery.conf are used, let's imagine that the server
removesrecovery.trigger but fails in renaming recovery.conf but a reason or another. Isn't there a risk of
inconsistencyif both triggering methods are used at the same time?<br /></div><div class="gmail_quote">3) Forcing a
harcodeof include_is_exists = 'recovery.conf' at the bottom of postgresql.conf doesn't look like a hack?<br
/></div><divclass="gmail_quote">4) Based on your proposal, are all the parameters included in postgresql.conf.sample or
not?Or only primary_conninfo, trigger_file and standby_mode?</div> -- <br />Michael<br /></div></div>
