Re: Determining client_encoding from client locale

From: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, Peter Eisentraut <peter_e(at)gmx(dot)net>
Subject: Re: Determining client_encoding from client locale
Date: 2010-02-24 16:37:34
Message-ID: 3073cc9b1002240837y54006fbdrfd308a0e8157e397@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 24, 2010 at 11:07 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> Did this patch go anywhere?  Is it a TODO?
>

There were problems with that patch, maybe Heikki will review it again
for 9.1 but for now it's already a TODO, it's in the "Multi-Language
Support" section

Set client encoding based on the client operating system encoding

Currently client_encoding is set in postgresql.conf, which
defaults to the server encoding.

* Re: [GENERAL] invalid byte sequence ?

--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-02-24 16:39:20 Re: A thought on Index Organized Tables
Previous Message Tom Lane 2010-02-24 16:30:50 Re: [COMMITTERS] pgsql: Un-break pg_dump for the case of zero-column tables.