Re: Memory leak in Pl/Python - Mailing list pgsql-hackers

From Andrey Zhidenkov
Subject Re: Memory leak in Pl/Python
Date
Msg-id CAJw4d1XQmqCaX4EmiW+XVZcWSx1PqzZ4M0tiV0-zv4p4qwzcHA@mail.gmail.com
Whole thread Raw
In response to Re: Memory leak in Pl/Python  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: Memory leak in Pl/Python  (Andrey Zhidenkov <andrey.zhidenkov@gmail.com>)
Re: Memory leak in Pl/Python  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
For test I wrote script in Python, which calls a test function via psycopg2:

#!/usr/bin/env python2

import psycopg2

conn = psycopg2.connect('xxx')

cursor = conn.cursor()

cursor.execute('set application_name to \'TEST\'')

for i in range(1, 1000000):   cursor.execute('select test()')   conn.commit()


I see memory consumption in htop and pg_activity tools.

On Sat, Jun 25, 2016 at 2:00 AM, David G. Johnston
<david.g.johnston@gmail.com> wrote:
> On Fri, Jun 24, 2016 at 6:41 PM, Andrey Zhidenkov
> <andrey.zhidenkov@gmail.com> wrote:
>>
>> For example, when I call this procedure
>> many times,
>
>
> Call how?  Specifically, how are you handling transactions in the calling
> client?  And what/how are you measuring memory consumption?
>
> David J.
>



-- 
Andrey Zhidenkov / Database developer
+79265617190/ andrey.zhidenkov@gmail.com




This e-mail message may contain confidential or legally privileged
information and is intended only for the use of the intended
recipient(s). Any unauthorized disclosure, dissemination,
distribution, copying or the taking of any action in reliance on the
information herein is prohibited. E-mails are not secure and cannot be
guaranteed to be error free as they can be intercepted, amended, or
contain viruses. Anyone who communicates with us by e-mail is deemed
to have accepted these risks. Company Name is not responsible for
errors or omissions in this message and denies any responsibility for
any damage arising from the use of e-mail. Any opinion and other
statement contained in this message and any attachment are solely
those of the author and do not necessarily represent those of the
company.



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Improving executor performance
Next
From: Craig Ringer
Date:
Subject: Re: initdb issue on 64-bit Windows - (Was: [pgsql-packagers] PG 9.6beta2 tarballs are ready)