On 07/08/2009 09:59 AM, Kevin Grittner wrote: <blockquote cite="mid:4A545FFB020000250002855B@gw.wicourts.gov"
type="cite"><prewrap="">Dimitri Fontaine <a class="moz-txt-link-rfc2396E"
href="mailto:dfontaine@hi-media.com"><dfontaine@hi-media.com></a>wrote: </pre><blockquote type="cite"><pre
wrap="">4. sync: slave is no more lagging, it's applying the stream as it gets it, either as part of the master
transactionor not depending on the GUC settings </pre></blockquote><pre wrap="">
I think the interesting bit is when you're at this point and the
connection between the master and slave goes down for a couple days.
How do you handle that?</pre></blockquote><br /> Been following with great interest...<br /><br /> If the updates are
notperformed at a regular enough interval, the slave is not truly a functioning standby. I think it's a different
problemdomain, probably best served by the existing pg_standby support? If the slave can be out of touch with the
masterfor an extended period of time, near real time logs provide no additional benefit over just shipping the archived
WALlogs and running the standby in continuous recovery mode?<br /><br /> Cheers,<br /> mark<br /><br /><pre
class="moz-signature"cols="72">--
Mark Mielke <a class="moz-txt-link-rfc2396E" href="mailto:mark@mielke.cc"><mark@mielke.cc></a>
</pre>
