It's possible that the problem is in my C code but every time that I'm allocating memory, using always the palloc() function, I'm always calling the pfree().
There is some way to analyze the code meanwhile is working inside the Postgre server (something like valgrind)?
However the command free -m on my machine outputs:
total used free shared buffers cached
Mem: 2010 664 1345 0 157 383
-/+ buffers/cache: 123 1886
Swap: 16386 41 16345
I think that the swap is enough.
Could you give me some tips about how can I see where is the problem?
Thank you for your help!
Cheers,
Angelo.
> Date: Thu, 17 Sep 2009 03:14:31 +1200
> From: oliver@opencloud.com
> To: amenuor@hotmail.com
> CC: pgsql-jdbc@postgresql.org
> Subject: Re: [JDBC] OOM on large SELECT
>
> Angelo Nicolosi wrote:
>
> > The dmesg command says:
> >
> > Out of memory: Killed process 22592 (postgres).
>
> If you are getting OOM-kills from the kernel, that usually means you
> have system-wide memory exhaustion.
>
> > I wrote some C-Language functions, added on a database [...]
>
> Since the size of a JVM is roughly constant, I would guess that the
> problem actually lies in your C code.
>
> Alternatively your system just doesn't have enough virtual memory
> configured to do whatever it is you're trying to do. Add more swap.
>
> Either way, it doesn't look like a JDBC driver problem based on the
> information you have given.
>
> -O
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc
Un' immagine personale per Messenger?
Crea il tuo Avatar!