Re: Time to drop plpython2?
От | Andres Freund |
---|---|
Тема | Re: Time to drop plpython2? |
Дата | |
Msg-id | 20220113174740.tu72p4gpq5t73wb7@alap3.anarazel.de обсуждение исходный текст |
Ответ на | Re: Time to drop plpython2? (Peter Eisentraut <peter.eisentraut@enterprisedb.com>) |
Список | pgsql-hackers |
Hi, On 2022-01-11 13:59:32 +0100, Peter Eisentraut wrote: > I suspect at this point, the Meson move isn't going to happen for PostgreSQL > 15. Yes - I IIRC even noted early in the thread that I don't think it's realistic to finish it in time for 15. There's just a good amount of portability hacking left to be done, and a good chunk of cleanup. I have a new colleague working on automating testing it on more platforms. Getting a few of the prerequisite patches in would make it more likely to succeed in 16 though. > Even if the code were ready, which it is not, then this kind of thing > would surely be something more sensible to put into PG16 early rather than > PG15 late. Right. There's also a lot of discussion around transition paths etc that need to be happening first. A lot of other projects that moved ran with multiple buildsystems for ~1 release, so things could mopped up without blocking everyone. > I think what I wrote in the message I'm responding to is the best way > forward, although maybe with less than 60 days now. Already happened, but I'm a belated +1 ;) Greetings, Andres Freund
В списке pgsql-hackers по дате отправления: