On 10/23/2014 06:01 PM, Simon Riggs wrote:
On 23 October 2014 15:39, Fujii Masao <masao.fu...@gmail.com> wrote:
Sorry, I'm going around in the circle. But I'd like to say again, I don't think
this is good idea. It prevents asynchronous pg_receivexlog from fsyncing
WAL data and sending feedbacks more frequently at all. They are useful,
for example, when we want to monitor the write location of asynchronous
pg_receivexlog in almost realtime. But if we adopt the idea, since feedback
cannot be sent soon in async mode, pg_stat_replication always returns
the not-up-to-date location.
Why not send a message every 10 seconds when its not sync rep?
Or even after every write(). It's a tiny amount of network traffic anyway.
- Heikki
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
