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

From Greg Stark
Subject Re: Problem with PITR recovery
Date
Msg-id 87vf6kkun8.fsf@stark.xeocode.com
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
Bruce Momjian <pgman@candle.pha.pa.us> writes:

> I see your point. New text is:
>     
>     4 Again connect to the database as a superuser, and issue the command
>     
>         SELECT pg_stop_backup();
>     
>       This should return successfully.
>     
>     5 Once the WAL segment files used during the backup are archived as
>       part of normal database activity, you are done. 
> 
> > sure that they get a good base backup. It actually seems like something
> > that maybe pg_stop_backup() should do in the future.
> 
> Yes, I added that to the TODO list:
>     
>     * Force archiving of partially-full WAL files when pg_stop_backup() is
>       called or the server is stopped

You could even make pg_stop_backup() hang until that's complete. 

-- 
greg



pgsql-hackers by date:

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