Re: pg_dump problems

El día 23 de marzo de 2011 14:03, Adrian Klaver
<adrian(dot)klaver(at)gmail(dot)com> 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
>> v<C3><A1>lida para tipo bytea
>> CONTEXT:  COPY novedades_fotos, l<C3><AD>nea 273, columna foto:
>>
>> <C2><AB>\377\330\377\340\000\020JFIF\000\001\001\001\000`\000`\000\000\377\341<\310Exif\000\000II
>> *\000\010\0...<C2><BB>
>> psql:siprebi-bu.sql:3477848: ERROR:  la sintaxis de entrada no es
>> v<C3><A1>lida para integer:<C2><AB>q43116<C2><BB>
>> CONTEXT:  COPY objetos, l<C3><AD>nea 99185, columna codigo:
>> <C2><AB>q43116<C2><BB>
>>
>
> 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á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).

--
Martín Marqués
select 'martin.marques' || '@' || 'gmail.com'
DBA, Programador, Administrador