Received: from localhost (unknown [200.46.204.183])
	by postgresql.org (Postfix) with ESMTP id 16B036501F0
	for <pgsql-admin-postgresql.org@postgresql.org>;
	Mon,  4 Aug 2008 01:39:24 -0300 (ADT)
Received: from postgresql.org ([200.46.204.86])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 99324-03 for <pgsql-admin-postgresql.org@postgresql.org>;
	Mon,  4 Aug 2008 01:39:13 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from renaissance-it.com (unknown [164.164.87.55])
	by postgresql.org (Postfix) with ESMTP id 16F5A65037C
	for <pgsql-admin@postgresql.org>; Mon,  4 Aug 2008 01:19:24 -0300 (ADT)
Received: (qmail 7300 invoked by uid 109); 4 Aug 2008 04:18:43 -0000
Received: from 192.168.1.6 by sritmail (envelope-from
	<praveen.k@renaissance-it.com>, uid 112) with qmail-scanner-1.25st
	(perlscan: 1.25st.  Clear:RC:1(192.168.1.6):.
	Processed in 0.010145 secs); 04 Aug 2008 04:18:43 -0000
Received: from unknown (HELO praveenkm) (praveen.k@[192.168.1.6])
	(envelope-sender <praveen.k@renaissance-it.com>)
	by renaissance-it.com (qmail-ldap-1.03) with SMTP
	for <agoodno@gmail.com>; 4 Aug 2008 04:18:42 -0000
Message-ID: <011201c8f5e9$e24fba00$274610ac@praveenkm>
From: "Praveen" <praveen.k@renaissance-it.com>
To: "Andrew Goodnough" <agoodno@gmail.com>,
	<pgsql-admin@postgresql.org>
References: <f93eaa100808031859y1c019fcbocc7a58d01c67d488@mail.gmail.com>
Subject: Re: client_encoding error on load
Date: Mon, 4 Aug 2008 09:53:45 +0530
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_010F_01C8F617.FBEB6D50"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.101 tagged_above=0 required=5
	tests=HTML_MESSAGE=0.001, RDNS_NONE=0.1
X-Spam-Level: 
X-Archive-Number: 200808/11
X-Sequence-Number: 29856

This is a multi-part message in MIME format.

------=_NextPart_000_010F_01C8F617.FBEB6D50
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

It will better you export and import through network by using following =
command.
psql -U < schemaname >  < databasename>   --schema=3Dschemaname | psql  =
-U postgres  -h < IP adddress of system where you are importing data> =
<database name>
  ----- Original Message -----=20
  From: Andrew Goodnough=20
  To: pgsql-admin@postgresql.org=20
  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 =3D '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

------=_NextPart_000_010F_01C8F617.FBEB6D50
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2963" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>It will better you export and import =
through=20
network by using following command.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>psql -U &lt; schemaname &gt; &nbsp;&lt; =

databasename&gt;&nbsp;&nbsp; --schema=3Dschemaname | psql&nbsp; -U =
postgres&nbsp;=20
-h &lt; IP adddress of system where you are importing data&gt; =
&lt;database=20
name&gt;</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dagoodno@gmail.com href=3D"mailto:agoodno@gmail.com">Andrew=20
  Goodnough</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dpgsql-admin@postgresql.org=20
  =
href=3D"mailto:pgsql-admin@postgresql.org">pgsql-admin@postgresql.org</A>=
 </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Monday, August 04, 2008 =
7:29=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [ADMIN] =
client_encoding error on=20
  load</DIV>
  <DIV><BR></DIV>
  <DIV dir=3Dltr>I'm using these commands to perform a dump and=20
  load.<BR><BR>pg_dump -c lakevie_typo | gzip &gt;=20
  $HOME/backups/typo_$DATE.sql.gz<BR>gzip &lt; =
$HOME/backups/typo_$DATE.sql.gz=20
  |psql -d lakevie_typobak -f -<BR><BR>The dump is fine but the load =
only works=20
  if I first extract the sql, then run it.&nbsp; Running it using the =
pipe to=20
  psql, I get:<BR><BR>psql:&lt;stdin&gt;:71: ERROR:&nbsp; invalid byte =
sequence=20
  for encoding "UTF8": 0x8b<BR>HINT:&nbsp; This error can also happen if =
the=20
  byte sequence does not match the encoding expected by the server, =
which is=20
  controlled by "client_encoding".<BR><BR>yet, doing a 'psql -l' shows =
this=20
  database to be UTF-8.&nbsp; And the dump file says:<BR><BR>SET =
client_encoding=20
  =3D 'UTF8';<BR><BR><BR>My goal is to get the two line dump/load =
working so I=20
  don't have any manual steps and sql files laying around.&nbsp; Any=20
  ideas?<BR><BR>Andy<BR></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_010F_01C8F617.FBEB6D50--