Andrew Dunstan <andrew@dunslane.net> writes:
> Peter Eisentraut wrote:
>> Well, someone could implement UTF-16 or UTF-whatever as client encoding.
>> But I have not heard of any concrete proposals about that.
> Doesn't the nul byte problem make that seriously hard?
Just about impossible. It would require a protocol bump, and removal of
C-style string usage *everywhere* on the client side.
Again, this is something that might be more feasible with encoding
conversion inside psql --- translating UTF16 to UTF8 immediately upon
reading it from any external file would confine the problem to possibly
manageable bounds.
regards, tom lane