| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp>, Bruce Momjian <bruce(at)momjian(dot)us>, Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: encoding of PostgreSQL messages |
| Date: | 2009-02-11 07:05:56 |
| Message-ID: | 499278D4.7040802@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane wrote:
> Reflecting on the bigger picture ... I would imagine that the vast
> majority of existing applications depend on client_encoding settings
> that come from postgresql.conf, ALTER USER SET, ALTER DATABASE SET, or
> just the default (== database encoding). I don't think a solution that
> penalizes those cases and makes only the case of setting it via
> PGCLIENTENCODING work nicely is going to make very many people happy.
I don't have any survey data available, but I think this assessment is
semantically wrong. Usefully, the client encoding can come only from
the client, or be defaulted (and even that is semantically wrong). I
see the other cases as workarounds.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-02-11 07:07:12 | Re: encoding of PostgreSQL messages |
| Previous Message | Pavel Stehule | 2009-02-11 07:04:58 | Re: Pl/PgSQL String formatting like raise? |