Re: WAL segment management on a standby

On 07/14/2014 09:57 PM, John Scalia wrote:
>
> First, it whined about no history.0000004 file, which as the last WAL
> segment is 0000000030000000E00000004E, I'm guessing the standby thought
> the timeline might have been changed, but it was not. Then, it
> complained about no history.00000003 file in the archive area. This file
> had already been copied up into pg_xlog and deleted from the archive.

No immediate answer for you there.

> Finally, the last complaint was that it couldn't find
> 0000000030000000E00000004F in the archive. It appears that under
> streaming a standby server will write concurrently with the primary any
> WAL segment the primary is still generating. I say this as that missing
> WAL segment ("...4F") was already in the pg_xlog directory, but it
> hadn't yet made it into the archive area. Eventually, 10 minutes later,
> 4F did appear in the archive. Is my interpretation here correct, that a
> standby will concurrently write a WAL segment in streaming replication
> mode?

The xlog files get written to in pg_xlog until they're rotated. When
rotated, they get archived; when the archive command completes, they
become accessible to standby servers.

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services