Re: psql blows up on BOM character sequence

On Fri, Mar 21, 2014 at 4:28 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I'd be okay with swallowing a leading BOM if and only if client encoding
> is UTF8.  This should apply to any file psql reads, whether script or
> data.

Yeah.  The one case that doesn't solve is:

cat f1.sql f2.sql | psql ...

Which is common usage in deployment systems where combining things
inside a single transaction scope is important.

There is no way for psql to handle that case though unless you'd strip
*all* BOMs encountered.  Compounding this problem is that there's no
practical way AFAIK to send multiple file to psql via single command
line invocation.  If you pass multiple -f arguments all but one is
ignored.

merlin