Pavan Deolasee wrote:
> Are we leaking memory in vac_update_relstats ?
> /* Fetch a copy of the tuple to scribble on */
> ctup = SearchSysCacheCopy(RELOID,
> 0, 0, 0);
> This copy is not subsequently freed in the function.
It's palloc'd in the current memory context, so it's not serious. It'll
be freed at the end of the transaction, if not before that. That's the
beauty of memory contexts; no need to worry about small allocations like
In response to
pgsql-hackers by date
|Next:||From: NikhilS||Date: 2007-07-20 10:17:46|
|Subject: Re: Memory leak in vac_update_relstats ?|
|Previous:||From: Pavan Deolasee||Date: 2007-07-20 09:16:18|
|Subject: Memory leak in vac_update_relstats ?|