Craig Ringer writes:
> [ long summary of all the weird and wonderful ways things can break ]
> ... unless an event is noticed that is associated with the corruption, or
> some way to reproduce it is found, there's no way to tell whether any
> given incident could be a rarely triggered Pg bug (ie:
Craig Ringer wrote:
> PostgreSQL has to trust the hardware and the OS to do their jobs. If the
> OS is, unbeknownst to PostgreSQL, flipping the high bit in any byte
Might not even be the OS - it could be the stars (through cosmic rays).
http://www.eetimes.com/news/98/1012news/ibm.html
'"This cl
postgres bee wrote:
> Correct me if I am wrong, but I thought one of the, if not the most, primary
> tasks for relational databases is to ensure that no data loss ever occurs.
> Which is why I was initially surprised that the issue did not get enough
> importnace. But now it seems more like the
postgres bee writes:
> But I do have one overriding question - since postgres is still running on
> the same hardware, wouldn't it rule out hardware as the primary suspect?
Uh, no. One of the principal characteristics of hardware problems is
that they're intermittent. (When they're not, you ha
> Was there any particular event that marked the onset of these issues?
> Anything in the system logs (dmesg / syslog etc) around that time?
Unfortunately, cannot recall anything abnormal.
> Was Pg forcibly killed and restarted, or the machine hard-reset? (This
> _shouldn't_ cause data corrupti
On Mon, 2009-09-14 at 22:58 -0700, John R Pierce wrote:
> and, if you're doing RAID with desktop grade disks, its quite possible
> for the drive to spontaneously decide a sector error requires a data
> relocation but not have the 'good' data to relocate, and not return an
> error code in time f
Craig Ringer wrote:
[for SATA disks]: does smartctl from the smartmontools package indicate
anything interesting about the disk(s)? (Ignore the "health status",
it's a foul lie, and rely on the error log plus the vendor attributes:
reallocated sector count, pending sector, uncorrectable sector co
On Mon, 2009-09-14 at 23:17 +, john martin wrote:
> All of a sudden we started seeing page header errors in certain queries.
Was there any particular event that marked the onset of these issues?
Anything in the system logs (dmesg / syslog etc) around that time?
[for SATA disks]: does smartc
