From: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> |
---|---|
To: | Tomas Vondra <tomas(at)vondra(dot)me> |
Cc: | Christoph Berg <myon(at)debian(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Tomas Vondra <tomas(dot)vondra(at)postgresql(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: Introduce pg_shmem_allocations_numa view |
Date: | 2025-06-25 06:45:55 |
Message-ID: | aFubIxuntEaPeO2t@ip-10-97-1-34.eu-west-3.compute.internal |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Hi,
On Tue, Jun 24, 2025 at 10:32:25PM +0200, Tomas Vondra wrote:
>
> Attached is a minor tweak of the valgrind suppresion rules,
Thanks!
> to add the
> two places touching the memory. I was hoping I could add a single rule
> for pg_numa_touch_mem_if_required, but that does not work - it's a
> macro, not a function. So I had to add one rule for both functions,
> querying the NUMA. That's a bit disappointing, because it means it'll
> hide all other failues (of Memcheck:Addr8 type) in those functions.
>
Shouldn't we add 2 rules for Memcheck:Addr4 too?
> Perhaps it'd be be better to turn pg_numa_touch_mem_if_required into a
> proper (inlined) function, at least with USE_VALGRIND defined.
Yeah I think that's probably better to reduce the scope to what we really want to.
> Something
> like the v2 patch -
yeah, maybe:
- add a rule for Memcheck:Addr4?
- have the same parameters name for the macro and the function?
Regards,
--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jakub Wartak | 2025-06-25 07:15:02 | Re: pgsql: Introduce pg_shmem_allocations_numa view |
Previous Message | Bertrand Drouvot | 2025-06-25 06:11:21 | Re: pgsql: Introduce pg_shmem_allocations_numa view |
From | Date | Subject | |
---|---|---|---|
Next Message | Bertrand Drouvot | 2025-06-25 06:50:50 | Re: POC: enable logical decoding when wal_level = 'replica' without a server restart |
Previous Message | Dilip Kumar | 2025-06-25 06:17:46 | Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly |