Cascaded standby message - Mailing list pgsql-hackers

From Magnus Hagander
Subject Cascaded standby message
Date
Msg-id CABUevEz-bnf8sCNb_1UVPP9G8x-GQsrQBLyO_QCzm6B6kepd3A@mail.gmail.com
Whole thread Raw
Responses Re: Cascaded standby message
List pgsql-hackers
From what I can tell, everytime I start a postmaster on HEAD (at least
when i've set wal_level=archive, and max_wal_senders > 0), I get the
message:
LOG:  terminating all walsender processes to force cascaded standby(s)
to update timeline and reconnect

in the startup log.

This is long before I've connected any slaves or even considered
cascading standbys - seems this message is written unnecessarily?

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/


pgsql-hackers by date:

Previous
From: PostgreSQL - Hans-Jürgen Schönig
Date:
Subject: Re: help with plug-in function for additional (partition/shard) visibility checks
Next
From: Hannu Krosing
Date:
Subject: Re: help with plug-in function for additional (partition/shard) visibility checks