From: | Junwang Zhao <zhjwpku(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: replace magic num in struct cachedesc with CATCACHE_MAXKEYS |
Date: | 2024-08-24 02:01:37 |
Message-ID: | CAEG8a3+Ee5=gsXtJ9CpN96o7NNSCcqChMGnU1asHDyVn=BGbHA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Aug 23, 2024 at 9:02 PM Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
>
> On 15.08.24 12:25, Junwang Zhao wrote:
> > I noticed that there is a magic number which can be replaced by CATCACHE_MAXKEYS
> > in struct cachedesc, I checked some other struct like CatCache, CatCTup, they
> > all use CATCACHE_MAXKEYS.
>
> The "syscache" is the only user of the "catcache" right now. But I
> think they are formally separate. So I don't think the "4" in the
> syscache is necessarily the same as CATCACHE_MAXKEYS. For example,
> increasing CATCACHE_MAXKEYS, hypothetically, wouldn't by itself make the
> syscache support more than 4 keys.
Thanks for your explanation.
CF status changed to withdrawn.
--
Regards
Junwang Zhao
From | Date | Subject | |
---|---|---|---|
Next Message | shawn wang | 2024-08-24 02:26:41 | Re: Trim the heap free memory |
Previous Message | Joel Jacobson | 2024-08-23 23:35:21 | Re: Optimising numeric division |