On Tue, Aug 16, 2011 at 11:56 PM, Heikki Linnakangas
wrote:
> I think there's a race condition here. If a walsender is just starting up,
> it might not have registered itself as a walsender yet. It's actually been
> there before this patch to suppress the log message.
Right. To address this probl
On 16.08.2011 16:25, Simon Riggs wrote:
On Tue, Aug 16, 2011 at 9:55 AM, Fujii Masao wrote:
When I tested the PITR on git master with max_wal_senders> 0,
I found that the following inappropriate log meesage was always
output even though cascading replication is not in progress. Attached
patch
On Tue, Aug 16, 2011 at 9:55 AM, Fujii Masao wrote:
> When I tested the PITR on git master with max_wal_senders > 0,
> I found that the following inappropriate log meesage was always
> output even though cascading replication is not in progress. Attached
> patch fixes this problem.
>
> LOG: t
Hi,
When I tested the PITR on git master with max_wal_senders > 0,
I found that the following inappropriate log meesage was always
output even though cascading replication is not in progress. Attached
patch fixes this problem.
LOG: terminating all walsender processes to force cascaded
standb
