On Wed, Jul 6, 2011 at 8:53 AM, Fujii Masao <masao.fu...@gmail.com> wrote:
>>> What about outputing something like the following message in that case? >>> >>> if ("walsender receives SIGUSR2") >>> ereport(LOG, "terminating walsender process due to >>> administrator command"); >> >> ...which doesn't explain the situation because we don't know why >> SIGUSR2 was sent. >> >> I was thinking of something like this >> >> LOG: requesting walsenders for cascading replication reconnect to >> update timeline > > Looks better than my proposal. > >> but then I ask: Why not simply send a new message type saying "new >> timeline id is X" and that way we don't need to restart the connection >> at all? > > Yeah, that's very useful. But I'd like to implement that as a separate patch. > > I'm thinking that in that case walsender should send the timeline history file > and walreceiver should write it down to the disk, instead of just sending > timeline ID. Otherwise, when the standby in receive side restarts, it cannot > calculate the latest timeline ID correctly. OK, happy to do that part as an additional patch. That way we can get this committed soon - in this CF. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers