Re: shall we have a TRACE_MEMORY mode - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: shall we have a TRACE_MEMORY mode
Date
Msg-id 1150793555.2587.138.camel@localhost.localdomain
Whole thread Raw
In response to Re: shall we have a TRACE_MEMORY mode  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: shall we have a TRACE_MEMORY mode  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
On Tue, 2006-06-20 at 00:18 -0400, Tom Lane wrote:

> One idea that comes to mind is to have a compile time option to record
> the palloc __FILE__ and _LINE__ in every AllocChunk header.  Then it
> would not be so hard to identify the culprit while trawling through
> memory.  The overhead costs would be so high that you'd never turn it on
> by default though :-(

Could we set that as an option for each memory context when we create
it? All or nothing seems too extreme for me for most cases.

--  Simon Riggs EnterpriseDB          http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: sync_file_range()
Next
From: Simon Riggs
Date:
Subject: Re: Generic Monitoring Framework Proposal