Re: pgsql/src/include (config.h.in)
От | Alfred Perlstein |
---|---|
Тема | Re: pgsql/src/include (config.h.in) |
Дата | |
Msg-id | 20001204105217.W8051@fw.wintelcom.net обсуждение исходный текст |
Ответ на | Re: pgsql/src/include (config.h.in) (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-committers |
* Tom Lane <tgl@sss.pgh.pa.us> [001204 08:00] wrote: > Alfred Perlstein <bright@wintelcom.net> writes: > >> I'm going to leave CLOBBER_FREED_MEMORY and MEMORY_CONTEXT_CHECKING > >> turned on by --enable-cassert for now, however. > > > Urk, this looks pretty expensive, is there any flags available that > > will enable the assertion checking without expensive memory zeroing > > (or 0xdeadbeef'ing) free'd memory? > > You can twiddle the declarations in config.h (or config.h.in). > > > Is running enable-cassert on my production boxes going to cause > > a lot of overhead? > > While I haven't tried hard to measure it, the profiles that I've done > don't show it as a huge cost. > > In any case, you're not planning to run beta code as production, > are you? Nope, I'm using 7.0.3, but cassert and debug options have helped us a lot in the past when tracking down bugs. :) It would be helpful to have a extra sanity checking option that doesn't do things like clear large blocks of memory. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk."
В списке pgsql-committers по дате отправления: