aboutsummaryrefslogtreecommitdiff
path: root/src/tutorial/complex.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2014-02-13 18:45:20 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2014-02-13 18:45:20 -0500
commit2573f08a164bfccb804c46106c0988464dc28e51 (patch)
treea3840ec0ccae7078b010d5f7a3570f2a09853e50 /src/tutorial/complex.c
parent8439ee415f4d8850806a7fb59cc7ce4dbb6ea2ed (diff)
downloadpostgresql-2573f08a164bfccb804c46106c0988464dc28e51.tar.gz
postgresql-2573f08a164bfccb804c46106c0988464dc28e51.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 'src/tutorial/complex.c')
0 files changed, 0 insertions, 0 deletions