Re: Use Python "Limited API" in PL/Python

2025-01-15 Thread Jakob Egger
On 14.01.2025, at 16:51, Jakob Egger wrote: > I've tried to create a patch with this change. I'm attaching it to this > message so that cfbot picks it up. (I was unable to reproduce the issue > locally) Apologies, please disregard my last patch. It does not work. It lo

Re: Use Python "Limited API" in PL/Python

2025-01-14 Thread Jakob Egger
On 07.01.2025, at 08:34, Peter Eisentraut wrote:On 02.12.24 09:51, Peter Eisentraut wrote:This patch changes PL/Python to use the Python "limited API". This API has stronger ABI stability guarantees.[0] This means, you can build PL/ Python against any Python 3.x version and use any other Python 3.

Re: Frontend/Backend Protocol: SSL / GSS Protocol Negotiation Problem

2019-12-06 Thread Jakob Egger
> On 6. Dec 2019, at 16:45, Andrew Gierth wrote: > >>>>>> "Jakob" == Jakob Egger writes: > > Jakob> But this also needs to be fixed on the client side as well, > Jakob> otherwise affected clients can't connect to older servers > J

Re: Protocol problem with GSSAPI encryption?

2019-12-06 Thread Jakob Egger
> On 4. Dec 2019, at 06:24, Stephen Frost wrote: > > Greetings, > > * Andrew Gierth (and...@tao11.riddles.org.uk) wrote: >>> "Peter" == Peter Eisentraut writes: >> It seems to me that this is a bug in ProcessStartupPacket, which should accept both GSS or SSL negotiation requests

Re: Frontend/Backend Protocol: SSL / GSS Protocol Negotiation Problem

2019-12-06 Thread Jakob Egger
> On 6. Dec 2019, at 15:08, Michael Paquier wrote: > > On Fri, Dec 06, 2019 at 02:25:46PM +0100, Jakob Egger wrote: >> I've received a bug report from a PostgreSQL user that psql 12.1 >> failed to connect to a PostgreSQL 12.1 server, with the following >> er

Frontend/Backend Protocol: SSL / GSS Protocol Negotiation Problem

2019-12-06 Thread Jakob Egger
Hi! I've received a bug report from a PostgreSQL user that psql 12.1 failed to connect to a PostgreSQL 12.1 server, with the following error message: psql: error: could not connect to server: FATAL: unsupported frontend protocol 1234.5679: server supports 2.0 to 3.0 After inspecting a TCP dump

Re: PG vs macOS Mojave

2018-11-02 Thread Jakob Egger
> Am 1. Nov. 2018 um 04:17 schrieb Tom Lane : > > You can verify the thing's built-in settings with something like > > $ echo >test.c > $ clang -v -E test.c > > and on Xcode 10.0 I get > > "/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang" > -cc1 -t

Re: PG vs macOS Mojave

2018-10-17 Thread Jakob Egger
Am 17.10.2018 um 16:28 schrieb Tom Lane : > It's also very odd, > if the compiler will search the sysroot automatically, why that seemingly > works for tcl.h but not perl.h. plperl definitely still fails if you > lobotomize the PG_SYSROOT logic. Because pl/tcl ends up using -iwithsysroot to spec

Re: PG vs macOS Mojave

2018-10-17 Thread Jakob Egger
Am 16. Okt. 2018 um 17:13 schrieb Tom Lane : > Oh, well *this* is interesting. I stated at the top of this thread that > pltcl doesn't build on Mojave without -isysroot because TCL_INCLUDE_SPEC > gets set to > -iwithsysroot > /System/Library/Frameworks/Tcl.framework/Versions/8.5/Headers >

Re: PG vs macOS Mojave

2018-10-16 Thread Jakob Egger
Am 25. Sep. 2018 um 06:49 schrieb Tom Lane : > It's a bit scary to be adding -isysroot globally. > (...) > I've tested this on all the macOS versions I have at hand, and it > doesn't seem to break anything. > (...) > Thoughts? > > regards, tom lane This breaks building ext