From: | <g(dot)hintermayer(at)inode(dot)at> |
---|---|
To: | <scott(dot)marlowe(at)ihs(dot)com> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Backend memory leakage when inserting |
Date: | 2003-05-07 07:02:42 |
Message-ID: | 50544.213.33.72.146.1052290962.squirrel@webmail.inode.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On Tue, 6 May 2003, Gerhard Hintermayer wrote:
> [...]
>>
>> Did compile postgreSQL (7.3.1) on a SuSE 8.1 box (Linux,2.4.19 kernel)
>> and see exactly the same behavior. Seems like the amount of leakage
>> depends on the size (number of tables, number of triggers ???) of the
>> whole database, on a empty database the memory growth rate is quite
>> slow (see posted example) , on the production system the mem usage
>> was ~ 120 MB after ~ 300000 inserts.
>
> How many shared buffers is your machine set to use? it may just be
> using them and it looks like a memory leak when it isn't.
In the test case I use the standard value for shared buffers (I think
64=512k).
On the production server I use 25000 (=200M). If a insert process would
try to takeover all of the shared memory, this would'nt be a good thing
either.
Gerhard
From | Date | Subject | |
---|---|---|---|
Next Message | Manfred Koizar | 2003-05-07 07:15:12 | Re: select offset by alphabetical reference |
Previous Message | Richard Huxton | 2003-05-07 06:48:35 | Re: Cancelling a command. |