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

From Jim Nasby
Subject Re: psql blows up on BOM character sequence
Date
Msg-id 532DB9CB.5080209@nasby.net
Whole thread Raw
In response to Re: psql blows up on BOM character sequence  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: psql blows up on BOM character sequence
List pgsql-hackers
On 3/21/14, 4:54 PM, Tom Lane wrote:
> 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?

Well, if you're catting multiple files into psql -1, you'd get all the files in one transaction, right? So I'd say
that'swhat should happen.
 
-- 
Jim C. Nasby, Data Architect                       jim@nasby.net
512.569.9461 (cell)                         http://jim.nasby.net



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: ALTER TABLE lock strength reduction patch is unsafe
Next
From: Thom Brown
Date:
Subject: Re: Partial index locks