| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Robert Mach <mach(dot)robert(at)gmail(dot)com> |
| Subject: | Re: Proposal: Integrity check |
| Date: | 2008-01-25 18:54:36 |
| Message-ID: | 3479.1201287276@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> writes:
> Tom Lane wrote:
>> This seems like a pretty horrid idea. Bad pages shouldn't be allowed to
>> get into shared buffers in the first place. Why not have the checking
>> logic operate outside shared buffers?
> It currently works outside the shared buffers, but I afraid about
> collision due to parallel read and write access on one block. I'm not
> sure if parallel write(8k) and read(8k) is synchronized by kernel/fs or
> not. If not it should generates false positive results. If yes than I'm
> happy :-) with outside processing.
We're already assuming that; otherwise base backups for PITR don't work.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-01-25 19:00:50 | Re: Truncate Triggers |
| Previous Message | Simon Riggs | 2008-01-25 18:50:15 | Re: Truncate Triggers |