Skip site navigation (1) Skip section navigation (2)

BUG #4548: Documentation Contradiction for 8.3

From: "Barry Reddy" <barryreddy(at)gmail(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #4548: Documentation Contradiction for 8.3
Date: 2008-11-24 21:37:02
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      4548
Logged by:          Barry Reddy
Email address:      barryreddy(at)gmail(dot)com
PostgreSQL version: 8.3.3
Operating system:   Linux 2.6.24-19-server i686 RHEL5
Description:        Documentation Contradiction for 8.3

I’ve been going over the PostgreSQL documentation for pg_archiving,
And have been struck by an apparent contradiction, which I’m hoping
To clarify…not sure if you have any thoughts, or can refer this to any
Contacts for a clarification, if so, feel free to forward.

1.	The database server must be shut down in order to get a usable backup.
Half-way measures such as disallowing all connections will not work (in part
because tar and similar tools do not take an atomic snapshot of the state of
the file system, but also because of internal buffering within the server).
Information about stopping the server can be found in Section 17.5. Needless
to say that you also need to shut down the server before restoring the

3.	Perform the backup, using any convenient file-system-backup tool such as
tar or cpio. It is neither necessary nor desirable to stop normal operation
of the database while you do this.

Can anyone clarify if this apparent contradiction is an oversight ?  Old
documentation with new archiving documentation patched on, with no attention
paid to the seeming contradiction on guidelines for filesystem backups of a
running PG database ?


pgsql-bugs by date

Next:From: Bill MoranDate: 2008-11-24 21:41:11
Subject: Re: BUG #4548: Documentation Contradiction for 8.3
Previous:From: John R PierceDate: 2008-11-24 17:20:13
Subject: Re: could not read block 77 of relation 1663/16385/388818775

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group