Re: failed NUMA pages inquiry status: Operation not permitted - Mailing list pgsql-hackers

From Christoph Berg
Subject Re: failed NUMA pages inquiry status: Operation not permitted
Date
Msg-id aWrYZC5HFMqI0fL1@msg.df7cb.de
Whole thread Raw
In response to Re: failed NUMA pages inquiry status: Operation not permitted  (Tomas Vondra <tomas@vondra.me>)
List 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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: 001_password.pl fails with --without-readline
Next
From: Michael Paquier
Date:
Subject: Re: [PATCH] Remove redundant Assert() calls in report_namespace_conflict()