Re: psql blows up on BOM character sequence

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Jim Nasby <jim(at)nasby(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: psql blows up on BOM character sequence
Date: 2014-03-21 21:54:08
Message-ID: 26821.1395438848@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Merlin Moncure <mmoncure(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-03-21 21:55:45 Re: Why is autovacuum_freeze_max_age a postmaster setting?
Previous Message Andres Freund 2014-03-21 21:52:33 Re: Memory ordering issue in LWLockRelease, WakeupWaiters, WALInsertSlotRelease