Re: psql weird behaviour with charset encodings

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: hernan gonzalez <hgonzalez(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: psql weird behaviour with charset encodings
Date: 2010-05-09 02:19:08
Message-ID: 20736.1273371548@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

hernan gonzalez <hgonzalez(at)gmail(dot)com> writes:
> BTW, I understand that postgresql uses locale semantics in the server code.
> But is this really necessary/appropiate in the client (psql) side?
> Couldnt we stick with C locale here?

As far as that goes, I think we have to turn on that machinery in order
to have gettext() work (ie, to have localized error messages).

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2010-05-09 02:33:21 Re: Database design confusing pg_restore, and misc pg_restore issues
Previous Message Tom Lane 2010-05-09 01:24:45 Re: [GENERAL] psql weird behaviour with charset encodings

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2010-05-09 02:23:43 Re: pg_start_backup and pg_stop_backup Re: Re: [COMMITTERS] pgsql: Make CheckRequiredParameterValues() depend upon correct
Previous Message Tom Lane 2010-05-09 01:24:45 Re: [GENERAL] psql weird behaviour with charset encodings