| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrey Zhidenkov <andrey(dot)zhidenkov(at)gmail(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Memory leak in Pl/Python |
| Date: | 2016-06-26 18:38:12 |
| Message-ID: | 19878.1466966292@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrey Zhidenkov <andrey(dot)zhidenkov(at)gmail(dot)com> writes:
> It's very strange, but when I use expression 'update test set test =
> 'test' where id = 1' as argument of plpy.execute() memory do not
> growing at all...
Well, that suggests it's not particularly plpython's fault at all, but
a leak somewhere in the table update. You still haven't provided a
self-contained test case, and this bit of information strongly suggests
that something about the test table is critical to reproducing the
problem.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2016-06-26 20:22:38 | Re: Rethinking representation of partial-aggregate steps |
| Previous Message | Andrey Zhidenkov | 2016-06-26 18:15:22 | Re: Memory leak in Pl/Python |