| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Barry Lind <blind(at)xythos(dot)com> |
| Cc: | Malcolm Warren <malcolm(at)villeinitalia(dot)com>, <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Bug #814 |
| Date: | 2003-09-15 17:14:17 |
| Message-ID: | Pine.LNX.4.33.0309151311110.15996-100000@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Mon, 15 Sep 2003, Barry Lind wrote:
> Malcolm,
>
> Without knowing what errors you are seeing, I can't say for sure what is
> going wrong for you. However the following seems to work for me:
>
> pg_dump -f test.dmp testdb
> createdb -E unicode newtestdb
> psql -f test.dmp newtestdb
If you have non-unicode characters in the ascii database the restore to a
unicode database will fail. People have recommended running iconv on the
dump file to convert it to unicode, for me setting
PGCLIENTENCODING=UNICODE before the dump of the original database fixed
the problem with bad characters.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2003-09-15 22:07:45 | Re: Statement.cancel() may cancel queries in the future |
| Previous Message | Barry Lind | 2003-09-15 16:21:09 | Re: Bug #814 |