Re: psql blows up on BOM character sequence

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: Jim Nasby <jim(at)nasby(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: psql blows up on BOM character sequence
Date: 2014-03-21 21:16:07
Message-ID: 532CAC17.7080701@dunslane.net
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 03/21/2014 05:06 PM, Merlin Moncure wrote:
> On Fri, Mar 21, 2014 at 4:02 PM, Jim Nasby <jim(at)nasby(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message MauMau 2014-03-21 21:22:37 Re: [RFC] What should we do for reliable WAL archiving?
Previous Message Merlin Moncure 2014-03-21 21:06:50 Re: psql blows up on BOM character sequence