Tom Lane <[EMAIL PROTECTED]> writes: > In the second place, we don't treat communication failures as ERRORs, > so how did step 3 happen?
You probably realize this, but just in case: "Broken Pipe" probably means the backend received SIGPIPE, not just that some file operation syscall returned -1. -- greg ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings
