From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: long transactions / backend memory usage |
Date: | 2015-11-26 14:41:06 |
Message-ID: | 20151126144106.GD4221@hermes.hilbert.loc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Nov 26, 2015 at 03:35:49PM +0100, krichy(at)tvnetwork(dot)hu wrote:
> We have run into a case where we run a long transaction, and during the
> transaction the backend process's memory usage is growing constantly.
>
> I've written a script to simulate this, please someone confirm if it is
> normal or not.
>
> The script just inserts and removes rows in a table in a single transaction.
> If given a parameter, the same row is being inserted and removed.
>
> The latter case also produces constantly increasing backend process memory
> usage.
>
> Create the table as in the script, and after run:
>
> $ perl pqtest.pl 5
>
> I've been running the script for nearly 40 minutes right now, it has done
> 120k iterations, and the RSS of the postgresql process is still growing.
>
> This can be reproduced on 9.3 and 9.4 also.
Can it be reproduced when implemented in another language, too ?
Karsten
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2015-11-26 15:47:33 | Re: Convert from hex to string |
Previous Message | krichy | 2015-11-26 14:35:49 | long transactions / backend memory usage |