From: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
---|---|
To: | Tomas Vondra <tomas(at)vondra(dot)me> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
Subject: | Re: Adding basic NUMA awareness |
Date: | 2025-07-03 14:07:18 |
Message-ID: | CAExHW5tj3rb5ox0jVQEWqAExu0cqAubj60BW2R_04mmbuG9XpA@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jul 2, 2025 at 6:06 PM Tomas Vondra <tomas(at)vondra(dot)me> wrote:
>
> I'm not sure how you're rebuilding the freelist. Presumably it can
> contain buffers that are no longer valid (after shrinking). How is that
> handled to not break anything? I think the NUMA variant would do exactly
> the same thing, except that there's multiple lists.
Before shrinking the buffers, we walk the free list removing any
buffers that are going to be removed. When expanding, by linking the
new buffers in the order and then adding those to the already existing
free list. 0005 patch in [1] has the code for the same.
--
Best Wishes,
Ashutosh Bapat
From | Date | Subject | |
---|---|---|---|
Next Message | Yugo Nagata | 2025-07-03 14:18:12 | Re: Prevent internal error at concurrent CREATE OR REPLACE FUNCTION |
Previous Message | Daniel Gustafsson | 2025-07-03 14:06:58 | Re: Explicitly enable meson features in CI |