Re: PG 7.3 is five years old today

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