Do we need to review the fsync error handling in pg_receivewal and pg_recvlogical, following the recent backend changes? The current default behavior is that these tools will log fsync errors and then reconnect and proceed with the next data streaming in. As a result, you might then have some files in the accumulated WAL that have not been fsynced. Perhaps a hard exit would be more appropriate?
-- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
