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

From Tom Lane
Subject Re: Hot Standby and handling max_standby_delay
Date
Msg-id 4813.1263825267@sss.pgh.pa.us
Whole thread Raw
In response to Re: Hot Standby and handling max_standby_delay  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Hot Standby and handling max_standby_delay  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> Simon Riggs wrote:
>> 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.

Whether or not anyone bothers with the timestamp message, I think adding
a message type header is a Must Fix item.  A protocol with no provision
for extension is certainly going to bite us in the rear before long.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Streaming replication, and walsender during recovery
Next
From: Simon Riggs
Date:
Subject: Re: Streaming replication, and walsender during recovery