On Fri, Mar 7, 2025 at 11:20 AM Jakub Wartak <jakub.war...@enterprisedb.com> wrote: > > Hi, > On Wed, Mar 5, 2025 at 10:30 AM Jakub Wartak > <jakub.war...@enterprisedb.com> wrote: > >Hi, > > > > Yeah, that's why I was mentioning to use a "shared" > > > populate_buffercache_entry() > > > or such function: to put the "duplicated" code in it and then use this > > > shared function in pg_buffercache_pages() and in the new numa related one. > > > > OK, so hastily attempted that in 7b , I had to do a larger refactor > > there to avoid code duplication between those two. I don't know which > > attempt is better though (7 vs 7b).. > > > > I'm attaching basically the earlier stuff (v7b) as v8 with the > following minor changes: > - docs are included > - changed int8 to int4 in one function definition for numa_zone_id
.. and v9 attached because cfbot partially complained about .cirrus.tasks.yml being adjusted recently (it seems master is hot these days). -J.
v9-0001-Add-optional-dependency-to-libnuma-Linux-only-for.patch
Description: Binary data
v9-0003-Add-pg_shmem_numa_allocations-to-show-NUMA-zones-.patch
Description: Binary data
v9-0002-Extend-pg_buffercache-with-new-view-pg_buffercach.patch
Description: Binary data
