Re: Misc. consequences of backend memory management changes
От | Peter Eisentraut |
---|---|
Тема | Re: Misc. consequences of backend memory management changes |
Дата | |
Msg-id | Pine.LNX.4.21.0006282050420.360-100000@localhost.localdomain обсуждение исходный текст |
Ответ на | Misc. consequences of backend memory management changes (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Misc. consequences of backend memory management changes
|
Список | pgsql-hackers |
Tom Lane writes: > Will anyone object if I make CLOBBER_FREED_MEMORY defined by default > until 7.1 release is near? > To help catch such problems sooner, it'd be a good idea to have > conditionally-compiled test code that forces *every* generated parse > and plan tree to be passed through copyObject(). Again, I propose > setting up config.h symbols for this and turning them on by default > during the 7.1 development phase. I've been thinking that we need a configure option for this sort of stuff, like --enable-debug=memory,lock,foo,noipc which would result in #define MEMORY_DEBUG 1 #define LOCK_DEBUG 1 #define FOO_DEBUG 1 #undef IPC_DEBUG Comments? -- Peter Eisentraut Sernanders väg 10:115 peter_e@gmx.net 75262 Uppsala http://yi.org/peter-e/ Sweden
В списке pgsql-hackers по дате отправления: