Skip site navigation (1) Skip section navigation (2)

Re: Online Backup and WAL archives

From: Pallav Kalva <pkalva(at)deg(dot)cc>
To: Morus Walter <morus(dot)walter(at)tanto(dot)de>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Online Backup and WAL archives
Date: 2005-02-03 14:54:50
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
yes, documentation points to the recovery_target_time(timestamp) option 
in this regard, sorry i missed that. but there is one thing which is 
still not clear to me is if we restore the database to some time back , 
what happens to WAL files in the pg_xlog  directory ? if we still keep 
those files there,  arent they out of sync  ? since we are going back in 
time and we dont need the WAL logs after the  
recovery_target_time(timestamp), or  is it that restore command takes 
care everything automatically ? the manual doesnt clearly say what 
happens to the WAL logs in pg_xlog in case if we use the 
recovery_target_time(timestamp)  option.

In Oracle i know that there is a option of resetting the logs if we have 
to restore some time in back, not sure how it works in new Postgres 8.

Morus Walter wrote:

>Pallav Kalva writes:
>>    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
>Yes. That's what PITR is about. Read the manual for details.
>If you look at the recovery.conf.sample you'll find a variable
>recovery_target_time that must be set. Unless I missed something this
>isn't explicitly stated in the docs but the comment in the sample conf
>is pretty clear.
>Alternatively you can define a transaction id (recovery_target_xid).
>Of course you must have a backup created before the incident and all WALs
>up to the time of the incident.
>---------------------------(end of broadcast)---------------------------
>TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org

In response to


pgsql-admin by date

Next:From: Ing. Jhon CarrilloDate: 2005-02-03 15:27:56
Subject: Problem with plpgsql installation!!!
Previous:From: Sanjay RathodDate: 2005-02-03 12:12:31
Subject: Regarding Postgres 8.0 !

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group