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
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?
pgsql-hackers by date
|Next:||From: Hannu Krosing||Date: 2011-09-02 12:36:00|
|Subject: Re: help with plug-in function for additional
(partition/shard) visibility checks|
|Previous:||From: PostgreSQL - Hans-Jürgen Schönig||Date: 2011-09-02 12:01:51|
|Subject: Re: help with plug-in function for additional (partition/shard) visibility checks|