From: Pallav Kalva <pkalva@deg.cc>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Morus Walter <morus.walter@tanto.de>
Cc: pgsql-admin@postgresql.org
Subject: Re: Online Backup and WAL archives
Date: Tue, 01 Feb 2005 14:47:40 -0500
Message-ID: <41FFDCDC.4030207@deg.cc> (raw)
In-Reply-To: <15479.1107277351@sss.pgh.pa.us>
References: <16895.32035.914311.612690@tanto-xipolis.de>
<15479.1107277351@sss.pgh.pa.us>
Hi Tom,
If I want to restore to a particular point in time lets say to the
point in time like a day back when one of my table was dropped
accidentally and if i want restore the archive log only to that
particular archive log file . what is the procedure we should follow ?
just keep the archive logs in the directory until the last archive log
file i need or is there a command something like " restore only until
at this archive log file " ? Also what happens to the transaction log
files in pg_xlog directory in this scenario ? do i have to still keep
them or they get created by themself since i am going a day back ?
Is this possible in postgres 8
Thanks,
Pallav
Tom Lane wrote:
>Morus Walter <morus.walter@tanto.de> writes:
>
>
>>The documentation says
>>' To make use of this backup, you will need to keep around all the
>>WAL segment files generated at or after the starting time of the backup. '
>>Now I'm wondering how much of these WAL segment files do I really need
>>in order to recover the databases to a consistent state.
>>
>>
>
>If you are satisfied with recovering to the state shortly after you
>completed the backup, then it would be sufficient to have a set of WAL
>files spanning the time period in which the backup is done. I'm dubious
>that this is necessarily an improvement over a pg_dump backup, though.
>
>
>
>>I expect the online backup to faster on recovery than an SQL dump, since
>>the latter would imply recreation of indexes during recovery.
>>
>>
>
>Is that assumption founded on any hard evidence?
>
> regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
>
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: pkalva@deg.cc, tgl@sss.pgh.pa.us, morus.walter@tanto.de
Subject: Re: Online Backup and WAL archives
In-Reply-To: <41FFDCDC.4030207@deg.cc>
References: <16895.32035.914311.612690@tanto-xipolis.de> <15479.1107277351@sss.pgh.pa.us> <41FFDCDC.4030207@deg.cc>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox