On 3/4/13 2:48 PM, Jeff Davis wrote:
On Mon, 2013-03-04 at 13:58 -0500, Greg Smith wrote:
>On 3/4/13 2:11 AM, Simon Riggs wrote:
> >It's crunch time. Do you and Jeff believe this patch should be
> >committed to Postgres core?
>
>I want to see a GUC to allow turning this off, to avoid the problem I
>saw where a non-critical header corruption problem can cause an entire
>page to be unreadable. A variation on that capable of turning this off
>altogether, as Craig suggested, is a good idea too.
Based on your comments as well those of Dan and Craig, I am leaning
toward a GUC that causes a checksum failure to be ignored. It will still
emit the checksum failure warning, but proceed.
I suggest we paint that GUC along the lines of "checksum_failure_log_level",
defaulting to ERROR. That way if someone wanted completely bury the elogs to like DEBUG
they could.
My $2.98 (inflation adjusted).
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
