Andres Freund <and...@2ndquadrant.com> writes: > On Friday, June 22, 2012 12:23:57 AM Peter Geoghegan wrote: >> Why are you using the stdlib's <assert.h>? Why have you used the >> NDEBUG macro rather than USE_ASSERT_CHECKING? This might make sense if >> the header was intended to live in port, but it isn't, right?
> That should probably be removed, yes. I did it that way that it could be > tested independently of casserts because the list checking code turns some > linear algorithms into quadratic ones which is noticeable even when --enable- > cassert is defined. As far as that goes, I wonder whether the list-checking code hasn't long since served its purpose. Neil Conway put it in when he redid the List API to help catch places that were using no-longer-supported hacks; but it's been years since I've seen it catch anything. I suggest that we might want to either remove it, or enable it via something other than USE_ASSERT_CHECKING (and not enable it by default). regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers