<div dir="ltr">Well replica's don't protect you from everything. Such as drop table, or delete from ... or truncate ...<div><br></div><div>No one backup solution protects you from everything.</div><div><br></div><div>Dave</div></div><div class="gmail_extra"><br clear="all"><div>Dave Cramer</div>
<br><div class="gmail_quote">On 17 October 2014 16:12, Vick Khera <span dir="ltr"><<a href="mailto:vivek@khera.org" target="_blank">vivek@khera.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Fri, Oct 17, 2014 at 9:00 AM, Dave Cramer <<a href="mailto:davecramer@gmail.com">davecramer@gmail.com</a>> wrote:<br>
> So what's the best way to deal with very large databases. pg_dump just<br>
> doesn't cut it. By the time we are finished dumping the data is stale anyway<br>
> !<br>
><br>
> I'm thinking of using PITR instead. Rolling over once a week<br>
<br>
</span>What problem are you solving then, that is not already solved by<br>
having a replica using slony?<br>
</blockquote></div><br></div>