| From: | Christoph Berg <myon(at)debian(dot)org> |
|---|---|
| To: | Tomas Vondra <tomas(at)vondra(dot)me> |
| Cc: | Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: failed NUMA pages inquiry status: Operation not permitted |
| Date: | 2026-01-17 00:31:32 |
| Message-ID: | aWrYZC5HFMqI0fL1@msg.df7cb.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Re: Tomas Vondra
> Here's WIP fix for the root cause, i.e. handling status -2 in the two
> views querying NUMA node for memory pages:
Thanks!
> I'm not sure if we need to mention this in the docs. It probably should
> mention the column can be NULL, which means "unknown node".
We could simply say
The returned value can be NULL if the NUMA node cannot be
determined, e.g. when the page has been swapped out.
> Subject: [PATCH] Handle ENOENT status when querying NUMA node
...
> We touch the memory before querying the status, but there is no
> guarangee it won't be moved to swap in between. We do the touching only
^ guarantee
Christoph
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2026-01-17 05:26:59 | Re: pgsql: Enable Python Limited API for PL/Python on MSVC |
| Previous Message | Tomas Vondra | 2026-01-16 21:29:47 | Re: failed NUMA pages inquiry status: Operation not permitted |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2026-01-17 00:38:49 | Re: [PATCH] Remove redundant Assert() calls in report_namespace_conflict() |
| Previous Message | Tom Lane | 2026-01-17 00:19:38 | Re: 001_password.pl fails with --without-readline |