Re: Partially corrupted table - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Partially corrupted table
Date
Msg-id 8452.1156860070@sss.pgh.pa.us
Whole thread Raw
In response to Partially corrupted table  ("Filip Hrbek" <filip.hrbek@plz.comstar.cz>)
List pgsql-bugs
"Filip Hrbek" <filip.hrbek@plz.comstar.cz> writes:
> dwhdb=# create temp table t_fct as select * from dwhdata_salemc.fct;
> SELECT

> dwhdb=# create temp table t_fct as select * from dwhdata_salemc.fct;
> server closed the connection unexpectedly
>         This probably means the server terminated abnormally
>         before or while processing the request.
> The connection to the server was lost. Attempting reset: Failed.
> !>

> dwhdb=# create temp table t_fct as select * from dwhdata_salemc.fct;
> ERROR:  row is too big: size 119264, maximum size 8136

> dwhdb=# create temp table t_fct as select * from dwhdata_salemc.fct;
> ERROR:  row is too big: size 38788, maximum size 8136

I think you've got hardware problems.  Getting different answers from
successive scans of the same table is really hard to explain any other
way.  memtest86 and badblocks are commonly suggested for testing memory
and disk respectively on Linux machines.

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Filip Hrbek"
Date:
Subject: Partially corrupted table
Next
From: "Filip Hrbek"
Date:
Subject: Re: Partially corrupted table