Re: [HACKERS] Checksums by default? - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: [HACKERS] Checksums by default?
Date
Msg-id 4f410482-7b2a-05ed-681e-bd27bf24cc63@BlueTreble.com
Whole thread Raw
In response to Re: [HACKERS] Checksums by default?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 1/23/17 8:24 PM, Tom Lane wrote:
> Jim Nasby <Jim.Nasby@bluetreble.com> writes:
>> On 1/23/17 7:47 PM, Stephen Frost wrote:
>>> It might be interesting to consider checking them in 'clean' pages in
>>> shared_buffers in a background process, as that, presumably, *would*
>>> detect shared buffers corruption.
>
>> Hmm... that would be interesting. Assuming the necessary functions are
>> exposed it presumably wouldn't be difficult to do that in an extension,
>> as a bgworker.
>
> But we don't maintain the checksum of a page while it sits in shared
> buffers.  Trying to do so would break, eg, concurrent hint-bit updates.

Hrm, I thought the checksum would be valid if the buffer is marked clean?
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Checksums by default?
Next
From: Stephen Frost
Date:
Subject: Re: [HACKERS] Checksums by default?