Re: Hot Standby and handling max_standby_delay - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Hot Standby and handling max_standby_delay
Date
Msg-id 4B53FF7D.9040800@enterprisedb.com
Whole thread Raw
In response to Re: Hot Standby and handling max_standby_delay  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Hot Standby and handling max_standby_delay  (Simon Riggs <simon@2ndQuadrant.com>)
Re: Hot Standby and handling max_standby_delay  (Simon Riggs <simon@2ndQuadrant.com>)
Re: Hot Standby and handling max_standby_delay  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Simon Riggs wrote:
> On Sun, 2010-01-17 at 22:57 +0200, Heikki Linnakangas wrote:
>>> It would be good if there was a keepalive WAL record with a
>> timestamp on it generated every N seconds while in streaming mode.
>>
>> Yeah, that would help. In streaming replication we could also send
>> such timestamp as a separate message, not within WAL.
> 
> Is that something you're working on?

No.

> Do we need a new record type for that, is there a handy record type to
> bounce from?

After starting streaming, slices of WAL are sent as CopyData messages.
The CopyData payload begins with an XLogRecPtr, followed by the WAL
data. That payload format needs to be extended with a 'message type'
field and a new message type for the timestamps need to be added.

--  Heikki Linnakangas EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Streaming replication, and walsender during recovery
Next
From: Greg Stark
Date:
Subject: Re: Bloom index