On Wed, Jan 6, 2010 at 6:11 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 3. Invoking tablespace_reloptions while switched into
> CacheMemoryContext.  This isn't a crasher, but it strikes me as a bad
> idea because if reloptions.c happens to leak anything, that'll represent
> a permanent (session-lifespan) memory leak.  And it's complicated enough
> that being sure it doesn't leak anything is hard.

What tools do we have for identifying memory leaks?

> I think you should
> invoke tablespace_reloptions in the caller's memory context, and then if
> it succeeds, copy the result into CacheMemoryContext.  That would
> probably require fixing the problem you noted earlier today about
> making TableSpaceOpts be a valid bytea value, so that it'll be easy to
> copy (then you can use datumCopy, for instance).

I think I'll just copy Alvaro's existing pattern in relcache.c, which
just uses palloc0 and memcpy.

...Robert

In response to

• Re: [COMMITTERS] pgsql: Support ALTER TABLESPACE name SET/RESET ( tablespace_options ). at 2010-01-06 23:11:39 from Tom Lane

Responses

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

pgsql-hackers by date

Next:	From: Kevin Grittner	Date: 2010-01-07 03:00:30
	Subject: Re: Testing with concurrent sessions
Previous:	From: Robert Haas	Date: 2010-01-07 02:49:38
	Subject: Re: Testing with concurrent sessions

pgsql-committers by date

Next:	From: Tom Lane	Date: 2010-01-07 03:13:44
	Subject: Re: [COMMITTERS] pgsql: Support ALTER TABLESPACE name SET/RESET ( tablespace_options ).
Previous:	From: Robert Haas	Date: 2010-01-07 02:41:16
	Subject: pgsql: Improve a couple of comments relating to large object snapshot