Re: psql blows up on BOM character sequence - Mailing list pgsql-hackers

From Tom Lane
Subject Re: psql blows up on BOM character sequence
Date
Msg-id 26821.1395438848@sss.pgh.pa.us
Whole thread Raw
In response to Re: psql blows up on BOM character sequence  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: psql blows up on BOM character sequence  (Jim Nasby <jim@nasby.net>)
List pgsql-hackers
Merlin Moncure <mmoncure@gmail.com> writes:
> 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.

Well, that seems like a solvable but rather independent problem.
I guess one issue is how you'd define the meaning of --single ...
one transaction per run, or one per file?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Memory ordering issue in LWLockRelease, WakeupWaiters, WALInsertSlotRelease
Next
From: Andres Freund
Date:
Subject: Re: Why is autovacuum_freeze_max_age a postmaster setting?