From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | Peter Geoghegan <peter(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH 04/16] Add embedded list interface (header only) |
Date: | 2012-06-22 14:18:35 |
Message-ID: | 10731.1340374715@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2012-06-22 14:19:22 | Re: [PATCH 01/16] Overhaul walsender wakeup handling |
Previous Message | Robert Haas | 2012-06-22 14:12:58 | Re: [PATCH] Lazy hashaggregate when no aggregation is needed |