From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: parse_oper cache |
Date: | 2009-12-27 21:29:28 |
Message-ID: | 603c8f070912271329q2a4472f0o3fa06a3a60c92cc8@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Dec 27, 2009 at 3:03 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2009-12-27 21:42:47 | Re: Hot Standy introduced problem with query cancel behavior |
Previous Message | Greg Stark | 2009-12-27 20:35:37 | Re: Removing pg_migrator limitations |