So anyway, consider me nudged to finish my patch to provide capability for that by 1 Jan.
My earlier patch aimed to allow WALReceiver to wait on both a latch and a socket as well as allow WALWriter to be active, so that WALReceiver could reply more quickly and handle greater workload. As I explained previously when we discussed that in recent posts, it is necessary infrastructure to have anybody wait on anything higher than remote-fsync. I aim to complete that by 1 Jan.
--
Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services