Re: Update of replication/README - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Update of replication/README
Date
Msg-id AANLkTimHzxEhgiCKDAtxE8pATkK+z_prz-adin1Yammh@mail.gmail.com
Whole thread Raw
In response to Update of replication/README  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: Update of replication/README
List pgsql-hackers
On Wed, Mar 9, 2011 at 6:11 AM, Fujii Masao <masao.fujii@gmail.com> wrote:
> The attached patch updates replication/README to reflect current
> walsender/walreceiver behavior. It doesn't include any description
> about sync rep. That would need to be added later.

Hrm.  What about this hunk?

-Each walsender allocates an entry from the WalSndCtl array, and advertises
-there how far it has streamed WAL already. This is used at checkpoints, to
-avoid recycling WAL that hasn't been streamed to a slave yet. However,
-that doesn't stop such WAL from being recycled when the connection is not
-established.
+Each walsender allocates an entry from the WalSndCtl array, and tracks
+information about replication progress. User can monitor them via
+statistics views.

Is the deleted text not (or no longer) true?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: wrap alpha4 tomorrow ~9am Eastern (was: Alpha4 release blockers)
Next
From: Robert Haas
Date:
Subject: Re: How should the waiting backends behave in sync rep?