Re: [GENERAL] PostgreSQL Point In Time Recovery

2013-10-25 Thread Gregory Haase
Before going through something like delayed replication, you really want to consider using zfs or lvm and taking regular snapshots on your hot or warm standby. In the event of the accidental table drop, you can just roll back to the snapshot prior and then do PITR from there. Greg Haase On Fri,

Re: [GENERAL] PostgreSQL Point In Time Recovery

2013-10-25 Thread Jayadevan
Alan Hodgson wrote > Well, yeah. The point was that you possibly could run it for a while to > "catch > up" without taking a new base backup if you desired. You should also keep > copies of it for PITR. Something like this - delayed replication

Re: [GENERAL] PostgreSQL Point In Time Recovery

2013-10-25 Thread Alan Hodgson
On Thursday, October 24, 2013 11:13:34 PM Jayadevan wrote: > Alan Hodgson wrote > > > That's basically what warm standby's do, isn't it? As long as they keep > > recovery open it should work. > > A warn standby will be almost in sync with the primary, right? So recovery > to point-in-time (like 1

Re: [GENERAL] PostgreSQL Point In Time Recovery

2013-10-24 Thread Jayadevan
Alan Hodgson wrote > That's basically what warm standby's do, isn't it? As long as they keep > recovery open it should work. A warn standby will be almost in sync with the primary, right? So recovery to point-in-time (like 10 AM this morning) won't be possible. We need a base, but it shouldn't be

Re: [GENERAL] PostgreSQL Point In Time Recovery

2013-10-24 Thread Jayadevan
Jeff Janes wrote > I restore from my base backup plus WAL quite often. It is how I get a > fresh dev or test instance when I want one. (It is also how I have > confidence that everything is working well and that I know what I'm doing > should the time come to do a real restore). When that starts

Re: [GENERAL] PostgreSQL Point In Time Recovery

2013-10-24 Thread Alan Hodgson
On Thursday, October 24, 2013 11:31:38 AM John R Pierce wrote: > On 10/24/2013 9:47 AM, Jeff Janes wrote: > > I restore from my base backup plus WAL quite often. It is how I get a > > fresh dev or test instance when I want one. (It is also how I have > > confidence that everything is working well

Re: [GENERAL] PostgreSQL Point In Time Recovery

2013-10-24 Thread John R Pierce
On 10/24/2013 9:47 AM, Jeff Janes wrote: I restore from my base backup plus WAL quite often. It is how I get a fresh dev or test instance when I want one. (It is also how I have confidence that everything is working well and that I know what I'm doing should the time come to do a real resto

Re: [GENERAL] PostgreSQL Point In Time Recovery

2013-10-24 Thread Jeff Janes
On Wed, Oct 23, 2013 at 9:10 PM, Jayadevan M wrote: > Hi, > I went through > http://www.postgresql.org/docs/9.3/static/continuous-archiving.html > and set up the archiving process. With this approach, if my database > crashes after a couple of weeks after the base backup is taken, recovering > wou

Re: [GENERAL] PostgreSQL Point In Time Recovery

2013-10-23 Thread John R Pierce
On 10/23/2013 9:10 PM, Jayadevan M wrote: I went through http://www.postgresql.org/docs/9.3/static/continuous-archiving.html and set up the archiving process. With this approach, if my database crashes after a couple of weeks after the base backup is taken, recovering would mean replaying the W

[GENERAL] PostgreSQL Point In Time Recovery

2013-10-23 Thread Jayadevan M
Hi, I went through http://www.postgresql.org/docs/9.3/static/continuous-archiving.html and set up the archiving process. With this approach, if my database crashes after a couple of weeks after the base backup is taken, recovering would mean replaying the WAL logs for about 2 weeks, right? To avoid