From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [v9.2] Start new timeline for PITR |
Date: | 2011-06-10 19:38:37 |
Message-ID: | 4DF272BD.3090309@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10.06.2011 22:34, Robert Haas wrote:
> 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?
Creating a dummy recovery.conf with bogus recovery_command would do the
trick.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2011-06-10 19:39:03 | Re: [v9.2] Start new timeline for PITR |
Previous Message | Robert Haas | 2011-06-10 19:34:23 | Re: [v9.2] Start new timeline for PITR |