I have tested it and I can now confirm that the issue is with pg8000. I
think its a good idea to mention this in the WIKI.
On Friday, July 29, 2016 at 12:12:07 AM UTC+5:30, Niphlod wrote:
>
> could you please try with psycopg2 ?
>
> On Thursday, July 28, 2016 at 6:53:10 PM UTC+2,
f postgresql...
>
> On Wednesday, July 27, 2016 at 5:09:34 AM UTC+2, Abhishek Ram wrote:
>>
>> Well the memory leak was from the postgres processes spawned by the
>> web2py scheduler process. I am sure about this as I have seen TOP and
>> confirmed that it was these processes that w
he leak in postgresql processes CAN'T be generated by
> web2py in any circumnstance. Unless you tinkered a lot with postgresql.conf
> (which is pretty conservative in all distros) you won't ever see postgresql
> leaking.
>
> On Sunday, July 17, 2016 at 5:50:04 AM UTC+2, Abhishek Ram wr
is running.
So my question is what is causing the scheduler process to do this?
P.S. The postgres processes linked to the main web2py process do not
exhibit this behaviour.
Regards
Abhishek Ram
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py
I am updating a record with a List field, but I see that the select widget
correspoding to this field is not populated with the existing value in the
record.
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
-
5 matches
Mail list logo