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

From Andrew Dunstan
Subject Re: psql blows up on BOM character sequence
Date
Msg-id 532CAC17.7080701@dunslane.net
Whole thread Raw
In response to Re: psql blows up on BOM character sequence  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: psql blows up on BOM character sequence  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: psql blows up on BOM character sequence  ("David E. Wheeler" <david@justatheory.com>)
List pgsql-hackers
On 03/21/2014 05:06 PM, Merlin Moncure wrote:
> On Fri, Mar 21, 2014 at 4:02 PM, Jim Nasby <jim@nasby.net> wrote:
>> See http://www.postgresql.org/message-id/4AFEAB39.3000009@dunslane.net
>>
>> This is still broken as of fairly recent HEAD; any objections to adding it to TODO?
> Agreed: this is a major annoyance.
>



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.


cheers

andrew



pgsql-hackers by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: psql blows up on BOM character sequence
Next
From: Simon Riggs
Date:
Subject: Re: ALTER TABLE lock strength reduction patch is unsafe Reply-To: