Andrew Dunstan <andrew@dunslane.net> writes:
> What I think we might sensibly do is to eat the leading BOM of an SQL
> file iff the client encoding is UTF8, and otherwise treat it as just
> bytes in whatever the encoding is.
That seems relatively non-risky.
> Should we also do the same for files passed via \copy? What about
> streams on stdin? What about files read from the backend via COPY?
Not thrilled about doing this on stdin --- you have no good
justification for assuming that start of stdin corresponds to a file
boundary somewhere. COPY files, maybe.
regards, tom lane
