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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-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 | Content-Type | Size |
---|---|---|
wal_checksum.v2.patch | text/x-patch | 8.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-01-04 17:58:37 | Re: Small vcbuild patch |
Previous Message | Andrew Dunstan | 2007-01-04 17:24:10 | Re: 8.3 pending patch queue |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-01-04 17:58:37 | Re: Small vcbuild patch |
Previous Message | Tom Lane | 2007-01-04 17:13:57 | Re: [HACKERS] wal_checksum = on (default) | off |