Re: [PATCH] Add SIGCHLD catch to psql

Stephen Frost <sfrost@snowman.net>

From: Stephen Frost <sfrost@snowman.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>, David Fetter <david@fetter.org>, Bruce Momjian <bruce@momjian.us>, pgsql-hackers@postgresql.org
Date: 2010-05-16T16:04:15Z
Lists: pgsql-hackers
* Tom Lane (tgl@sss.pgh.pa.us) wrote:
> A saner
> approach, which would also help for other corner cases such as
> out-of-disk-space, would be to check for write failures on the output
> file and abandon the query if any occur.

I had considered this, but I'm not sure we really need to catch *every*
write failure.  Perhaps just catching if the '\n' at the end of a row
fails to be written out would be sufficient?  Then turning around and
setting cancel_query might be enough..  I'll write that up and test if
it works.

	Thanks,

		Stephen