We need to calculate a more accurate time since WAL arrived to make
max_standby_delay sensible in all cases. Difficult to know exactly when
to record new timestamps for received WAL. So, proposal is...
if (Base time is earlier than WAL record time)
standby_delay = WAL record time - Base time
standby_delay = now() - Base time
When standby_mode = off we record new base time when a new WAL file
When standby_mode = on we record new base time each time we do
XLogWalRcvFlush(). We also record a new base time on first entry to the
main for loop in XLogRecv(), i.e. each time we start writing a new burst
of streamed WAL data.
So in either case, when we are waiting for new input we reset the timer
as soon as new WAL is received. The resolution/accuracy of standby_delay
will be no more than the time taken to replay a single file. This
shouldn't matter, since sane settings of max_standby_delay are either 0
or a number like 5-20 (seconds).
Which means if we are busy we don't record many new times, whereas if we
are working in sporadic bursts we keep up with the latest time of
receipt. This also works when we are performing an archive_recovery for
an old backup.
Startup process will access base time each time it begins to wait and
calculate current standby_delay before comparing against
Simon Riggs www.2ndQuadrant.com
pgsql-hackers by date
|Next:||From: Heikki Linnakangas||Date: 2010-01-15 16:47:44|
|Subject: Re: Streaming replication, loose ends|
|Previous:||From: Heikki Linnakangas||Date: 2010-01-15 16:42:27|
|Subject: Re: New XLOG record indicating WAL-skipping|