Re: Problem with PITR recovery - Mailing list pgsql-hackers

From Ragnar Hafstað
Subject Re: Problem with PITR recovery
Date
Msg-id 1113733545.31618.32.camel@localhost.localdomain
Whole thread Raw
In response to Re: Problem with PITR recovery  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Problem with PITR recovery  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
On Sat, 2005-04-16 at 23:06 -0400, Bruce Momjian wrote:
[about backup procedure with PITR documentation

> I see in the docs:
> 
>     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. To
>     aid you in doing this, the pg_stop_backup function creates a backup
>     history file that is immediately stored into the WAL archive area. This
>     file is named after the first WAL segment file that you need to have to
>     make use of the backup. For example, if the starting WAL file is
>     0000000100001234000055CD the backup history file will be named something
>     like 0000000100001234000055CD.007C9330.backup. (The second part of this
>     file name stands for an exact position within the WAL file, and can
>     ordinarily be ignored.) Once you have safely archived the backup dump
>     file, you can delete all archived WAL segments with names numerically
>     preceding this one.
> 
> I am not clear on what the "backup dump file" is?  I assume it means
> 0000000100001234000055CD.  It is called "WAL segment file" above.  I
> will rename that phrase to match the above terminology.  Patch attached
> and applied.

Doesn't it refer to the backup file itself (the tar file of the data
directory) ?
You do not want to start deleting WAL segments until that one is safely
archived.

gnari




pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Problem with PITR recovery
Next
From: Bruce Momjian
Date:
Subject: Re: Problem with PITR recovery