From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
Cc: | Euler Taveira de Oliveira <euler(at)timbira(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Named restore points |
Date: | 2011-02-08 13:05:24 |
Message-ID: | AANLkTinHW53TGn=v5Z8Y-yZnRAr3Qn=tx5ex-VGFr_Nb@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Feb 8, 2011 at 2:05 AM, Jaime Casanova <jaime(at)2ndquadrant(dot)com> wrote:
>> Finally, this is a nice feature iif we have a way to know what named restore
>> points are available. DBAs need to take note of this list (that is not good)
>> and the lazy ones will have a hard time to recover the right name (possibly
>> with a xlog dump tool).
>>
>> So how could we store this information? Perhaps a file in
>> $PGDATA/pg_xlog/restore_label that contains the label (and possibly the WAL
>> location). Also it must have a way to transmit the restore_label when we add
>> another restore point. I didn't implement this part (Jaime?) and it seems as
>> important as the new xlog record type that is in the patch. It seems
>> complicate but I don't have ideas. Anyone? The restore point names could be
>> obtained by querying a function (say, pg_restore_point_names or
>> pg_restore_point_list).
>>
>
> i still think this should be a separate tool or a dba written list,
I agree. Keeping track of where you've set named restore points is
not going to be a problem with a simple solution. Which restore
points are available is going to depend on which base backup you
restored and what WAL files you stuffed into pg_xlog.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2011-02-08 13:35:48 | Re: SSI patch version 14 |
Previous Message | Itagaki Takahiro | 2011-02-08 12:25:29 | Re: SQL/MED - file_fdw |