Just to to finish this thread: We had a corrupted memory bank in the development server, and that was, for some reason corrupting the data that got written to disk. All is good now. Sorry for the noise. El dÃa 23 de marzo de 2011 16:28, MartÃn MarquÃs <martin.marques@xxxxxxxxx> escribiÃ: > 2011/3/23 Vick Khera <vivek@xxxxxxxxx>: >> 2011/3/23 MartÃn MarquÃs <martin.marques@xxxxxxxxx>: >>> 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Â >>> >> >> That's a single-bit error. ÂI'm voting hardware problems. ÂDoes your >> memory have ECC? ÂHow reliable is your disk? >> > > The production server is a Compaq Prolaint, with ECC memory and RAID > by hardware. > > How can I discard, or affirm that we are dealing with hardware problems? > > -- > MartÃn MarquÃs > select 'martin.marques' || '@' || 'gmail.com' > DBA, Programador, Administrador > -- MartÃn MarquÃs select 'martin.marques' || '@' || 'gmail.com' DBA, Programador, Administrador -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
