From: Heikki Linnakangas on 18 Jan 2010 01:28 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 -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Simon Riggs on 18 Jan 2010 03:45 On Mon, 2010-01-18 at 08:28 +0200, Heikki Linnakangas wrote: > 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. How accurate is this now? With regard to remaining items of work. http://wiki.postgresql.org/wiki/Streaming_Replication -- Simon Riggs www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Simon Riggs on 18 Jan 2010 04:30 On Mon, 2010-01-18 at 08:28 +0200, Heikki Linnakangas 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. It wouldn't be a good use of all of our time for me to work on this. I have zero unallocated time remaining and you'd still need to review what I'd written, in any case. -- Simon Riggs www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Fujii Masao on 18 Jan 2010 04:35 On Mon, Jan 18, 2010 at 5:45 PM, Simon Riggs <simon(a)2ndquadrant.com> wrote: > How accurate is this now? With regard to remaining items of work. > http://wiki.postgresql.org/wiki/Streaming_Replication Not accurate. I'll correct that and provide the link from "v8.5 Open Items page" to that. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Fujii Masao on 18 Jan 2010 06:18 On Mon, Jan 18, 2010 at 6:35 PM, Fujii Masao <masao.fujii(a)gmail.com> wrote: > On Mon, Jan 18, 2010 at 5:45 PM, Simon Riggs <simon(a)2ndquadrant.com> wrote: >> How accurate is this now? With regard to remaining items of work. >> http://wiki.postgresql.org/wiki/Streaming_Replication > > Not accurate. I'll correct that and provide the link from > "v8.5 Open Items page" to that. I listed the TODO items that need to be addressed for v8.5. http://wiki.postgresql.org/wiki/Streaming_Replication#v8.5 If you find any other TODO items, please add them to the list. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 4 5 Prev: [HACKERS] Hot Standby and handling max_standby_delay Next: Mammoth in Core? |