Re: Python 3.x versus PG 9.1 branch

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Python 3.x versus PG 9.1 branch
Date: 2016-01-14 16:38:41
Message-ID: CA+TgmoYPB7hbJUa2afo_QFAoTtDueCHADY6wOfG29v0Zc4wy4w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jan 13, 2016 at 11:46 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Or we could just blow it off on the grounds that 9.1 is not long
> for this world anyhow.

+1 for blowing it off. I can't see the point in putting effort into
this. Nobody should be spinning up new PostgreSQL 9.1 deployments at
this point, and whatever PostgreSQL 9.1 deployments already exist are
evidently OK with what we've been doing up until now. So it seems
unlikely to help anyone.

Also, if it does help someone, it will be helping them to deploy a
nearly-obsolete PostgreSQL version at a time when, really, it would be
much better if they were thinking about how to get off that version.

Moreover, it's not inconceivable that back-porting all of those
commits could break something that works now, in which event we would
end up worse off than we are today.

So I really don't see any upside.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-01-14 16:46:07 Re: tiny doc patch
Previous Message Robert Haas 2016-01-14 16:32:38 Re: pgindent-polluted commits