Re: pgsql: Introduce pg_shmem_allocations_numa view

From: Christoph Berg <myon(at)debian(dot)org>
To: Tomas Vondra <tomas(dot)vondra(at)postgresql(dot)org>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Introduce pg_shmem_allocations_numa view
Date: 2025-06-23 14:48:27
Message-ID: aFlpO2lBsMjqarbp@msg.df7cb.de
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Re: To Tomas Vondra
> Why do we try to force the pages to be allocated at all? This is just
> a monitoring function, it should not change the actual system state.

One-time touching might also not be enough, what if the pages later
get swapped out and the monitoring functions are called again? They
will have to deal with these "not in memory" error conditions anyway.

Christoph

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2025-06-23 15:14:54 Re: pgsql: Introduce pg_shmem_allocations_numa view
Previous Message Christoph Berg 2025-06-23 14:42:26 Re: pgsql: Introduce pg_shmem_allocations_numa view

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-06-23 14:51:21 Re: Improve CRC32C performance on SSE4.2
Previous Message Ranier Vilela 2025-06-23 14:46:05 Fixes possible api misuse when connecting with server