Skip site navigation (1) Skip section navigation (2)

Re: Misc. consequences of backend memory management changes

From: Chris Bitmead <chris(at)bitmead(dot)com>
To: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Misc. consequences of backend memory management changes
Date: 2000-07-01 04:04:19
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Tom Lane wrote:

> 2. Currently there is some code in aset.c that arranges to wipe
> freed space immediately upon its being freed, as an aid in detecting
> attempted uses of already-freed objects.  It's conditionally compiled
> based on "#ifdef CLOBBER_FREED_MEMORY", which ought to be mentioned
> in (but isn't yet).  This slows things down a little bit
> so I wouldn't recommend having it turned on for production use, but
> I think it would be a good idea to keep it turned on during the
> development and early beta phases of 7.1.  With the memory
> management changes I think we will be at increased risk of having
> use-of-freed-memory bugs, so I'd like to get as much testing as
> possible done with this code enabled.  Will anyone object if I make
> CLOBBER_FREED_MEMORY defined by default until 7.1 release is near?

Could we instead have some configure option --devel or something that
turns on all the checks?

In response to

pgsql-hackers by date

Next:From: The Hermit HackerDate: 2000-07-01 04:06:16
Subject: Re: Built with PostgreSQL (images)
Previous:From: Chris BitmeadDate: 2000-07-01 03:59:26
Subject: Re: Big 7.1 open items

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group