From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
---|---|
To: | "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru> |
Cc: | Yura Sokolov <y(dot)sokolov(at)postgrespro(dot)ru>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Subject: | Re: Fix bank selection logic in SLRU |
Date: | 2024-12-10 13:58:29 |
Message-ID: | CAFiTN-uZXxsnZu5OGNqpP137pzv2yB0u0kSdZiPHkWUA9epDQQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 10 Dec 2024 at 7:24 PM, Andrey M. Borodin <x4mmm(at)yandex-team(dot)ru>
wrote:
>
>
> > On 10 Dec 2024, at 16:26, Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
> >
> > IIUC, we do check that it should be in multiple of bank size (i.e.)
> > which is multiple of 2, right? Am I missing something?
>
> Bank selection code assumes that number of buffers is power of 2.
> If the number of buffers is not power of 2 - only subset of buffers will
> be used. In worst case, e.g. 65 buffers, everything will be buffered only
> in bank 64.
But why that would be the case? the acceptable values for GUC to configure
the slru buffers are in multiple of 16(bank size) we have that check to
check the GUC values.
—
Dilip
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2024-12-10 13:59:11 | Re: XMLDocument (SQL/XML X030) |
Previous Message | Andrey M. Borodin | 2024-12-10 13:53:50 | Re: Fix bank selection logic in SLRU |