From: | Martín Marqués <martin(dot)marques(at)gmail(dot)com> |
---|---|
To: | Vick Khera <vivek(at)khera(dot)org> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_dump problems |
Date: | 2011-03-30 14:40:03 |
Message-ID: | AANLkTinN=XV=Hv2wOHD36srouTMcrisKjb1r6fKp90JY@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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(dot)marques(at)gmail(dot)com> escribió:
> 2011/3/23 Vick Khera <vivek(at)khera(dot)org>:
>> 2011/3/23 Martín Marqués <martin(dot)marques(at)gmail(dot)com>:
>>> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Sabino Mullane | 2011-03-30 15:29:25 | DBD::Pg 2.18.0 released |
Previous Message | Dmitriy Igrishin | 2011-03-30 13:43:21 | Re: Stange IO error while working with large objects. |