| From: | Aidan Van Dyk <aidan(at)highrise(dot)ca> |
|---|---|
| To: | Greg Stark <greg(dot)stark(at)enterprisedb(dot)com> |
| Cc: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Block-level CRC checks |
| Date: | 2008-10-17 16:14:08 |
| Message-ID: | 20081017161408.GA16893@yugib.highrise.ca |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Greg Stark <greg(dot)stark(at)enterprisedb(dot)com> [081017 12:05]:
> I'm far from convinced wal logging hint bits is a non starter. In fact
> I doubt the wal log itself I a problem. Having to take the buffer lock
> does suck though.
And remember, you don't even need to WAL all the hint-bit setts:... You
only *need* to get a WAL backup of the block at some *any* point before the
block's written to save from the torn-page on recovery leading to an
inconsistent CRC.
a.
--
Aidan Van Dyk Create like a god,
aidan(at)highrise(dot)ca command like a king,
http://www.highrise.ca/ work like a slave.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-10-17 16:30:31 | Re: Block-level CRC checks |
| Previous Message | Jonah H. Harris | 2008-10-17 16:13:59 | Re: Block-level CRC checks |