From: | Ben <bench(at)silentmedia(dot)com> |
---|---|
To: | Greg Smith <gsmith(at)gregsmith(dot)com> |
Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Am I missing something about the output of pg_stop_backup()? |
Date: | 2007-07-10 22:47:20 |
Message-ID: | Pine.LNX.4.64.0707101547120.27105@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ah, perfect, that's what I was looking for. Thanks!
On Tue, 10 Jul 2007, Greg Smith wrote:
> On Tue, 10 Jul 2007, Ben wrote:
>
>>> "The backup history file is just a small text file. It contains the label
>>> string you gave to pg_start_backup, as well as the starting and ending
>>> times and WAL segments of the backup.
>
>> For instance, in the case when the backup history file from the previous
>> backup is, for some reason, still around, but the backup history file from
>> the current run has yet to be written, then I'd backup more WAL files than
>> I need.
>
> You should give each backup a unique label (normally today's date suffices)
> and confirm that the history file you find has that label in it. That's how
> you prevent this class of problem. If you don't find the label you expect in
> the history, abort the whole thing because your backup didn't happen
> correctly.
>
> --
> * Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-07-10 23:34:08 | Re: Hyper-Trading |
Previous Message | Andrej Ricnik-Bay | 2007-07-10 22:18:24 | Re: Hyper-Trading |