To: Vincent Dautremont <vincent@searidgetech.com>
cc: pgsql-admin@postgresql.org
Subject: Re: out of memory error 
In-reply-to: 
 <CAA4Vp48tDW5vRA3t=WqEJzwYfDY1wmZ=YwDgPkaZ8ktMwUsUaQ@mail.gmail.com>
References: 
 <CAA4Vp4_pD3tc8dT8rtdPjO4vQfW+eyuNpYb72HPYYRokdPHS7A@mail.gmail.com>
	<3902.1337708023@sss.pgh.pa.us>
	<CAA4Vp48tDW5vRA3t=WqEJzwYfDY1wmZ=YwDgPkaZ8ktMwUsUaQ@mail.gmail.com>
Comments: In-reply-to Vincent Dautremont <vincent@searidgetech.com>
	message dated "Tue, 22 May 2012 14:04:39 -0400"
Date: Tue, 22 May 2012 14:30:03 -0400
Message-ID: <5105.1337711403@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Vincent Dautremont <vincent@searidgetech.com> writes:
> I think that i'm using the database for pretty basic stuffs.
> It's mostly used with stored procedures to update/ insert / select a row of
> each table.
> On 3 tables (less than 10 rows each), clients does updates/select at 2Hz to
> have pseudo real-time data up to date.
> I've got a total of 6 clients to the DB, they all access DB using stored
> procedures
> I would say that this is a light usage of the DB.

> Then I have rubyrep 1.2.0 running to sync a backup of the DB.
> it syncs 8 tables : 7 of them doesn't really change often and 1 is one of
> the pseudo real-time data one.

This is not much information.  What I suspect is happening is that
you're using plpgsql functions (or some other PL) in such a way that the
system is leaking cached plans for the functions' queries; but there is
far from enough evidence here to prove or disprove that, let alone debug
the problem if that is a correct guess.  An entirely blue-sky guess as
to what your code might be doing to trigger such a problem is if you
were constantly replacing the same function's definition via CREATE OR
REPLACE FUNCTION.  But that could be totally wrong, too.

Can you put together a self-contained test case that triggers similar
growth in the server process size?

			regards, tom lane