| From: | Jim Nasby <jim(at)nasby(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: psql blows up on BOM character sequence |
| Date: | 2014-03-22 16:26:51 |
| Message-ID: | 532DB9CB.5080209@nasby.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/21/14, 4:54 PM, Tom Lane wrote:
> 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?
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's what should happen.
--
Jim C. Nasby, Data Architect jim(at)nasby(dot)net
512.569.9461 (cell) http://jim.nasby.net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2014-03-22 16:28:16 | Re: Partial index locks |
| Previous Message | Jim Nasby | 2014-03-22 16:23:37 | Re: psql blows up on BOM character sequence |