From: | "MauMau" <maumau307(at)gmail(dot)com> |
---|---|
To: | "Michael Paquier" <michael(dot)paquier(at)gmail(dot)com> |
Cc: | "Heikki Linnakangas" <hlinnakangas(at)vmware(dot)com>, "PostgreSQL mailing lists" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Recovery to backup point |
Date: | 2013-12-07 13:11:33 |
Message-ID: | 5DCDF3A106FD47B7B01D5C156A999B67@maumau |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
From: "Michael Paquier" <michael(dot)paquier(at)gmail(dot)com>
> On Sat, Dec 7, 2013 at 9:06 AM, MauMau <maumau307(at)gmail(dot)com> wrote:
>> Recovery target 'immediate'
>> http://www.postgresql.org/message-id/51703751.2020208@vmware.com
>>
>> May I implement this feature and submit a patch for the next commitfest
>> if I have time?
> Please feel free. I might as well participate in the review.
Thanks. I'm feeling incliend to make the configuration "recovery_target =
'backup_point'" instead of "recovery_target = 'immediate'", because:
* The meaning of this feature for usrs is to recover the database to the
backup point.
* it doesn't seem to need a new parameter. recovery_target_time sounds
appropriate because users want to restore the database at the "time" of
backup.
Regards
MauMau
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2013-12-07 13:16:26 | Re: [PATCH 1/2] SSL: GUC option to prefer server cipher order |
Previous Message | MauMau | 2013-12-07 12:32:16 | Re: [bug fix] pg_ctl fails with config-only directory |