Re: Bug in batch tuplesort memory CLUSTER case (9.6 only) - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: Bug in batch tuplesort memory CLUSTER case (9.6 only)
Date
Msg-id 43b82d9a-b74c-6556-5e5d-0bf72a5c745e@BlueTreble.com
Whole thread Raw
In response to Re: Bug in batch tuplesort memory CLUSTER case (9.6 only)  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
On 7/2/16 12:40 AM, Peter Geoghegan wrote:
> We should be more ambitious about adding test coverage to tuplesort.c.

IMHO, s/ to tuplesort.c//, at least for the buildfarm.

TAP tests don't run by default, so maybe that's the place to start 
"going crazy" with adding more testing. Though I do think something 
that's sorely needed is the ability to test stuff at the C level. 
Sometimes SQL is jut too high a level to verify things.
-- 
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: Victor Giannakouris - Salalidis
Date:
Subject: Statistics Injection
Next
From: Christoph Berg
Date:
Subject: Re: Broken handling of lwlocknames.h