From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Davin M(dot) Potts" <davin(at)discontinuity(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
Subject: | Re: [Pgbuildfarm] buildfarm olinguito vs python |
Date: | 2015-05-25 20:37:11 |
Message-ID: | 27151.1432586231@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Davin M. Potts" <davin(at)discontinuity(dot)net> writes:
> At Alvaro's suggestion, I'm forwarding my questions (see email thread
> further below) to this list.
> In short, building of PL/Python has been disabled on OpenBSD since 2005.
> The errors seen at the time (on OpenBSD and FreeBSD, both) may or may
> not still be an issue with modern builds of Python. Can someone point
> me to examples of how these errors manifested themselves? Has Peter
> Eisentraut or others poked at this recently enough to tell me this is
> not worth chasing down?
I'm fairly sure that the errors were blatantly obvious, ie failure to
build or failure to pass even basic regression tests. If you can tell
us that that configure check is inappropriate on modern openbsd, I'd
be happy to see it go.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2015-05-25 20:41:10 | Re: fsync-pgdata-on-recovery tries to write to more files than previously |
Previous Message | Andrew Dunstan | 2015-05-25 20:26:02 | Re: [Pgbuildfarm] buildfarm olinguito vs python |