Re: Enabling Checksums - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: Enabling Checksums
Date
Msg-id 514D2EF3.9050904@nasby.net
Whole thread Raw
In response to Re: Enabling Checksums  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On 3/18/13 2:25 PM, Simon Riggs wrote:
> On 18 March 2013 19:02, Jeff Davis <pgsql@j-davis.com> wrote:
>> On Sun, 2013-03-17 at 22:26 -0700, Daniel Farina wrote:
>>> as long as I am able to turn them off easily
>>
>> To be clear: you don't get the performance back by doing
>> "ignore_checksum_failure = on". You only get around the error itself,
>> which allows you to dump/reload the good data.
>
> Given that the worst pain point comes from setting hint bits during a
> large SELECT, it makes sense to offer an option to simply skip hint
> bit setting when we are reading data (SELECT, not
> INSERT/UPDATE/DELETE). That seems like a useful option even without
> checksums. I know I have seen cases across many releases where setting
> that would have been good, since it puts the cleanup back onto
> VACUUM/writers, rather than occasional SELECTs.

+1



pgsql-hackers by date:

Previous
From: Josh Kupershmidt
Date:
Subject: Re: pg_dump/restore syntax checking bug?
Next
From: Jim Nasby
Date:
Subject: Re: Let's invent a function to report lock-wait-blocking PIDs