| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Named restore points |
| Date: | 2011-01-14 23:44:48 |
| Message-ID: | AANLkTikkt2rQ_6v3zyZT3EXG3aukEzbhTtn6N4hdyFce@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jan 14, 2011 at 3:41 PM, Jaime Casanova <jaime(at)2ndquadrant(dot)com> wrote:
> Here is a patch that implements "named restore points".
>
> It allows DBAs to specify an exact point to which they can recover
> but that point will have a name, so they have a better control of when
> they want to stop recovery (ie: DBA's won't depend of remember
> specific times, dates and such).
>
> This adds a new function: pg_create_restore_point(text) (i'm not
> wedded with the name so if someone wants to suggest something better,
> that's fine with me), a new xlog record and a new recovery_target
> parameter in recovery.conf
Neat.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-01-14 23:45:57 | Re: [PATCH] Return command tag 'REPLACE X' for CREATE OR REPLACE statements. |
| Previous Message | Robert Haas | 2011-01-14 23:41:55 | Re: LOCK for non-tables |