| From: | Stephen Robert Norris <srn(at)commsecure(dot)com(dot)au> |
|---|---|
| To: | Denis Gasparin <denis(at)edinet(dot)it> |
| Cc: | Postgresql General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Python interface memory leak? |
| Date: | 2001-10-17 08:10:15 |
| Message-ID: | 1003306217.6934.4.camel@chinstrap |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 2001-10-17 at 16:56, Denis Gasparin wrote:
> 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...
Actually, it's a bug. I spent most of today with a co-worker looking for
it. There's a Py_DECREF missing in the fetch routine, which makes it
leak the results of every fetch. Who do I send the (one-line) fix to?
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Poslusny | 2001-10-17 08:23:23 | Re: |
| Previous Message | Denis Gasparin | 2001-10-17 06:56:20 | Re: Python interface memory leak? |