Re: parse_oper cache - Mailing list pgsql-hackers

From Robert Haas
Subject Re: parse_oper cache
Date
Msg-id 603c8f070912271329q2a4472f0o3fa06a3a60c92cc8@mail.gmail.com
Whole thread Raw
In response to Re: parse_oper cache  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sun, Dec 27, 2009 at 3:03 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> If we're really doing it, sure.  But putting half of it in
>> TopMemoryContext and the other half in CacheMemoryContext is not
>> obviously of any value.
>
> There isn't any of that stuff that's *in* TopMemoryContext.  Whether the
> hash table contexts are children of TopMemoryContext or
> CacheMemoryContext would be important if we were ever going to reset
> either, but we aren't.  The main point in my mind is that it be possible
> to tell from a memory stats dump how much is being used for what, and we
> do have that.

Oh, I see.  I was thinking that it might matter that the hash table
contexts are descended from TopMemoryContext rather than
CacheMemoryContext, but I guess that doesn't matter very much.

...Robert


pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: Removing pg_migrator limitations
Next
From: Simon Riggs
Date:
Subject: Re: Hot Standy introduced problem with query cancel behavior