"Joel Jacobson" <[email protected]> writes: > Fix by adjusting handleCopyIn() to use the binary code path also when the copy > source is a file (i.e., copystream != pset.cur_cmd_source), even in textual > copies.
That seems like a hack, as it also changes the behavior w.r.t.
prompts and EOF-mark detection, neither for the better.
I'm not really convinced that we need to do anything at all
about this.
regards, tom lane
