Re: Is it a memory leak in PostgreSQL 7.4beta?

Mark Kirkwood <markir@paradise.net.nz>

From: Mark Kirkwood <markir@paradise.net.nz>
To: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Hans-Jürgen Schönig <hs@cybertec.at>, pgsql-hackers@postgresql.org, eg@cybertec.at
Date: 2003-08-31T04:43:50Z
Lists: pgsql-hackers
Stephan Szabo wrote:

>
>I rebuild without debug, and ran just the start/insert/commit sequence
>over and over and noticed that on my machine it looked to grow as above
>but that if I let it go long enough it seemed to basically stop (or at
>least the growth was slow enough to go without notice as compared to the
>easily noticable growth before).  I'm running the full sequence now, but
>it's going to be a while before it stops or gets up to the place where it
>stoped in the s/i/c sequence.
>  
>
This is the Pg backend line from top after about 90 minutes runtime :

 PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
16083 postgres  17   0  9172 9172 8524 R 94.7  2.4  84:59.68 postmaster

No sign of the shared growth stopping at this stage...

Pg built with --disable-debug --without-zlib

Platform is Linux 2.4.21+ xfs (Mandrake 9.2beta)

regards


Mark