From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | David Fetter <david(at)fetter(dot)org>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [v9.2] Start new timeline for PITR |
Date: | 2011-06-10 05:20:25 |
Message-ID: | BANLkTimPRvSx5b_5ktyDA4Z0v9bHomF8Nw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jun 9, 2011 at 8:59 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> David Fetter <david(at)fetter(dot)org> writes:
>> The nice people at VMware, where I work, have come up with a small
>> patch to allow PITR to create a new timeline. This is useful in cases
>> where you're using filesystem snapshots of $PGDATA which may be old.
>
> Huh? We already start a new timeline when doing a non-crash-recovery
> replay scenario.
>
> The code looks pretty confused too, which makes it difficult to
> reverse-engineer what your point is.
I am guessing that they are taking a filesystem snapshot, and then
using that to fire up PG. So to PG it looks like a crash recovery,
but they want a new timeline anyway.
<waves hands>
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2011-06-10 06:53:33 | Re: Creating new remote branch in git? |
Previous Message | Robert Haas | 2011-06-10 05:18:09 | Re: Creating new remote branch in git? |