Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 238761337BCC for ; Wed, 23 Mar 2011 14:33:11 -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 60277-04 for ; Wed, 23 Mar 2011 17:33:03 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-iw0-f174.google.com (mail-iw0-f174.google.com [209.85.214.174]) by mail.postgresql.org (Postfix) with ESMTP id 8D1461337BC8 for ; Wed, 23 Mar 2011 14:33:03 -0300 (ADT) Received: by iwn34 with SMTP id 34so8779272iwn.19 for ; Wed, 23 Mar 2011 10:33:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Pu3sQK1LY2bxM9YZB6MHjj0AGffw8kWY/5+9gpLur/M=; b=j7EvmQgnyPSHCSJOOEL4LOYfluNTbYjEJUujyegLIy5sD3jnn9uam9y9Eei9N6Zivk lNPYUySNviz08EmK4IAlTUCuWrBwSGKQh8XxIAjrV5wBRXy2coEeey+zW3X49H8eXjVx Lk4SenhKk5wKA8KFuECnGwHQxOdEyB5e4JfeU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=QL85o2L3Rz6Wo0f00D80CHE6N0Fr+clBJbuFxDLZ2fWIfsaNwuuTFlMjQt/NrlDmit MwQ5fF1O1t0NPYp1VvSyR5PktAHLmKFJ/oiGeeyBpzBn4mszrgbxxAgZPqS9jubxjyIC ektEM2lRGwxPj7aqGbhMjCoIkZAZPGQ4aCRrM= MIME-Version: 1.0 Received: by 10.43.50.5 with SMTP id vc5mr9056525icb.198.1300901582835; Wed, 23 Mar 2011 10:33:02 -0700 (PDT) Received: by 10.231.211.149 with HTTP; Wed, 23 Mar 2011 10:33:02 -0700 (PDT) In-Reply-To: <4D8A27DB.70702@gmail.com> References: <201103230718.40361.adrian.klaver@gmail.com> <4D8A27DB.70702@gmail.com> Date: Wed, 23 Mar 2011 14:33:02 -0300 Message-ID: Subject: Re: pg_dump problems From: =?UTF-8?B?TWFydMOtbiBNYXJxdcOpcw==?= To: Adrian Klaver Cc: pgsql-general@postgresql.org, Vick Khera Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-5 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7 X-Spam-Level: X-Archive-Number: 201103/830 X-Sequence-Number: 174091 El d=C3=ADa 23 de marzo de 2011 14:03, Adrian Klaver escribi=C3=B3: > On 03/23/2011 07:56 AM, Mart=C3=ADn Marqu=C3=A9s wrote: >> >> >> Ok, did a remote dump (from the development server which has pg 8.4) >> and I got a similar error: >> >> psql:siprebi-bu.sql:27374: ERROR: =C2=A0sintaxis de entrada no >> vlida para tipo bytea >> CONTEXT: =C2=A0COPY novedades_fotos, lnea 273, columna foto: >> >> \377\330\377\340\000\020JFIF\000\001\001\001\000`\000`\000\000\3= 77\341<\310Exif\000\000II >> *\000\010\0... >> psql:siprebi-bu.sql:3477848: ERROR: =C2=A0la sintaxis de entrada no es >> vlida para integer:q43116 >> CONTEXT: =C2=A0COPY objetos, lnea 99185, columna codigo: >> q43116 >> > > So you are feeding a plain text dump to psql correct? How can I verify this? It's already dificult to manage the file, asi it has over 700Mb. The second error is very curious, as it looks like pg_dump changed 1 for a 'q' in an integer field: psql:siprebi-bu.sql:2219245: ERROR: la sintaxis de entrada no es v=C3=A1lida para integer: =C2=ABq721695=C2=BB CONTEXT: COPY objeto_datos_rep, l=C3=ADnea 991894, columna codigo: =C2=ABq= 721695=C2=BB Looking at the dump file I see this: 1721693 657083 Eclairage... 5 1721694 657083 photometrie 5 q721695 657084 Keitz, H. A. E. 2 1721696 657084 Ligth calculations and measurements... 5 1721697 657085 La Toison, M. 2 > Does the data in the file look correct for the affected tables? > Are there any other errors being reported? Thats the first error. After that there are similar errores and others related to that register not gentting inserted (foreign keys that don't have there corresponding primary key). --=20 Mart=C3=ADn Marqu=C3=A9s select 'martin.marques' || '@' || 'gmail.com' DBA, Programador, Administrador