Thanks. I am running this on 1 year old hardware on a wholly-encrypted C
drive, encrypted with TrueCrypt. I suspect that I would have been alerted
already with that or SMART if I had hardware issues?
I am on 9.1.3, although I think the data was inserted back when I was
running 9.0.x. I upgraded to 9.1 almost as soon as it came out, doing the
requisite dumps and reloads. I have also reindexed a couple of times as
diagnostic steps.
So far, looks like only that one row has data corruption.
Aren
On Sun, Mar 18, 2012 at 9:33 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Aren Cambre <aren@arencambre.com> writes:
> > Just want to again emphasize that my database state has changed, so I am
> > not sure this is remains a good case for finding a bug.
>
> Your description of an apparently-all-nulls row sounds a great deal like
> data corruption. I suspect there may be more wrong than just the one
> row, and that that's what's leading to the inconsistent results. It'd
> be worthwhile to run hardware diagnostics (memtest, disk tests), make
> sure you are on the latest minor release of Postgres, and perhaps do a
> database dump and reload. (If the latter seems impractical, at least
> consider reindexing everything.)
>
> regards, tom lane
>