| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "jesse(dot)waters(at)gmail(dot)com" <jesse(dot)waters(at)gmail(dot)com> |
| Cc: | "Michael Glaesemann" <grzm(at)seespotcode(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: UTF8 frustrations |
| Date: | 2007-09-05 19:39:13 |
| Message-ID: | dcc563d10709051239m25cce432taf68be465da5741d@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 9/5/07, jesse(dot)waters(at)gmail(dot)com <jesse(dot)waters(at)gmail(dot)com> wrote:
> Thanks all for the quick replies.
>
> SET client_encoding = 'UTF8';
>
> Results, same error. Now I'm really concerned.
How / where are you setting the client_encoding? I'm wonder if it's
really set when the pg_dump / pg_restore commands are being issued, or
if you're inheriting a different encoding along with the new
connection it gets.
You can try:
alter user set client_encoding='UTF8'
for the postgres user to see if that helps.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2007-09-05 20:06:48 | Re: psql hanging |
| Previous Message | Scott Marlowe | 2007-09-05 19:30:37 | Re: SQL for Deleting all duplicate entries |