Skip site navigation (1) Skip section navigation (2)

Re: buglet in 7.1.4

From: Neil Conway <neilc(at)samurai(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, weigelt(at)metux(dot)de,pgsql-bugs(at)postgresql(dot)org
Subject: Re: buglet in 7.1.4
Date: 2004-03-09 22:30:31
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
Tom Lane wrote:
> The "harm" is the developer time spent on doing so.  Releasing back
> versions takes nontrivial effort (witness what it took to get 7.3.6
> out the door :-().

True; that said, much of this overhead is (IMHO) avoidable. There 
should be little or no manual intervention needed in the release 
process, so if the code in the REL7_1_STABLE branch is 'release 
quality', there shouldn't be that much work needed to issue an 
additional release.

But yes, I agree: developer time is finite, and we should focus most 
of it on 7.4.x and 7.5

> Also, quite frankly, I don't want to encourage people to keep using
> such old releases.  If they are installing on a new machine they should
> update to something newer and less buggy.

I agree, but there are some plausible uses for installing old releases 
on new machines. For example, there are probably commercial or 
unmaintained legacy applications that will only work smoothly with 7.1 
(or some other old release). Similarly, an application developer may 
wish to ensure that their application is portable among the most 
recent 'x' Postgres releases, and want to install copies of them for 
testing. Or a production environment may wish to install an identical 
version of PG on all their machines, so they might be forced to run a 
fairly old release on newly-purchased machines.

So I think there are legitimate, albeit somewhat obscure, reasons for 
running an old release on a relatively modern system.


In response to


pgsql-bugs by date

Next:From: Tom LaneDate: 2004-03-09 22:44:18
Subject: Re: buglet in 7.1.4
Previous:From: Theodore PetroskyDate: 2004-03-09 22:17:23
Subject: not necessarily a bug...

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group