Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id C7B291337B69 for ; Wed, 23 Mar 2011 11:18:52 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 80762-09 for ; Wed, 23 Mar 2011 14:18:44 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.216.181]) by mail.postgresql.org (Postfix) with ESMTP id AA46F1337B43 for ; Wed, 23 Mar 2011 11:18:44 -0300 (ADT) Received: by qyg14 with SMTP id 14so7100785qyg.19 for ; Wed, 23 Mar 2011 07:18:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:reply-to:to:subject:date:user-agent:cc :references:in-reply-to:x-kmail-markup:mime-version:content-type :content-transfer-encoding:message-id; bh=0FcoJdO5TR67aT0yPQN4PxlyUfN/oswtWMm38QpkKDU=; b=KIKUFRzoo0JomVfIu7jIUovcg1sbJJPlb2RloohstBgB6AE5ZByft8FvoHN6JjBksT ENmLVPE0HXIhB1lvz+lNJsdU5tlFwv0s15Kz3XSNIDaiebqwAnj4Ojv4tAuupaCJeySF eb2Ayp+R4yLPkxRUhiFBgnBdi5YVcofun3MwU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:reply-to:to:subject:date:user-agent:cc:references:in-reply-to :x-kmail-markup:mime-version:content-type:content-transfer-encoding :message-id; b=jOlFI0b4aF9TJT5cgL8tQ+SnOP0FVf/vZSD7pjAbOYJZvWjJH6Dy2ghfGiL98jIeMS hGQQAkU5Ve6de8lK+CdA96jbxTi0DSq1DIJ2aSFFdh7TVH/sMBATXBMqUk2VjXJlqkOp t7CjTNX9IxKb8C5XiYKHMPY7GAXiPCYt/PQwo= Received: by 10.52.65.195 with SMTP id z3mr6882136vds.175.1300889925122; Wed, 23 Mar 2011 07:18:45 -0700 (PDT) Received: from tucker.localnet (c-24-17-164-54.hsd1.wa.comcast.net [24.17.164.54]) by mx.google.com with ESMTPS id b26sm2400999vby.15.2011.03.23.07.18.42 (version=SSLv3 cipher=OTHER); Wed, 23 Mar 2011 07:18:43 -0700 (PDT) From: Adrian Klaver Reply-To: adrian.klaver@gmail.com To: pgsql-general@postgresql.org Subject: Re: pg_dump problems Date: Wed, 23 Mar 2011 07:18:39 -0700 User-Agent: KMail/1.13.5 (Linux/2.6.32-30-generic; KDE/4.4.5; i686; ; ) Cc: =?iso-8859-1?q?Mart=EDn_Marqu=E9s?= , Vick Khera References: In-Reply-To: X-KMail-Markup: true MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="Boundary-01=_/EgiNcFpMiXCp5j" Content-Transfer-Encoding: 7bit Message-Id: <201103230718.40361.adrian.klaver@gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.588 tagged_above=-5 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, T_TO_NO_BRKTS_FREEMAIL=0.01 X-Spam-Level: X-Archive-Number: 201103/815 X-Sequence-Number: 174076 --Boundary-01=_/EgiNcFpMiXCp5j Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Wednesday, March 23, 2011 6:57:35 am Mart=C3=ADn Marqu=C3=A9s wrote: > Now I'm getting weirder things. I did a pg_dump with -d option and the > dump adds strange caracters: As previously stated try using the 8.4 version of pg_dump to dump the 8.3=20 database. FYI in 8.4+ there is no -d option anymore, it has become --insert= s to=20 reduce confusion with other commands where -d specified the database. >=20 > ERROR: error de sintaxis en o cerca de =C2=ABI=C2=BB > L=C3=8DNEA 1: I^NSERT INTO objeto_datos_rep VALUES (1172339, 387943, 'Wil= de... >=20 > Could it be binary corruption (pg_dump for example)? >=20 > 2011/3/23 Vick Khera : > > 2011/3/23 Mart=C3=ADn Marqu=C3=A9s : > >> The scenario is like this. I tried today to dump a DB from our > >> production server to load on our development server and got some > >> errors, which I show below. > >=20 > > Try using the pg_dump from the 8.4 install to create your dump file. >=20 > I'll try this. >=20 > > Also make sure your 8.3 installation doesn't have a non-default bytea > > encoding setting (not sure when that setting was introduced, so there > > may not even be such a setting). >=20 > bytea has encoding? I thought it was plain binary data. I think he was talking about bytea_output, which appeared in 9.0. In any event you may want to verify that the encodings/locales for the two= =20 databases are the same. =2D-=20 Adrian Klaver adrian.klaver@gmail.com --Boundary-01=_/EgiNcFpMiXCp5j Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

On Wednesda= y, March 23, 2011 6:57:35 am Mart=C3=ADn Marqu=C3=A9s wrote:

> Now I'= m getting weirder things. I did a pg_dump with -d option and the

> dump a= dds strange caracters:

As previous= ly stated try using the 8.4 version of pg_dump to dump the 8.3 database. FY= I in 8.4+ there is no -d option anymore, it has become --inserts to reduce = confusion with other commands where -d specified the database.

>

> ERROR:= error de sintaxis en o cerca de =C2=ABI=C2=BB

> L=C3= =8DNEA 1: I^NSERT INTO objeto_datos_rep VALUES (1172339, 387943, 'Wilde...<= /p>

>

> Could = it be binary corruption (pg_dump for example)?

>

> 2011/3= /23 Vick Khera <vivek@khera.org>:

> > 2= 011/3/23 Mart=C3=ADn Marqu=C3=A9s <martin.marques@gmail.com>:

> >&g= t; The scenario is like this. I tried today to dump a DB from our

> >&g= t; production server to load on our development server and got some

> >&g= t; errors, which I show below.

> > <= /p>

> > T= ry using the pg_dump from the 8.4 install to create your dump file.

>

> I'll t= ry this.

>

> > A= lso make sure your 8.3 installation doesn't have a non-default bytea

> > e= ncoding setting (not sure when that setting was introduced, so there

> > m= ay not even be such a setting).

>

> bytea = has encoding? I thought it was plain binary data.

I think he = was talking about bytea= _output, which appeared in 9.0.

In any even= t you may want to verify that the encodings/locales for the two databases a= re the same.

--

Adrian Klav= er

adrian.klav= er@gmail.com

--Boundary-01=_/EgiNcFpMiXCp5j--