On 2013-10-15 16:12:56 +0530, Pavan Deolasee wrote: > On Tue, Oct 15, 2013 at 3:59 PM, Andres Freund <and...@2ndquadrant.com>wrote: > > > > > I don't think that'd be a good idea - the "caughtup" logic is used to > > determine whether we need to wait for further wal to be generated > > locally if we haven't got anything else to do. And we only need to do so > > when we reached the end of the WAL. > > > > > Obviously I do not understand the logic caughtup fully, but don't you think > the log message about standby having caught up with master while it hasn't > because the sender has buffered a lot of data, is wrong ? Or are you saying > those are two different things really ?
The message is logged when the state changes because the state is important for the behaviour of replication (e.g. that node becomes elegible for sync rep). I don't think delaying the message is a good idea. Greetings, Andres Freund -- Andres Freund 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