| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | cedric(at)2ndquadrant(dot)com |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Recovery target 'immediate' |
| Date: | 2013-05-06 19:33:51 |
| Message-ID: | CA+TgmoZWZp04tzB4iQAsUdfApHZWpq=d7_k3Luid5Bxo+zGvNQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 3, 2013 at 11:13 AM, Cédric Villemain
<cedric(at)2ndquadrant(dot)com> wrote:
>> If we want to avoid adding a new option for this, how about a magic
>> restore point called "consistent" or "immediate":
>>
>> recovery_target_name='immediate'
>>
>> That would stop recovery right after reaching consistency, but there
>> wouldn't be an actual restore point record in the WAL stream.
>
> Back to your first email then.
> +1 (as pointed by Simon, this is something we must document well: stopping at
> 'immediate' is sure to reduce your chance of recovering all the possible data
> ... opposite to recovery_target_name=ultimate, the default ;) )
Sounds good to me.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Kreen | 2013-05-06 19:39:40 | pgcrypto: Fix RSA password-protected keys |
| Previous Message | Robert Haas | 2013-05-06 19:31:36 | Re: corrupt pages detected by enabling checksums |