GNU tar and PITR

Am Montag, 16. Juli 2007 12:01 schrieb Peter Eisentraut:

http://developer.postgresql.org/pgdocs/postgres/continuous-archiving.html
says:

"""
Also, some versions of GNU tar consider it an error if a file is changed
while tar is copying it. There does not seem to be any very convenient way
to distinguish this error from other types of errors, other than manual
inspection of tar's messages. GNU tar is therefore not the best tool for
making base backups.
"""

However, GNU tar returns 2 for a real error and 1 for the file changed
case. Isn't that sufficient?

Ah ...

"""
version 1.16 - Sergey Poznyakoff, 2006-10-21

* After creating an archive, tar exits with code 1 if some files were
changed while being read. Previous versions exited with code 2 (fatal
error), and only if some files were truncated while being archived.
"""

We should update the documentation.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

Peter Eisentraut wrote:

Am Montag, 16. Juli 2007 12:01 schrieb Peter Eisentraut:

http://developer.postgresql.org/pgdocs/postgres/continuous-archiving.html
says:

"""
Also, some versions of GNU tar consider it an error if a file is changed
while tar is copying it. There does not seem to be any very convenient way
to distinguish this error from other types of errors, other than manual
inspection of tar's messages. GNU tar is therefore not the best tool for
making base backups.
"""

However, GNU tar returns 2 for a real error and 1 for the file changed
case. Isn't that sufficient?

Ah ...

"""
version 1.16 - Sergey Poznyakoff, 2006-10-21

* After creating an archive, tar exits with code 1 if some files were
changed while being read. Previous versions exited with code 2 (fatal
error), and only if some files were truncated while being archived.
"""

We should update the documentation.

Docs updated, patch attached.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +