Marc Schablewski wrote:
If pages with bogus data but correct checksum are ever found on disk, I think this would prove that there is no hardware / file system / os issue.
No, it would only suggest that the issue is not in the filesystem or I/O subsystem. Even then, it wouldn't catch bugs where the contents of one block are copied over or swapped with another block. The checksum would be calculated when a page is written to disk, so the corruption could still be caused by faulty memory, memory bus, CPU or OS, while the page sits in the buffer cache.
If an access violation resulting from writes to locked pages were hit, would it be possible to log a stack backtrace?
I think you'd get a segmentation fault. With a core dump if the system is configured so.
Question: Who is responsible for maintaining this part (buffer cache maintenance, writer etc) of postgres code?
There's no named individuals, just the community in general. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
