From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Mental <Mental(at)NeverLight(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: importing data |
Date: | 2004-01-19 17:57:40 |
Message-ID: | 3987.1074535060@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Mental <Mental(at)NeverLight(dot)com> writes:
> We were having trouble with characters that were high ascii encoded.
You probably need to pay attention to your client_encoding setting,
and perhaps also reconsider what database encoding you are using.
If either of these is not SQL_ASCII then it had better be an accurate
description of the character set you are using, else you're in for a
world of hurt :-(. Also, setting client_encoding to SQL_ASCII when the
database encoding is something else does not get you out of having to
respect the encoding setting --- it just prevents any automatic
conversion from happening during I/O. The data you ship had better be
in the database encoding in this case.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2004-01-19 17:57:54 | Re: New PostgreSQL search resource |
Previous Message | Fernando Schapachnik | 2004-01-19 17:57:01 | Re: 7.4 -> 7.4.1 upgrade with customization on freebsd |