Re: NULL dereference when memory is tight

From: Federico Di Gregorio <federico(dot)digregorio(at)dndg(dot)it>
To: psycopg(at)postgresql(dot)org
Subject: Re: NULL dereference when memory is tight
Date: 2011-02-24 09:52:52
Message-ID: 4D662A74.9020300@dndg.it
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: psycopg

On 24/02/11 10:39, Brian Sutherland wrote:
> Attached is a patch for another issue, though I'm not sure if calling
> PyErr_NoMemory within libpq is sane.

I won't call any Py* function without holding the GIL. That's why
conn_notice_callback() uses its own data structure instead of a simple
Python list.

federico

--
Federico Di Gregorio federico(dot)digregorio(at)dndg(dot)it
Studio Associato Di Nunzio e Di Gregorio http://dndg.it
The reverse side also has a reverse side. -- Japanese proverb

In response to

Responses

Browse psycopg by date

  From Date Subject
Next Message Daniele Varrazzo 2011-02-24 10:32:23 Re: NULL dereference when memory is tight
Previous Message Brian Sutherland 2011-02-24 09:39:20 Re: NULL dereference when memory is tight