Excellent. Once you're ready, fire it over and I'll test it on our config.<br /><br /> Doug<br /> On Thu, 2007-03-08
at18:34 +0000, Simon Riggs wrote: <blockquote type="CITE"><pre>
<font color="#000000">On Thu, 2007-03-08 at 13:29 -0500, Doug Knight wrote:</font>
<font color="#000000">> I would preserve the existing trigger function as little t "-t", and</font>
<font color="#000000">> maybe implement a catchup trigger function as big t "-T"? Set it up so</font>
<font color="#000000">> that if the first attempt to find the WAL file postgres is currently</font>
<font color="#000000">> requesting succeeds, skip over the trigger check. If the first attempt</font>
<font color="#000000">> fails, then do your trigger check. That way, in the OCF script, the</font>
<font color="#000000">> postmaster can be started, the trigger file set, and connection to the</font>
<font color="#000000">> database looped on until it succeeds as an indication for when the</font>
<font color="#000000">> database is up and available. I think that's cleaner than comparing a</font>
<font color="#000000">> filename from a 'ps' command. Once I've completed the OCF script and</font>
<font color="#000000">> done some testing, I'll forward it to you for you to review and see if</font>
<font color="#000000">> you want to include it.</font>
<font color="#000000">I'm happy to do this, unless other objections.</font>
<font color="#000000">I'll be doing another version before feature freeze.</font>
</pre></blockquote>
