From: | Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com> |
---|---|
To: | Melvin Davidson <melvin6925(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | "Igal (at) Lucee(dot)org" <igal(at)lucee(dot)org>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Finally upgrading to 9.6! |
Date: | 2017-10-18 18:08:51 |
Message-ID: | 329e0c0b-2680-a56e-cd2a-b2df6cb0e993@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/18/2017 05:57 PM, Melvin Davidson wrote:
>
> On Wed, Oct 18, 2017 at 11:46 AM, David G. Johnston
> <david(dot)g(dot)johnston(at)gmail(dot)com <mailto:david(dot)g(dot)johnston(at)gmail(dot)com>> wrote:
>
> The contributors do an excellent job but the reality of this
> community is that a critical mass of people do not start seriously
> testing and using a new version until it is officially released.
> The first couple of bug-fix releases are thus, unfortunately, likely
> to be non-trivial as the masses flex the system at scales and using
> workloads that were not known or available to the developers. Its a
> balancing act for most and falling on the side of waiting for a few
> point releases before promoting to production is, I suspect, common.
>
> I support the policy of using caution with regards to new versions. They
> are often thought of as "bleeding edge" for the reason described by
> David G Johnston. The fact that PostgreSQL 10 was only released this
> month is critical and therefore is should not be a production server. It
> should be used as development, or QA, at best.
No, the Betas and RC should have been used in development and QA.
--
Vik Fearing +33 6 46 75 15 36
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Kellerer | 2017-10-18 18:09:51 | Re: Monitoring Tool for PostgreSQL |
Previous Message | Basques, Bob (CI-StPaul) | 2017-10-18 17:46:10 | Re: Monitoring Tool for PostgreSQL |