Re: Python 3.x versus PG 9.1 branch - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Python 3.x versus PG 9.1 branch
Date
Msg-id CA+TgmoYPB7hbJUa2afo_QFAoTtDueCHADY6wOfG29v0Zc4wy4w@mail.gmail.com
Whole thread Raw
In response to Python 3.x versus PG 9.1 branch  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Jan 13, 2016 at 11:46 AM, Tom Lane <tgl@sss.pgh.pa.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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: pgindent-polluted commits
Next
From: Robert Haas
Date:
Subject: Re: tiny doc patch