Re: Use Python "Limited API" in PL/Python - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Use Python "Limited API" in PL/Python
Date
Msg-id a1bbb380-9e26-4694-9e68-cfca31b9b155@eisentraut.org
Whole thread Raw
In response to Re: Use Python "Limited API" in PL/Python  (Peter Eisentraut <peter@eisentraut.org>)
Responses Re: Use Python "Limited API" in PL/Python
List pgsql-hackers
On 05.03.25 17:40, Peter Eisentraut wrote:
> On 03.03.25 11:17, Peter Eisentraut wrote:
>> Update for the hackers list: This patch set was briefly committed but 
>> had to be reverted because it crashed on some older Python versions; 
>> see [0].
>>
>> I have locally reproduced the problem with Python 3.6 and 3.7; Python 
>> 3.8 is ok.  This matches the results from the buildfarm.
>>
>> I have poked at this a bit more but haven't gotten a good idea where 
>> or how to fix it so far.  Help welcome.
> 
> I have figured this out.  There was a Python API change/bugfix between 
> 3.7 and 3.8 that directly affects this patch.  The relevant commit is 
> <https://github.com/python/cpython/commit/364f0b0f19c>.  I have applied 
> the workarounds described there to my patch set, and now it works for 
> 3.6 and 3.7 as well.

This has all been committed now.




pgsql-hackers by date:

Previous
From: Álvaro Herrera
Date:
Subject: Re: Minor rework of ALTER TABLE SET RelOptions code
Next
From: Frédéric Yhuel
Date:
Subject: Add time spent in posix_fadvise() in I/O read time ?