pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Hannes Dorbath <light@theendofthetunnel.de>
Cc: pgsql-admin@postgresql.org
Subject: Re: character problem
Date: Mon, 10 Oct 2005 10:27:27 -0400
Message-ID: <20560.1128954447@sss.pgh.pa.us> (raw)
In-Reply-To: <dideic$1ppa$1@news.hub.org>
References: <4349106C.6080206@infinito.it>
	<did562$epf$1@news.hub.org>
	<434A2792.1070106@infinito.it>
	<didaip$2me3$1@news.hub.org>
	<dideic$1ppa$1@news.hub.org>

Hannes Dorbath <light@theendofthetunnel.de> writes:
> On 10.10.2005 11:56, Luca Ferrari wrote:
>> gestione_personale=# \l
>> List of databases
>> Name        |   Owner   | Encoding
>> --------------------+-----------+-----------
>> gestione_database  | dbmanager | SQL_ASCII
>> gestione_personale | wwwrun    | SQL_ASCII
>> template0          | dbmanager | SQL_ASCII
>> template1          | dbmanager | SQL_ASCII

> OK, so you are not using Unicode. I don't know much about the SQL_ASCII 
> charset, but I expect it to slightly differ from LATIN1. Type

> SET client_encoding = LATIN1;

No, SQL_ASCII represents the complete absence of any encoding
knowledge.  With this database setting, changing client_encoding is a
complete no-op.  Postgres will just absorb and re-emit strings exactly
as they were supplied originally, no matter what client_encoding is.

The cause of the unexpected conversions Luca is having trouble with must
be somewhere on the client side.  It's not going to be done by Postgres
with this encoding setting.

If you are actively dealing with non-7-bit-ASCII data, using SQL_ASCII
for the database encoding is probably a bad idea, exactly because
Postgres won't help you out at all with converting encodings or
enforcing that data is validly encoded.

			regards, tom lane



view thread (10+ messages)  latest in thread

Message-ID: <20560.1128954447@sss.pgh.pa.us>
Permalink:  ../20560.1128954447@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/20560.1128954447@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, light@theendofthetunnel.de
  Subject: Re: character problem
  In-Reply-To: <20560.1128954447@sss.pgh.pa.us>
  References: <4349106C.6080206@infinito.it> <did562$epf$1@news.hub.org> <434A2792.1070106@infinito.it> <didaip$2me3$1@news.hub.org> <dideic$1ppa$1@news.hub.org> <20560.1128954447@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox