From: | Denis Gasparin <denis(at)edinet(dot)it> |
---|---|
To: | Postgresql General <pgsql-general(at)postgresql(dot)org> |
Cc: | Stephen Robert Norris <srn(at)commsecure(dot)com(dot)au> |
Subject: | Re: Python interface memory leak? |
Date: | 2001-10-17 06:56:20 |
Message-ID: | 5.1.0.14.0.20011017085106.00a8dc90@10.1.1.2 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
At 16/10/01 14.00, you wrote:
>Does the python interface leak memory? We are seeing the process grow
>with basically every select. Any suggestions on what's going on? There
>are no cycles, and a trivial program (basically a loop around a select)
>demonstrates the problem.
>
>This is 7.1.2 on RH7.[01].
>
> Stephen
The python interface stores query datas in memory. If you don't clean such
datas, the used memory will grow up...
If this is not the case, try the PoPy postgres driver for Python
(http://popy.sourgeforge.net or
http://freshmeat.net/redir/popy/8258/url_tgz/PoPy-2.0.7.tar.gz ).
Regards,
Doct. Eng. Denis
Gasparin denis(at)edistar(dot)com
---------------------------------------------------------------------------------------
Programmer & System
Administrator http://www.edistar.com
---------------------------------------------------------------------------------------
Well alas we've seen it all before
Knights in armour, days of yore
The same old fears and the same old crimes
We haven't changed since ancient times
-- Iron Hand -- Dire Straits --
---------------------------------------------------------------------------------------
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Robert Norris | 2001-10-17 08:10:15 | Re: Python interface memory leak? |
Previous Message | Oliver Elphick | 2001-10-17 06:53:01 | Re: Easy way of pruning pg_data? |