| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | krichy(at)tvnetwork(dot)hu, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: long transactions / backend memory usage |
| Date: | 2015-11-26 16:47:26 |
| Message-ID: | 5657379E.5040104@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11/26/2015 06:35 AM, krichy(at)tvnetwork(dot)hu wrote:
> Dear all,
>
> 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.
Also what minor versions for the above?
>
> Thanks in advance,
> Kojedzinszky Richárd
> Euronet Magyarorszag Informatika Zrt.
>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-11-26 17:43:41 | Re: long transactions / backend memory usage |
| Previous Message | Karsten Hilbert | 2015-11-26 16:24:38 | Re: long transactions / backend memory usage |