| From: | Jim Nasby <jim(at)nasby(dot)net> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: psql blows up on BOM character sequence |
| Date: | 2014-03-22 16:23:37 |
| Message-ID: | 532DB909.5000206@nasby.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/21/14, 8:13 PM, David E. Wheeler wrote:
> On Mar 21, 2014, at 2:16 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
>> Surely if it were really a major annoyance, someone would have sent code to fix it during the last 4 years and more since the above.
>>
>> I suspect it's a minor annoyance :-)
>>
>> But by all means add it to the TODO list if it's not there already.
>
> I have cleaned up many a BOM added to files that made psql blow up. I think PGAdmin III was a culprit, though I’m not sure (I don’t use, it, cleaned up after coworkers who do).
Yes, my coworker that figured out what the problem was said the culprit here is actually pgAdmin. :(
--
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:26:51 | Re: psql blows up on BOM character sequence |
| Previous Message | Tom Lane | 2014-03-22 16:22:17 | Re: Review: plpgsql.extra_warnings, plpgsql.extra_errors |