On Tue, Jun 29, 2010 at 10:58 AM, Kevin Grittner
> Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>>> If someone is sloppy about how they copy the WAL files around,
>>> they could temporarily have a truncated file.
>> Can you explain the scenario you're concerned about in more
> If someone uses cp or scp to copy a WAL file from the pg_xlog
> directory to an archive directory, there will be a window of time
> where the file exists and is not complete. If you wait "a while"
> (that being a duration which could be highly variable, depending on
> the specifics of the environment and copy techniques used), the
> missing part of the file will materialize.
Drat. It looks like we even recommend that configuration in the docs.
Well, I don't know what to do about this, then, but I predict
somebody's going to get bitten by it... hard.
The Enterprise Postgres Company
In response to
pgsql-hackers by date
|Next:||From: Bruce Momjian||Date: 2010-07-02 23:20:41|
|Subject: Re: _bt_parent_deletion_safe() isn't safe|
|Previous:||From: Robert Haas||Date: 2010-07-02 21:44:14|
|Subject: Re: keepalives on MacOS X|