Skip site navigation (1) Skip section navigation (2)

UNICODE isn't expressed.(pg_dump,pg_restore)

From: "Hiroshi Saito" <saito(at)inetrt(dot)skcapi(dot)co(dot)jp>
To: "Andreas Pflug" <Andreas(dot)Pflug(at)web(dot)de>
Cc: <pgadmin-hackers(at)postgresql(dot)org>,"Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
Subject: UNICODE isn't expressed.(pg_dump,pg_restore)
Date: 2004-11-17 01:16:45
Message-ID: 024301c4cc43$1aedbe40$1f324d80@w2k (view raw, whole thread or download thread mbox)
Lists: pgadmin-hackers
Hi Andreas.

I think how to solve this problem.

postgresql.conf-> # client_encoding =  this is comment out;
Then, pg_dump is discharged with server_encoding.

postgresql.conf-> client_encoding = UNICODE
Then, pg_dump is discharged with UNICODE.
This case is to see this.

But, this problem seems to contain much.

Any idea?
Thank you.

Hiroshi Saito


pgadmin-hackers by date

Next:From: Hiroshi SaitoDate: 2004-11-17 06:27:12
Subject: Mistake of the pg_dump option
Previous:From: Dave PageDate: 2004-11-16 21:57:36
Subject: RC2 uploaded

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group