-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
>> I notice that we now have four buildfarm members failing in the 8.1
>> branch, with symptoms indicating that they are running python 2.5,
>> which pre-8.2 plpython has known incompatibilities with. I think
>> it's high time we back-patched those compatibility fixes
> Why would anyone running PostgreSQL 8.1 in production upgrade their stable
> server to Python 2.5, and remove Python 2.4 in the process?
Because the keep their operating system up to date, and because we still
do not have any sort of in-place upgrade.
> What is the use case, except "build farm maintainers can't keep their
> environments stable"?
What's not stable about having Python 2.5?
> Have we had any complaints from the field about this?
Probably due to lack of plpython use more than anything else, but I don't
see what the alternative is: hard-code a hack into the buildfarm code?
Keep emailing individual buildfarm members and asking them to make special
exceptions? The buildfarm is meant to test many different combinations of
factors that may or may not be seen in the field, and in this case it is
doing that job admirably.
- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200807290721
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iEYEAREDAAYFAkiO/bUACgkQvJuQZxSWSsissgCdFVaiZ3AvGTzCChrVa6JAAUAf
TYcAoON6x7YJm8YIJpem7KwaV/D96oSz
=ERo0
-----END PGP SIGNATURE-----
