Re: UTF8 with BOM support in psql

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Bruce Momjian <bruce@momjian.us>, Itagaki Takahiro <itagaki.takahiro@oss.ntt.co.jp>, pgsql-hackers@postgresql.org
Date: 2009-10-20T15:51:31Z
Lists: pgsql-hackers
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