From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Jacek Rembisz" <jacek(dot)rembisz(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: a question about data corruption |
Date: | 2008-06-26 00:24:59 |
Message-ID: | 25759.1214439899@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Jacek Rembisz" <jacek(dot)rembisz(at)gmail(dot)com> writes:
> Postgresql started to log "could not access status of transaction"
> messages. Since the transaction IDs were far away from what
> server was using I took a look at data files i pgsql/base/ and I found
> a total garbage there.
> In five tables (of about 100) I have found a one to four blocks of random data.
> In two places it was data from other table instead of random data.
> All these blocks have sizes which are multiplications of 512 (for
> example 1, 9, 26) and
> starts at offsets which are also a multiplication of 512.
Substituting sector-size blocks of one file for another could easily
be a filesystem (kernel) bug ...
> The system is linux 2.4.31 filesystem XFS on RAID5
... and XFS on such an old kernel version doesn't seem like a very
good bet for stability.
> My question is: Is there any known bug in postgresql 8.0.3 that
> could lead to such a data corruption or is it rather a hardware problem?
No, nothing like that has ever been reported in any released PG
version. If the substituted blocks were from non-Postgres files
then I think you could write off the idea of a PG bug entirely.
It could still be a software issue though.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2008-06-26 02:12:44 | Re: ERROR: could not open relation with OID 2836 |
Previous Message | Richard Broersma | 2008-06-25 23:08:46 | IF ROW( NEW ) <> ROW( OLD ) |