Re: Unable to dump database/table - Mailing list pgsql-bugs

From Andre Maasikas
Subject Re: Unable to dump database/table
Date
Msg-id Pine.LNX.4.50.0410112011150.2890-100000@abbs03xe3.corp.abs.ee
Whole thread Raw
In response to Re: Unable to dump database/table  (Krok <krok@void.ru>)
List pgsql-bugs
On Mon, 11 Oct 2004, Krok wrote:

> void=> select max(length(passwd)) from users;
>      max
> -----------
>   536870919
> (1 row)

....
>
> But how can this happen, that varchar(255) field became broken ?
>
According to my caclulator, in hex this is 0x20000007
so there's likely a bit flip if the length is actually stored
so ( i don't know the internals yet )

I'd be worried about hardware and more importantly about data
consistency at this point. I would suggest running manufacturer's
test suites or something similar on this machine.

(memtest on x86 would be good, copying some .iso's around and
checksumming them in between was a good way for me to ask
a replacement machine once)

Andre

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Why is the index not created in the tablespace delivered in the create-index-command ?
Next
From: Neil Conway
Date:
Subject: Re: PANIC: ERRORDATA_STACK_SIZE exceeded