On Wed, Jan 6, 2010 at 10:13 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> What tools do we have for identifying memory leaks?
>
> User complaints :-(

YGTBFKM.

It seems like we should have a tool that dumps out every memory
context in the system, with the number of allocations and frees and
number of bytes allocated and freed since the last reset.  Maybe the
time of the last reset.  You could run that before and after doing
whatever it is that might leak and compare.

...Robert

In response to

• Re: [COMMITTERS] pgsql: Support ALTER TABLESPACE name SET/RESET ( tablespace_options ). at 2010-01-07 03:13:44 from Tom Lane

Responses

• Re: [COMMITTERS] pgsql: Support ALTER TABLESPACE name SET/RESET ( tablespace_options ). at 2010-01-07 04:14:42 from Tom Lane

pgsql-hackers by date

Next:	From: Robert Haas	Date: 2010-01-07 03:43:11
	Subject: Re: Testing with concurrent sessions
Previous:	From: Tom Lane	Date: 2010-01-07 03:13:44
	Subject: Re: [COMMITTERS] pgsql: Support ALTER TABLESPACE name SET/RESET ( tablespace_options ).

pgsql-committers by date

Next:	From: Bruce Momjian	Date: 2010-01-07 03:41:41
	Subject: Re: pgsql: PG_MAJORVERSION: For simplicity, use PG_MAJORVERSION rather than
Previous:	From: Tom Lane	Date: 2010-01-07 03:24:57
	Subject: pgsql: Fail in a nicer way if we have --with-perl and no Perl.