Cost of AtEOXact_Buffers in --enable-cassert - Mailing list pgsql-hackers

From Andres Freund
Subject Cost of AtEOXact_Buffers in --enable-cassert
Date
Msg-id 201008061950.56950.andres@anarazel.de
Whole thread Raw
Responses Re: Cost of AtEOXact_Buffers in --enable-cassert  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Cost of AtEOXact_Buffers in --enable-cassert  (Greg Smith <greg@2ndquadrant.com>)
List pgsql-hackers
Hi,

I do test (and even run) some stuff running with cassert enabled. For many 
things the reliability and performance is ok enough and its useful, especially 
if you have your own c functions and such.
Imho thats useful as it makes catching some bugs more likely...

The most prohibitively expensive part is the AtEOXact_Buffers check of running 
through all buffers and checking their pin count. And it makes $app's 
regression tests take thrice their time...

Would somebody object agains putting those in an extra define so that those can 
be disabled in pg_config_manual? Or even disable it by default entirely...

Andres


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Initial review of xslt with no limits patch
Next
From: Tom Lane
Date:
Subject: Re: Initial review of xslt with no limits patch