On Fri, May 3, 2013 at 11:13 AM, Cédric Villemain <ced...@2ndquadrant.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
