Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> What platform is this on? Is it possible that on some platform the chunk
> size we're using is not doing an atomic write?
Another idea is that some of the write() calls are failing --- elog.c
doesn't check for that. Eyeing the POSIX spec for write(), I wonder
if somehow the pipe has gotten set into O_NONBLOCK mode and we're
not retrying EAGAIN failures.
regards, tom lane