From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andreas <maps(dot)on(at)gmx(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: invalid byte sequence ? |
Date: | 2006-08-24 13:45:23 |
Message-ID: | 20060824134523.GC18349@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Martijn van Oosterhout wrote:
> For glibc systems we can get 100% reliable results. Even for other
> systems there's standard code out there for determining the charset.
> But this has been discussed before:
>
> http://archives.postgresql.org/pgsql-hackers/2003-05/msg00744.php
> http://archives.postgresql.org/pgsql-general/2004-04/msg00470.php
> http://archives.postgresql.org/pgsql-hackers/2006-06/msg01027.php
>
> It seems to me that setting the client encoding based on the
> client-locale is the *only* sensible way of doing it. The locale is
> going to effect the results of programs like sort and any scripts used
> to process the data anyway.
Yes please. This would make the pgsql-es-ayuda list lose a small but
measurable amount of its traffic (which I won't miss). Non-matching
\encoding settings is just too frequent.
FWIW I'm not sure if it really belongs in libpq, or it must be rather in
psql (and thus in every client).
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2006-08-24 13:45:49 | Re: Saving a jpg into Postgresql table |
Previous Message | Silvela, Jaime (Exchange) | 2006-08-24 13:21:32 | Re: Can't open Postgres at all!!! |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-08-24 13:58:10 | Re: Autovacuum on by default? |
Previous Message | Alvaro Herrera | 2006-08-24 13:38:43 | Re: Autovacuum on by default? |