Re: Reviewing freeze map code - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: Reviewing freeze map code
Date
Msg-id 1e78ce70-db1e-e639-f758-dc202f56ab5e@BlueTreble.com
Whole thread Raw
In response to Re: Reviewing freeze map code  (Peter Geoghegan <pg@heroku.com>)
Responses Re: Reviewing freeze map code  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
On 5/6/16 4:55 PM, Peter Geoghegan wrote:
> On Fri, May 6, 2016 at 2:49 PM, Andres Freund <andres@anarazel.de> wrote:
>>> Jeff Janes has done astounding work in these matters.  (I don't think
>>> we credit him enough for that.)
>>
>> +many.
>
> Agreed. I'm a huge fan of what Jeff has been able to do in this area.
> I often say so. It would be even better if Jeff's approach to testing
> was followed as an example by other people, but I wouldn't bet on it
> ever happening. It requires real persistence and deep understanding to
> do well.

It takes deep understanding to *design* the tests, not to write them. 
There's a lot of folks out there that will never understand enough to 
design tests meant to expose data corruption but who could easily code 
someone else's design, especially if we provided tools/ways to tweak a 
cluster to make testing easier/faster (such as artificially advancing 
XID/MXID).
-- 
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)   mobile: 512-569-9461



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: Reviewing freeze map code
Next
From: Jim Nasby
Date:
Subject: Re: Reviewing freeze map code