On 1/24/15 3:31 PM, Tom Lane wrote:
Another idea is to teach Valgrind that whenever a backend reduces its pin count on a shared buffer to zero, that buffer should become undefined memory.
<paranoia> Shouldn't this technically tie in with ResourceOwners? If a pointer takes the pin count from 1 to 2, then that pointer should be invalid by the time the pin count goes from 2 to 1... I'm worried that a simple test when pin count is 0 could miss some cases of pointers just happening to be cleared by a second part of the code even though the pin count has already dropped. -- Jim Nasby, Data Architect, Blue Treble Consulting Data in Trouble? Get it in Treble! http://BlueTreble.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
