I used your suggestion and renamed "online backup" to "incremental
backup", and added a mention that many database vendors call it "online
backup".
Patch attached.
---
Rick Gigger wrote:
> How about:
>
> use "Online backup" or "Hot backup" to refer to either method of back
> since they are both done while the system is online or hot.
>
> If you want to get specific refer to doing a "sql dump" etc for using
> pg_dump
> Then use "Incremental backup" to refer to the whole process of the
> WAL archival etc
> Refer to the actual log files themselves as transaction logs.
>
> That all seems to be pretty intuitive and non-ambiguous non-confusing
> to me.
>
> On Dec 26, 2005, at 11:44 AM, Tom Lane wrote:
>
> > Bruce Momjian writes:
> >> I suggest the following patch to rename our capability "Continuous
> >> Backup".
> >
> > This doesn't seem like an improvement. "Online backup" is the
> > standard
> > terminology AFAIK.
> >
> > regards, tom lane
> >
> > ---(end of
> > broadcast)---
> > TIP 4: Have you searched our list archives?
> >
> >http://archives.postgresql.org
> >
>
>
> ---(end of broadcast)---
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>choose an index scan if your joining column's datatypes do not
>match
>
--
Bruce Momjian| http://candle.pha.pa.us
[email protected] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown Square, Pennsylvania 19073
Index: doc/src/sgml/backup.sgml
===
RCS file: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v
retrieving revision 2.76
diff -c -c -r2.76 backup.sgml
*** doc/src/sgml/backup.sgml7 Nov 2005 17:36:44 - 2.76
--- doc/src/sgml/backup.sgml14 Feb 2006 04:00:50 -
***
*** 19,25
SQL dump
File system level backup
!On-line backup
Each has its own strengths and weaknesses.
--- 19,25
SQL dump
File system level backup
!Incremental backup
Each has its own strengths and weaknesses.
***
*** 372,382
!
! On-line backup and point-in-time recovery (PITR)
!on-line backup
--- 372,382
!
! Incremental backup and point-in-time recovery (PITR)
!incremental backup
***
*** 452,458
!To recover successfully using an on-line backup, you need a continuous
sequence of archived WAL files that extends back at least as far as the
start time of your backup. So to get started, you should set up and test
your procedure for archiving WAL files before you take your
--- 452,459
!To recover successfully using an incremental backup (also called "online
!backup" by many database vendors), you need a continuous
sequence of archived WAL files that extends back at least as far as the
start time of your backup. So to get started, you should set up and test
your procedure for archiving WAL files before you take your
***
*** 782,793
pg_start_backup or pg_stop_backup, and
you will therefore be left to your own devices to keep track of which
backup dump is which and how far back the associated WAL files go.
! It is generally better to follow the on-line backup procedure above.
!Recovering with an On-line Backup
Okay, the worst has happened and you need to recover from your backup.
--- 783,794
pg_start_backup or pg_stop_backup, and
you will therefore be left to your own devices to keep track of which
backup dump is which and how far back the associated WAL files go.
! It is generally better to follow the incremental backup procedure above.
!Recovering with an Incremental Backup
Okay, the worst has happened and you need to recover from your backup.
***
*** 1119,1129
!
Caveats
! At this writing, there are several limitations of the on-line backup
technique. These will probably be fixed in future releases:
--- 1120,1130
!
Caveats
! At this writing, there are several limitations of the incremental backup
technique. These will probably be fixed in future releases:
Index: doc/src/sgml/config.sgml
===
RCS file: /cvsroot/pgsql/doc/src/sgml/config.sgml,v
retrieving revision 1.47
diff -c -c -r1.47 config.sgml
*** doc/src/sgml/config.sgml5 Feb 2006 18:19:14 -
