| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Python 2.5 vs the buildfarm |
| Date: | 2008-07-29 07:58:33 |
| Message-ID: | 200807291058.33911.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Am Monday, 28. July 2008 schrieb Tom Lane:
> 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? What is the use
case, except "build farm maintainers can't keep their environments stable"?
Have we had any complaints from the field about this?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2008-07-29 08:01:59 | Re: gsoc, oprrest function for text search take 2 |
| Previous Message | Peter Eisentraut | 2008-07-29 07:53:26 | Re: Do we really want to migrate plproxy and citext into PG core distribution? |