Skip site navigation (1) Skip section navigation (2)

Cascaded standby message

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Cascaded standby message
Date: 2011-09-02 12:19:35
Message-ID: CABUevEz-bnf8sCNb_1UVPP9G8x-GQsrQBLyO_QCzm6B6kepd3A@mail.gmail.com (view raw or flat)
Thread:
Lists: 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/

Responses

pgsql-hackers by date

Next:From: Hannu KrosingDate: 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önigDate: 2011-09-02 12:01:51
Subject: Re: help with plug-in function for additional (partition/shard) visibility checks

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group