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

Re: [COMMITTERS] pgsql: Support ALTER TABLESPACE name SET/RESET ( tablespace_options ).

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Support ALTER TABLESPACE name SET/RESET ( tablespace_options ).
Date: 2010-01-07 03:37:10
Message-ID: 603c8f071001061937x49b402d3i86345baf4db22a54@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
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

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2010-01-07 03:43:11
Subject: Re: Testing with concurrent sessions
Previous:From: Tom LaneDate: 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 MomjianDate: 2010-01-07 03:41:41
Subject: Re: pgsql: PG_MAJORVERSION: For simplicity, use PG_MAJORVERSION rather than
Previous:From: Tom LaneDate: 2010-01-07 03:24:57
Subject: pgsql: Fail in a nicer way if we have --with-perl and no Perl.

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