Re: simple update closes connection. why? - Mailing list pgsql-novice

From Tom Lane
Subject Re: simple update closes connection. why?
Date
Msg-id 2345.1075671314@sss.pgh.pa.us
Whole thread Raw
In response to Re: simple update closes connection. why?  (joseph speigle <joe.speigle@jklh.us>)
Responses Re: simple update closes connection. why?
List pgsql-novice
joseph speigle <joe.speigle@jklh.us> writes:
> okay.  I"m making progress here.  :)   I want to know if I should just delete the oid that's too very large?
> because, I can issue a select up to row 1100.  So, Select * from calling limit 1100 returns all rows, whereas
> select * from calling limit 1101 kills the process.

Okay, so you have a corrupted tuple --- from the evidence so far I'd
guess that the length word of the first column in that row is clobbered.
The wacky OIDs in some of the other rows look like data corruption too.

At this point my thoughts are heading in the direction of hardware
problems.  Have you tried running any memory or disk diagnostics?
memtest86 and badblocks seem to be the most widely used tests.

            regards, tom lane

pgsql-novice by date:

Previous
From: joseph speigle
Date:
Subject: Re: simple update closes connection. why?
Next
From: joseph speigle
Date:
Subject: Re: simple update closes connection. why?