Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id EE5841337BD5 for ; Wed, 23 Mar 2011 14:38:44 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 23699-01-2 for ; Wed, 23 Mar 2011 17:38:34 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-pz0-f46.google.com (mail-pz0-f46.google.com [209.85.210.46]) by mail.postgresql.org (Postfix) with ESMTP id 0DB1A1337BF1 for ; Wed, 23 Mar 2011 14:38:20 -0300 (ADT) Received: by pzk9 with SMTP id 9so1056631pzk.19 for ; Wed, 23 Mar 2011 10:38:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=JSLO5/qA6G7+AkIWfwF73rCRqoLMdB/Dvpkl5Pv6o5Q=; b=tqv7O/bxxLttp+yeaaDlL3DpS7ph9xugTu36ZJRbkl/OcVLxpbF/hbHfLOjImjqyPH GhZMCHG/SAG32DkfMZeKklIuQKXrewafi93nuBNezokLcNu3BqTkMLPCjMnIgEWYmQzb /qtHkfqeUImWYs/ugKftTJ6gPkeJ7B1tTJ/UA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=EBYUmFEbHGI25urLmiyVg8sVmFI/MgsNIWtAjj3IZAnuYMTJFnxB4ksD1+/8PCKWWY Uby/geogNFsQWi4ZdDIKifB4yjaTvftXCeGSHMIeldVnZMCuUR7ugnWEVn3sUufnrlP7 uVq10edxIjet5cDhH9YbabJaLMgZFxmdeRO7U= Received: by 10.142.231.11 with SMTP id d11mr5439614wfh.35.1300901900284; Wed, 23 Mar 2011 10:38:20 -0700 (PDT) Received: from [192.168.0.109] (c-24-17-179-185.hsd1.wa.comcast.net [24.17.179.185]) by mx.google.com with ESMTPS id d35sm10331448wfj.9.2011.03.23.10.38.19 (version=SSLv3 cipher=OTHER); Wed, 23 Mar 2011 10:38:19 -0700 (PDT) Message-ID: <4D8A300A.90105@gmail.com> Date: Wed, 23 Mar 2011 10:38:18 -0700 From: Adrian Klaver User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: =?UTF-8?B?TWFydMOtbiBNYXJxdcOpcw==?= CC: pgsql-general@postgresql.org, Vick Khera Subject: Re: pg_dump problems References: <201103230718.40361.adrian.klaver@gmail.com> <4D8A27DB.70702@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.899 tagged_above=-5 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001 X-Spam-Level: X-Archive-Number: 201103/833 X-Sequence-Number: 174094 On 03/23/2011 10:33 AM, Martín Marqués wrote: > El día 23 de marzo de 2011 14:03, Adrian Klaver > escribió: >> On 03/23/2011 07:56 AM, Martín Marqués 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: sintaxis de entrada no >>> vlida para tipo bytea >>> CONTEXT: COPY novedades_fotos, lnea 273, columna foto: >>> >>> \377\330\377\340\000\020JFIF\000\001\001\001\000`\000`\000\000\377\341<\310Exif\000\000II >>> *\000\010\0... >>> psql:siprebi-bu.sql:3477848: ERROR: la sintaxis de entrada no es >>> vlida para integer:q43116 >>> CONTEXT: COPY 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. One way would be to dump only the table(s) that are causing the problem. > > The second error is very curious, as it looks like pg_dump changed 1 > for a 'q' in an integer field: My guess is that it is combining data from two fields. In other words the 'q' is the end of the previous field. > > psql:siprebi-bu.sql:2219245: ERROR: la sintaxis de entrada no es > válida para integer: «q721695» > CONTEXT: COPY objeto_datos_rep, línea 991894, columna codigo: «q721695» > > 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). > -- Adrian Klaver adrian.klaver@gmail.com