| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Daniel Farina <daniel(at)heroku(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Avoiding timeline generation |
| Date: | 2011-03-25 11:54:55 |
| Message-ID: | 2F1A7A52-6E2D-48E2-A57D-F0BFF2972CFE@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mar 24, 2011, at 9:00 PM, Daniel Farina <daniel(at)heroku(dot)com> wrote:
> * Offline WAL application -- I want to be able to bring up a second
> server, perform some amount of point in time recovery, and then stop
> and archive. It would be nice to support read-only queries in this
> case to test the recovered database. The goal of this is to reduce
> recovery time in a disaster scenario without tying up resources on a
> live server.
The new 9.1 feature paise_at_recovery_target seems like it might be what you need here.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2011-03-25 12:12:05 | Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. |
| Previous Message | Fujii Masao | 2011-03-25 11:53:15 | Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. |