Re: PG 7.3 is five years old today

From: "Usama Dar" <munir(dot)usama(at)gmail(dot)com>
To: "Andreas 'ads' Scherbaum" <adsmail(at)wars-nicht(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: PG 7.3 is five years old today
Date: 2007-11-29 12:26:14
Message-ID: ff0e67090711290426ncabb42ft2fa04afe01b2abf6@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

+1

On Nov 29, 2007 4:09 AM, Andreas 'ads' Scherbaum <adsmail(at)wars-nicht(dot)de>
wrote:

> On Tue, 27 Nov 2007 15:37:04 -0500 Tom Lane wrote:
>
> > "Andreas 'ads' Scherbaum" <adsmail(at)wars-nicht(dot)de> writes:
> > > On Tue, 27 Nov 2007 11:08:58 -0800 Joshua D. Drake wrote:
> > >> Release 7.3.21 with and EOL addendum :). E.g; this is the last
> release
> > >> of 7.3 and 7.3 is now considered unsupported.
> >
> > > I know at least one customer who is using RHEL-3 and PG 7.3 on dozens
> > > machines worldwide.
> >
> > Are they running 7.3.20? Will they update to 7.3.21 promptly when we
> > ship it? Or are they using whatever Red Hat includes in RHEL-3?
> > (which is still 7.3.19 I believe)
>
> I'm not sure, which micro version they are using right now. I only know,
> they have 7.3.x, cause i already had to take care of this on some
> projects.
>
>
> > One of the reasons for losing interest in frequent updates is that
> > it seems most of the people we hear from who are running 7.3.x are
> > running a pretty obsolete "x". If we produce an update and no one
> > actually installs it, we're just wasting time with make-work.
>
> I said: we should not disband support of 7.3 today, release a final
> version next week and that's it. Something like 3, 4 month of
> pre-announce seems to be ok for me and i don't think, this makes much
> difference.
>
>
> Kind regards
>
> --
> Andreas 'ads' Scherbaum
> Failure is not an option. It comes bundled with your Microsoft product.
> (Ferenc Mantfeld)
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2007-11-29 12:30:21 Re: pgwin32_open returning EINVAL
Previous Message hubert depesz lubaczewski 2007-11-29 12:17:04 Re: [HACKERS] [GENERAL] plperl and regexps with accented characters - incompatible?