Moving to -docs...
Does anyone know what the history of the docs saying that GNU tar had
issues with files changing underneath it? According to this report it's
actually BSD tar that has the issue.
On Wed, May 09, 2007 at 10:19:05AM -0700, Jeff Davis wrote:
On Wed, 2007-05-09 at 11:40 -0500,
Looks like a problem specific to FreeBSD. I use Centos/postgres 8.2.3
and I do not see that problem at all.
Dhaval
On 5/8/07, Jeff Davis [EMAIL PROTECTED] wrote:
On Tue, 2007-05-08 at 13:24 -0400, Merlin Moncure wrote:
On 5/8/07, Jeff Davis [EMAIL PROTECTED] wrote:
On Tue, 2007-05-08 at
Actually, looking at the docs, the problem is with some versions of
GNU tar. AFAIK bsdtar is perfectly happy to archive files that have
changed from underneath it.
On May 9, 2007, at 10:45 AM, Dhaval Shah wrote:
Looks like a problem specific to FreeBSD. I use Centos/postgres 8.2.3
and I do
On Wed, 2007-05-09 at 11:40 -0500, Jim Nasby wrote:
Actually, looking at the docs, the problem is with some versions of
GNU tar. AFAIK bsdtar is perfectly happy to archive files that have
changed from underneath it.
$ tar --version
bsdtar 1.2.53 - libarchive 1.3.1
That fails to create a
The docs recommend using tar to perform a base backup for PITR.
Usually, tar reports notices like:
tar: Truncated write; file may have grown while being archived.
Did you call pg_start_backup(text) before you started to archive?
Yours,
Laurenz Albe
---(end of
On May 7, 2007, at 1:58 PM, Jeff Davis wrote:
Second, it seems that it can cause a bad backup to occur if you
pass the
z option to tar. Instead, piping the output of tar through the
compression program seems to avoid that problem (i.e. tar cf - ... |
gzip ...). I am using FreeBSD's tar, other
On Tue, 2007-05-08 at 10:25 -0500, Jim Nasby wrote:
On May 7, 2007, at 1:58 PM, Jeff Davis wrote:
Second, it seems that it can cause a bad backup to occur if you
pass the
z option to tar. Instead, piping the output of tar through the
compression program seems to avoid that problem (i.e.
On Tue, 2007-05-08 at 08:47 +0200, Albe Laurenz wrote:
The docs recommend using tar to perform a base backup for PITR.
Usually, tar reports notices like:
tar: Truncated write; file may have grown while being archived.
Did you call pg_start_backup(text) before you started to archive?
On 5/8/07, Jeff Davis [EMAIL PROTECTED] wrote:
On Tue, 2007-05-08 at 08:47 +0200, Albe Laurenz wrote:
The docs recommend using tar to perform a base backup for PITR.
Usually, tar reports notices like:
tar: Truncated write; file may have grown while being archived.
Did you call
On Tue, 2007-05-08 at 13:24 -0400, Merlin Moncure wrote:
On 5/8/07, Jeff Davis [EMAIL PROTECTED] wrote:
On Tue, 2007-05-08 at 08:47 +0200, Albe Laurenz wrote:
The docs recommend using tar to perform a base backup for PITR.
Usually, tar reports notices like:
tar: Truncated write;
The docs recommend using tar to perform a base backup for PITR.
Usually, tar reports notices like:
tar: Truncated write; file may have grown while being archived.
First of all, is the tar archive still safe if those errors occur?
Second, it seems that it can cause a bad backup to occur if you
11 matches
Mail list logo
