Re: psql blows up on BOM character sequence

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: andrew(at)dunslane(dot)net, mmoncure(at)gmail(dot)com, jim(at)nasby(dot)net, pgsql-hackers(at)postgresql(dot)org
Subject: Re: psql blows up on BOM character sequence
Date: 2014-03-25 00:28:45
Message-ID: 20140325.092845.1908431098781098182.t-ishii@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> The code would probably be pretty trivial, *if* we had consensus on
> what the behavior ought to be. I'm not sure if we do. People who
> only use Unicode would probably like it if BOMs were unconditionally
> swallowed, whether or not psql thinks the client_encoding is UTF8.
> (And I seem to recall somebody even proposing that finding a BOM
> be cause to switch the client_encoding to UTF8.)

This is a bad idea. ISO 8859-1 uses 0xfe and 0xff (BOM) for some
characters.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2014-03-25 01:07:07 Re: Useless "Replica Identity: NOTHING" noise from psql \d
Previous Message Michael Paquier 2014-03-25 00:28:22 Re: About adding an attribute to pg_attibute