From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kevin Kempter <kevin@kevinkempterllc.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Understanding wal segments
Date: Fri, 02 Nov 2007 01:52:00 -0400
Message-ID: <22472.1193982720@sss.pgh.pa.us> (raw)
In-Reply-To: <200711012338.13229.kevin@kevinkempterllc.com>
References: <200711012155.16409.kevin@kevinkempterllc.com>
<200711012239.07980.kevin@kevinkempterllc.com>
<22325.1193981928@sss.pgh.pa.us>
<200711012338.13229.kevin@kevinkempterllc.com>
Kevin Kempter <kevin@kevinkempterllc.com> writes:
> One more question. I see a fair amount of file changed warnings in the tar
> output. Like this:
> tar: ./data/base/82097725/4242350944: file changed as we read it
Yeah, GNU tar complains about that. It's not a problem, other than the
risk that a boatload of such warnings could obscure real problems ...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, kevin@kevinkempterllc.com
Subject: Re: Understanding wal segments
In-Reply-To: <22472.1193982720@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox