diff options
Diffstat (limited to 'doc/src/sgml')
| -rw-r--r-- | doc/src/sgml/backup.sgml | 10 |
1 files changed, 4 insertions, 6 deletions
diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml index d61fe997e6f..e0ffe559330 100644 --- a/doc/src/sgml/backup.sgml +++ b/doc/src/sgml/backup.sgml @@ -1,5 +1,5 @@ <!-- -$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.54.4.6 2005/06/25 22:47:49 tgl Exp $ +$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.54.4.7 2007/09/29 01:36:39 tgl Exp $ --> <chapter id="backup"> <title>Backup and Restore</title> @@ -1084,11 +1084,9 @@ restore_command = 'copy /mnt/server/archivedir/%f "%p"' # Windows <para> To deal with these problems, <productname>PostgreSQL</> has a notion - of <firstterm>timelines</>. Each time you recover to a point-in-time - earlier than the end of the WAL sequence, a new timeline is created - to identify the series of WAL records generated after that recovery. - (If recovery proceeds all the way to the end of WAL, however, we do not - start a new timeline: we just extend the existing one.) The timeline + of <firstterm>timelines</>. Whenever an archive recovery is completed, + a new timeline is created to identify the series of WAL records + generated after that recovery. The timeline ID number is part of WAL segment file names, and so a new timeline does not overwrite the WAL data generated by previous timelines. It is in fact possible to archive many different timelines. While that might |