From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Aidan Van Dyk <aidan(at)highrise(dot)ca> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Page Checksums |
Date: | 2011-12-19 14:18:21 |
Message-ID: | 20111219141821.GB24234@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Aidan Van Dyk (aidan(at)highrise(dot)ca) wrote:
> #) Anybody investigated putting the CRC in a relation fork, but not
> right in the data block? If the CRC contains a timestamp, and is WAL
> logged before the write, at least on reading a block with a wrong
> checksum, if a warning is emitted, the timestamp could be looked at by
> whoever is reading the warning and know tht the block was written
> shortly before the crash $X $PERIODS ago....
I do like the idea of putting the CRC info in a relation fork, if it can
be made to work decently, as we might be able to then support it on a
per-relation basis, and maybe even avoid the on-disk format change..
Of course, I'm sure there's all kinds of problems with that approach,
but it might be worth some thinking about.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2011-12-19 14:31:17 | Re: Command Triggers |
Previous Message | Stephen Frost | 2011-12-19 14:14:09 | Re: Page Checksums |