Re: Partially corrupted table

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Filip Hrbek" <filip(dot)hrbek(at)plz(dot)comstar(dot)cz>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Partially corrupted table
Date: 2006-08-29 14:01:10
Message-ID: 8452.1156860070@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Filip Hrbek" <filip(dot)hrbek(at)plz(dot)comstar(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Teodor Sigaev 2006-08-29 14:16:14 Re: BUG #2594: Gin Indexes cause server to crash on Windows
Previous Message Tom Lane 2006-08-29 13:44:55 Re: BUG #2594: Gin Indexes cause server to crash on Windows