Re: client_encoding error on load

From: "Praveen" <praveen(dot)k(at)renaissance-it(dot)com>
To: "Andrew Goodnough" <agoodno(at)gmail(dot)com>, <pgsql-admin(at)postgresql(dot)org>
Subject: Re: client_encoding error on load
Date: 2008-08-04 04:23:45
Message-ID: 011201c8f5e9$e24fba00$274610ac@praveenkm
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

It will better you export and import through network by using following command.
psql -U < schemaname > < databasename> --schema=schemaname | psql -U postgres -h < IP adddress of system where you are importing data> <database name>
----- Original Message -----
From: Andrew Goodnough
To: pgsql-admin(at)postgresql(dot)org
Sent: Monday, August 04, 2008 7:29 AM
Subject: [ADMIN] client_encoding error on load

I'm using these commands to perform a dump and load.

pg_dump -c lakevie_typo | gzip > $HOME/backups/typo_$DATE.sql.gz
gzip < $HOME/backups/typo_$DATE.sql.gz |psql -d lakevie_typobak -f -

The dump is fine but the load only works if I first extract the sql, then run it. Running it using the pipe to psql, I get:

psql:<stdin>:71: ERROR: invalid byte sequence for encoding "UTF8": 0x8b
HINT: This error can also happen if the byte sequence does not match the encoding expected by the server, which is controlled by "client_encoding".

yet, doing a 'psql -l' shows this database to be UTF-8. And the dump file says:

SET client_encoding = 'UTF8';

My goal is to get the two line dump/load working so I don't have any manual steps and sql files laying around. Any ideas?

Andy

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Andrew Goodnough 2008-08-04 04:25:24 Re: client_encoding error on load
Previous Message Tom Lane 2008-08-04 02:38:14 Re: client_encoding error on load