| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Melih Mutlu <m(dot)melihmutlu(at)gmail(dot)com> |
| Cc: | Rahila Syed <rahilasyed90(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>, andres(at)anarazel(dot)de, vignesh C <vignesh21(at)gmail(dot)com> |
| Subject: | Re: Separate memory contexts for relcache and catcache |
| Date: | 2024-12-11 00:27:03 |
| Message-ID: | Z1jcV7fmlc8U2m2H@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Nov 26, 2024 at 05:11:16PM +0300, Melih Mutlu wrote:
> That said, these changes come with a cost, and it may not be worth it to
> separate every single cache into its own context. IIUC, introducing
> contexts for heavily used caches results in much less fragmentation. If
> that’s the case, then I believe we should focus on RelCache and CatCache,
> as they are heavily used since the backend starts. I see that you and
> Ashutosh [2] mentioned that PlanCacheContext is less likely to be heavily
> used, so we could consider leaving that context out for now.
Looking at the tail of this thread, some feedback has been provided.
These are not that easy to look at, so I've marked the patch as
returned with feedback for now, and there were a few concerns raised
as well. Feel free to adjust as you feel if you think this is not
adapted.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2024-12-11 00:34:40 | Re: Serverside SNI support in libpq |
| Previous Message | Michael Paquier | 2024-12-11 00:22:06 | Re: Expand applicability of aggregate's sortop optimization |