| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Markus Wanner <markus(at)bluegap(dot)ch> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Block-level CRC checks |
| Date: | 2008-10-20 19:04:40 |
| Message-ID: | 48FCD648.7000907@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Markus Wanner wrote:
> Alvaro Herrera wrote:
>> So this discussion died with no solution arising to the
>> hint-bit-setting-invalidates-the-CRC problem.
>
> Isn't double-buffering solving this issue? Has somebody checked if it
> even helps performance due to being able to release the lock on the
> buffer *before* the syscall?
Double-buffering helps with the hint bit issues within shared buffers,
but doesn't help with the torn page and hint bits problem. The torn page
problem seems to be the show-stopper.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julius Stroffek | 2008-10-20 19:05:33 | Multi CPU Queries - Feedback and/or suggestions wanted! |
| Previous Message | Joshua Tolley | 2008-10-20 19:00:50 | Re: Lisp as a procedural language? |