Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] wal_checksum = on (default) | off

From: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>,<pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] wal_checksum = on (default) | off
Date: 2007-01-04 17:53:44
Message-ID: 1167933225.20749.216.camel@silverbirch.site (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
On Thu, 2007-01-04 at 12:13 -0500, Tom Lane wrote:
> "Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> > On Thu, 2007-01-04 at 11:09 -0500, Tom Lane wrote:
> >> "It works most of the time" doesn't exactly satisfy me.
> 
> > It seemed safer to allow a very rare error through to the next level of
> > error checking rather than to close the door so tight that recovery
> > would not be possible in a very rare case.
> 
> If a DBA is turning checksums off at all, he's already bought into the
> assumption that he's prepared to recover from backups.  What you don't
> seem to get here is that this "feature" is pretty darn questionable in
> the first place, and for it to have a side effect of poking a hole in
> the system's reliability even when it's off is more than enough to get
> it rejected outright.  It's just a No Sale.

I get it, and I listened. I'm was/am happy to do it the way you
suggested; I was merely explaining that I had considered the issue.

New patch enclosed.

-- 
  Simon Riggs             
  EnterpriseDB   http://www.enterprisedb.com


Attachment: wal_checksum.v2.patch
Description: text/x-patch (8.6 KB)

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2007-01-04 17:58:37
Subject: Re: Small vcbuild patch
Previous:From: Andrew DunstanDate: 2007-01-04 17:24:10
Subject: Re: 8.3 pending patch queue

pgsql-patches by date

Next:From: Tom LaneDate: 2007-01-04 17:58:37
Subject: Re: Small vcbuild patch
Previous:From: Tom LaneDate: 2007-01-04 17:13:57
Subject: Re: [HACKERS] wal_checksum = on (default) | off

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group