Re: Problem with PITR recovery

From: Greg Stark <gsstark(at)mit(dot)edu>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Problem with PITR recovery
Date: 2005-04-18 14:48:59
Message-ID: 87vf6kkun8.fsf@stark.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2005-04-18 15:02:43 Re: Problem with PITR recovery
Previous Message simon 2005-04-18 14:44:02 Re: Re: Problem with PITR recovery