<div dir="ltr">Well we don't have snapshots yet. This is what I will be implementing. </div><div class="gmail_extra"><br><div class="gmail_quote">On 18 October 2014 12:27, 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">Yes, this is true, but you say that taking a pg_dump instantly makes<br>
your backup stale. I don't get what you want to achieve that you don't<br>
already have: live "backup" using slony, and snapshots for disaster<br>
recovery.<br>
<div><div class="h5"><br>
On Fri, Oct 17, 2014 at 4:37 PM, Dave Cramer <<a href="mailto:davecramer@gmail.com">davecramer@gmail.com</a>> wrote:<br>
> Well replica's don't protect you from everything. Such as drop table, or<br>
> delete from ... or truncate ...<br>
><br>
> No one backup solution protects you from everything.<br>
><br>
> Dave<br>
><br>
> Dave Cramer<br>
><br>
> On 17 October 2014 16:12, Vick Khera <<a href="mailto:vivek@khera.org">vivek@khera.org</a>> wrote:<br>
>><br>
>> 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<br>
>> > anyway<br>
>> > !<br>
>> ><br>
>> > I'm thinking of using PITR instead. Rolling over once a week<br>
>><br>
>> What problem are you solving then, that is not already solved by<br>
>> having a replica using slony?<br>
><br>
><br>
</div></div>_______________________________________________<br>
Slony1-general mailing list<br>
<a href="mailto:Slony1-general@lists.slony.info">Slony1-general@lists.slony.info</a><br>
<a href="http://lists.slony.info/mailman/listinfo/slony1-general" target="_blank">http://lists.slony.info/mailman/listinfo/slony1-general</a><br>
</blockquote></div><br></div>