| From: | Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hans-Jürgen Schönig <hs(at)cybertec(dot)at>, pgsql-hackers(at)postgresql(dot)org, eg(at)cybertec(dot)at |
| Subject: | Re: Is it a memory leak in PostgreSQL 7.4beta? |
| Date: | 2003-08-31 04:43:50 |
| Message-ID: | 3F517D06.1050807@paradise.net.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-08-31 04:44:25 | Re: pg_dump and REVOKE on function |
| Previous Message | Joe Conway | 2003-08-31 04:42:12 | Re: [HACKERS] New array functions |