Re: Move base directory to different location - Mailing list pgsql-admin

From David G. Johnston
Subject Re: Move base directory to different location
Date
Msg-id CAKFQuwb7xf+Y27mL0+3474aH+BwdpAHEZBtdSchF=E-2xt3Ruw@mail.gmail.com
Whole thread Raw
In response to Re: Move base directory to different location  (Paul Förster <paul.foerster@gmail.com>)
Responses Re: Move base directory to different location  (Paul Förster <paul.foerster@gmail.com>)
List pgsql-admin
On Thu, Nov 26, 2020 at 7:56 AM Paul Förster <paul.foerster@gmail.com> wrote:
Hi David,

> On 26. Nov, 2020, at 15:49, David G. Johnston <david.g.johnston@gmail.com> wrote:
>
> But the comment was to full upgrade, not just update.  The OP didn’t state which patch release but is running version 10.

IMHO, the same applies to major versions.

Also, it's IMHO easier to get problems fixed if you use a current version because developers don't have to check old code but can work and test with a current version. And if you have a real problem, then you most likely won't get a backward compatible patch. It will rather be fixed in the next release.

As always, after an update/upgrade is before an update/upgrade. :-)


IMHO, that is all a load of nonsense.

5 years of support is just that, and it is done quite well - the trade-off of upgrading only in order to make the developer's lives marginally easier isn't a good one.  Plus, they have to check the old code anyway since most likely such fixes will need to be back-patched.

The few behavior changes that don't get back-patched support not upgrading to the newest release ASAP, not doing so sooner.

And if a such non-batchpatch-able fix is recently discovered it won't be available until the next major release anyway, so even those running cutting-edge wouldn't see a difference compared to running an prior version.

David J.

pgsql-admin by date:

Previous
From: Paul Förster
Date:
Subject: Re: current log file removal
Next
From: Paul Förster
Date:
Subject: Re: Move base directory to different location