On Fri, Jun 17, 2011 at 1:54 PM, David Fetter wrote:
> On Fri, Jun 17, 2011 at 09:57:13AM -0500, Jaime Casanova wrote:
>>
>> Are you still working on this? should we expect a new patch?
>
> Yes, sorry about that. I let work get on top of me. Will try for a
> new patch this evening.
>
ok... i wi
On Fri, Jun 17, 2011 at 09:57:13AM -0500, Jaime Casanova wrote:
> On Fri, Jun 10, 2011 at 11:30 AM, David Fetter wrote:
> >
> > This also allows subsequent PITR to other times on the original
> > timeline.
> >
> > Josh B pointed out that since this option to true conflicts with
> > another option,
On Fri, Jun 10, 2011 at 11:30 AM, David Fetter wrote:
>
> This also allows subsequent PITR to other times on the original
> timeline.
>
> Josh B pointed out that since this option to true conflicts with
> another option, having both should prevent recovery from even
> starting, and I'll work up a
On 6/10/11 12:34 PM, Robert Haas wrote:
> On Fri, Jun 10, 2011 at 2:53 PM, Josh Berkus 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 the
On 10.06.2011 22:34, Robert Haas wrote:
On Fri, Jun 10, 2011 at 2:53 PM, Josh Berkus 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 W
On Fri, Jun 10, 2011 at 2:53 PM, Josh Berkus 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
David,
> 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. D
David,
> 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. D
On Fri, Jun 10, 2011 at 01:20:25AM -0400, Robert Haas wrote:
> On Thu, Jun 9, 2011 at 8:59 PM, Tom Lane wrote:
> > David Fetter 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 yo
On Thu, Jun 9, 2011 at 8:59 PM, Tom Lane wrote:
> David Fetter 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?
David Fetter 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-re
On 6/9/11 4:51 PM, David Fetter wrote:
> Folks,
>
> 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.
>
> PFA a patch implementing and d
Folks,
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.
PFA a patch implementing and documenting same :)
Cheers,
David.
--
David Fetter
13 matches
Mail list logo
