Re: Troubles with performances

From: Jan Wieck <janwieck(at)Yahoo(dot)com>
To: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>
Cc: Warren Vanichuk <pyber(at)street-light(dot)com>, "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Troubles with performances
Date: 2001-01-19 13:03:02
Message-ID: 200101191303.IAA06518@jupiter.jw.home
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Lamar Owen wrote:
>
> /*
> * _SHM_ID_BITS + _SHM_IDX_BITS must be <= 24 on the i386 and
> * SHMMAX <= (PAGE_SIZE << _SHM_IDX_BITS).
> */
>
> #define SHMMAX 0x2000000 /* max shared seg size (bytes)
> */
> /* Try not to change the default shipped SHMMAX - people rely on it */
>
> -------
>
> Hmmmm....
>
> Looks pretty difficult to change.

echo 134217728 >/proc/sys/kernel/shmmax

set's the maximum allowed segment! size to 128M. Shared
memory under Linux can be swapped, so if you have 256M
physical and run 3 postmasters, you can start all of them
with 64M (or more) and while they're idle they most likey
consume some swap space. But when it poors, they'll grab the
memory they need.

Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jan Wieck 2001-01-19 13:14:25 Re: order of triggers
Previous Message Cedar Cox 2001-01-19 11:41:20 Re: [INTERFACES] pl/pgSQL & transaction