Subject: Re: [vserver] Shared Memory
From: Herbert Poetzl <herbert@13thfloor.at>
Date: Tue, 27 Oct 2009 09:54:48 +0100

On Tue, Oct 27, 2009 at 12:15:25AM +0100, Holger Amann wrote:
> Hi!

> We have a Debian guest running on a Debian Host (linux-image-2.6.26-1- 
> vserver-amd64, util-vserver  0.30.216~r2772-6) for our Postgres 8.4  
> database. After a period of time, Postgres got killed

> [27795665.838308] VM: killing process postgres

> This is reproducable, if we open a few connections and execute a large  
> query on each of them, sequential. The guests "top" (VIRT_MEM) showed  
> us, that after an executed query on a connection (process), the  
> available memory decreases with the amount of postgres' shmem setting  
> ( "shared_buffer_size", shared memory) until swap got filled. The  
> settings for Postgres are ok, it never comes to that situation on a  
> _real_ server with an equal configuration  (available Ram, equal  
> database content, equal configuration and so on). What could lead to  
> that wrong behaviour?

please try with a working kernel and not with the
known-broken debian kernel, and recent util-vserver,
if the issue persists, please run an 'strace -fF' of
postgress for some activity, so that we can take a
look what happens on the query ...

best,
Herbert

> Thanks in advance

> Holger