Cost of AtEOXact_Buffers in --enable-cassert

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Cost of AtEOXact_Buffers in --enable-cassert
Date: 2010-08-06 17:50:56
Message-ID: 201008061950.56950.andres@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-08-06 17:52:08 Re: Initial review of xslt with no limits patch
Previous Message Robert Haas 2010-08-06 17:50:08 Re: including backend ID in relpath of temp rels - updated patch