Well we don't have snapshots yet. This is what I will be implementing.

On 18 October 2014 12:27, Vick Khera <vivek at khera.org> wrote:

> Yes, this is true, but you say that taking a pg_dump instantly makes
> your backup stale. I don't get what you want to achieve that you don't
> already have: live "backup" using slony, and snapshots for disaster
> recovery.
>
> On Fri, Oct 17, 2014 at 4:37 PM, Dave Cramer <davecramer at gmail.com> wrote:
> > Well replica's don't protect you from everything. Such as drop table, or
> > delete from ... or truncate ...
> >
> > No one backup solution protects you from everything.
> >
> > Dave
> >
> > Dave Cramer
> >
> > On 17 October 2014 16:12, Vick Khera <vivek at khera.org> wrote:
> >>
> >> On Fri, Oct 17, 2014 at 9:00 AM, Dave Cramer <davecramer at gmail.com>
> wrote:
> >> > So what's the best way to deal with very large databases. pg_dump just
> >> > doesn't cut it. By the time we are finished dumping the data is stale
> >> > anyway
> >> > !
> >> >
> >> > I'm thinking of using PITR instead. Rolling over once a week
> >>
> >> What problem are you solving then, that is not already solved by
> >> having a replica using slony?
> >
> >
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20141018/d40fb113/attachment.htm