On 8/18/2005 5:14 AM, Qingqing Zhou wrote:
""Marc G. Fournier"" <[EMAIL PROTECTED]> 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.
If this happens often to be PostgreSQL's shared buffers, then you have
configured too many of them.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== [EMAIL PROTECTED] #
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
