On Thu, May 22, 2014 at 5:00 PM, Alvaro Herrera <alvhe...@2ndquadrant.com> wrote: > Andres Freund wrote: >> On 2014-05-22 16:37:35 -0400, Tom Lane wrote: >> > We could do that ... but I wonder if we shouldn't remove assert_enabled >> > altogether. What's the use case for turning it off? Not matching the >> > speed of a non-cassert build, because for instance MEMORY_CONTEXT_CHECKING >> > doesn't get turned off. >> >> I've used it once or twice to avoid having to recompile postgres when I >> wanted things not to be *that* slow (AtEOXactBuffers() I am looking at >> you). But I wouldn't be very sad if it'd go. >> >> Anybody against that? > > I have used it too (for a different reason IIRC), but like you I > wouldn't have a problem if it weren't there.
I've used it, too, although not recently. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
