Re: Am I missing something about the output of pg_stop_backup()?
От | Ben |
---|---|
Тема | Re: Am I missing something about the output of pg_stop_backup()? |
Дата | |
Msg-id | Pine.LNX.4.64.0707101547120.27105@localhost.localdomain обсуждение исходный текст |
Ответ на | Re: Am I missing something about the output of pg_stop_backup()? (Greg Smith <gsmith@gregsmith.com>) |
Список | 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@gregsmith.com http://www.gregsmith.com Baltimore, MD > > ---------------------------(end of broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster >
В списке pgsql-general по дате отправления: