Re: UTF8 with BOM support in psql - Mailing list pgsql-hackers

From Tom Lane
Subject Re: UTF8 with BOM support in psql
Date
Msg-id 26930.1256049406@sss.pgh.pa.us
Whole thread Raw
In response to Re: UTF8 with BOM support in psql  (Bruce Momjian <bruce@momjian.us>)
Responses Re: UTF8 with BOM support in psql
List pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes:
> Seems there is community support for accepting BOM:
>     http://archives.postgresql.org/pgsql-hackers/2009-09/msg01625.php

That discussion has approximately nothing to do with the
much-more-invasive change that Itagaki-san is suggesting.

In particular I think an automatic change of client_encoding isn't
particularly a good idea --- wouldn't you have to change it back later,
and is there any possibility of creating a security issue from such
behavior?  Remember that client_encoding *IS* tied to security issues
such as backslash escape handling.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Controlling changes in plpgsql variable resolution
Next
From: Tom Lane
Date:
Subject: Re: Application name patch - v2