Re: Misc. consequences of backend memory management changes

Peter Eisentraut <peter_e@gmx.net>

From: Peter Eisentraut <peter_e@gmx.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Development <pgsql-hackers@postgresql.org>
Date: 2000-06-29T17:27:33Z
Lists: 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