Re: SHM_LOCK under Linux ... do we use this? - Mailing list pgsql-hackers

From Qingqing Zhou
Subject Re: SHM_LOCK under Linux ... do we use this?
Date
Msg-id de1jlh$22k1$1@news.hub.org
Whole thread Raw
In response to SHM_LOCK under Linux ... do we use this?  ("Marc G. Fournier" <scrappy@postgresql.org>)
Responses Re: SHM_LOCK under Linux ... do we use this?
List pgsql-hackers
""Marc G. Fournier"" <scrappy@postgresql.org> writes
>
> I've done a grep through the code, to see if its something that we do use,
and
> it doesn't seem to come back with anything ... I believe its considered
> common knowledge that 'swapping' for a database is evil, so am wondering
> if there is some way that we can make use of this to help reduce/eliminate
> that from happening?
>

There are some similar flags in other OS could help us to keep the memory
resident in. However, it is not always a net win if we force it. This is
because other parts of the system (like fork a process) may need memory, so
the OS will pick up the "coldest" memory to be swapped. If we have already
use our memory intensively, I don't think we will be swapped. On the
contrary, if we force OS not to swap some memory, we may get other penalties
like our processes have to be sarcrificed.

Regards,
Qingqing




pgsql-hackers by date:

Previous
From: Tino Wildenhain
Date:
Subject: Re: How to secure PostgreSQL Data for distribute?
Next
From: "Merlin Moncure"
Date:
Subject: Re: [PERFORM] bitmap scan issues 8.1 devel