| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [v9.2] Start new timeline for PITR |
| Date: | 2011-06-10 19:34:23 |
| Message-ID: | BANLkTimx0nO0+JhhjJWudzYvwoEKO=5fxg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jun 10, 2011 at 2:53 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>> Let's imagine we're taking filesystem snapshots each day by whatever
>> means. We're also archiving xlogs, but only have space for 48 hours'
>> worth. Now we want to recover to 3 days ago, but there are no WALs
>> from that time, so we do a crash recovery from the filesystem
>> snapshot. Doing continuous archiving from this conflicts with the
>> existing WALs, which we solve by creating a new timeline.
>
> How is this different from just changing the recovery_command?
*scratches head*
How is it the same?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2011-06-10 19:38:37 | Re: [v9.2] Start new timeline for PITR |
| Previous Message | Tom Lane | 2011-06-10 19:07:00 | Re: pg_dump vs malloc |