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

From David E. Wheeler
Subject Re: psql blows up on BOM character sequence
Date
Msg-id A99A0A7A-B735-4A12-AA83-AD79C2A5BBFF@justatheory.com
Whole thread Raw
In response to Re: psql blows up on BOM character sequence  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: psql blows up on BOM character sequence  (Jim Nasby <jim@nasby.net>)
List pgsql-hackers
On Mar 21, 2014, at 2:16 PM, Andrew Dunstan <andrew@dunslane.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
sincethe 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). 

David




pgsql-hackers by date:

Previous
From: Vik Fearing
Date:
Subject: Re: Partial index locks
Next
From: Michael Paquier
Date:
Subject: Re: Patch for CREATE RULE sgml -- Was in: [DOCS]