aboutsummaryrefslogtreecommitdiff
path: root/contrib/intarray/_int_gist.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2014-02-13 18:45:15 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2014-02-13 18:46:03 -0500
commitf208fb436b40e08189e40c0602f3d5b9882c6dac (patch)
tree6bf88b8899377f606aa80748af0a8b19d65391e4 /contrib/intarray/_int_gist.c
parentfb47de2be6e44397ab40508729606697f52702ac (diff)
downloadpostgresql-f208fb436b40e08189e40c0602f3d5b9882c6dac.tar.gz
postgresql-f208fb436b40e08189e40c0602f3d5b9882c6dac.zip
Clean up error cases in psql's COPY TO STDOUT/FROM STDIN code.
Adjust handleCopyOut() to stop trying to write data once it's failed one time. For typical cases such as out-of-disk-space or broken-pipe, additional attempts aren't going to do anything but waste time, and in any case clean truncation of the output seems like a better behavior than randomly dropping blocks in the middle. Also remove dubious (and misleadingly documented) attempt to force our way out of COPY_OUT state if libpq didn't do that. If we did have a situation like that, it'd be a bug in libpq and would be better fixed there, IMO. We can hope that commit fa4440f51628d692f077d54b8313aea31af087ea took care of any such problems, anyway. Also fix longstanding bug in handleCopyIn(): PQputCopyEnd() only supports a non-null errormsg parameter in protocol version 3, and will actively fail if one is passed in version 2. This would've made our attempts to get out of COPY_IN state after a failure into infinite loops when talking to pre-7.4 servers. Back-patch the COPY_OUT state change business back to 9.2 where it was introduced, and the other two fixes into all supported branches.
Diffstat (limited to 'contrib/intarray/_int_gist.c')
0 files changed, 0 insertions, 0 deletions