| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | "James Pang (chaolpan)" <chaolpan(at)cisco(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: thousands of CachedPlan entry per backend |
| Date: | 2023-06-02 19:17:13 |
| Message-ID: | CAMkU=1ykgN2=DeNZxKQSW6yg3h4+PfCyf_3n3pqjhiM7PK4dVQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, Jun 1, 2023 at 4:51 AM James Pang (chaolpan) <chaolpan(at)cisco(dot)com>
wrote:
> 2) from this line, we saw total 42 blocks ,215 chunks
> CacheMemoryContext: 8737352 total in 42 blocks; 1021944 free (215 chunks);
> 7715408 used,
>
> But from sum of it’s child level entrys, total sum(child lines)
> block ,trunks show much more than “CacheMemoryContext, is expected to see
> that?
>
Yes, that is expected. The parent context reports only its own direct
memory usage and blocks. It does not include the sum of memory usage of
its child contexts.
Cheers,
Jeff
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Satalabaha Postgres | 2023-06-03 07:18:37 | Understand time taken by individual SQL statements in a procedure |
| Previous Message | James Pang (chaolpan) | 2023-06-02 09:06:12 | RE: thousands of CachedPlan entry per backend |