'Re: 20220226-Clarification regarding delay time of PostgeSQL starting up'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: 20220226-Clarification regarding delay time of PostgeSQL starting up
From:       Mladen Gogala <gogala.mladen () gmail ! com>
Date:       2022-02-26 21:13:13
Message-ID: 5cdf78d3-8312-2d8f-5b49-84992d443076 () gmail ! com
[Download RAW message or body]

On 2/26/22 13:34, Techsupport wrote:
> Thanks for your reply.
> Is it a good practice to upgrade / update database on production on every
> year ?

No, it is not a good practice. Database upgrade must be treated as a 
project which will result in non-negligible downtime. You should upgrade 
to the new version if the new version brings about features that you 
need. Here is the list of new features, introduced in the PostgreSQL 14:

https://www.postgresql.org/docs/14/release-14.html#id-1.11.6.7.5

If you need any of the listed features, you should upgrade. If not, you 
can safely skip the release. Upgrade is something that has business 
repercussions, inconveniences the database users and should be subjected 
to the same cost-benefit analysis as every other major IT move. Upgrade 
policy is usually set by the management, not by the DBA, much to chagrin 
of the DBA personnel. I used to be a DBA for a very long time and I know.

-- 
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
https://dbwhisperer.wordpress.com

[Attachment #3 (text/html)]

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 2/26/22 13:34, Techsupport wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:002001d82b3f$79fc6df0$6df549d0$@sardonyx.in">
      <pre class="moz-quote-pre" wrap="">Thanks for your reply.
Is it a good practice to upgrade / update database on production on every
year ?</pre>
    </blockquote>
    <p>No, it is not a good practice. Database upgrade must be treated
      as a project which will result in non-negligible downtime. You
      should upgrade to the new version if the new version brings about
      features that you need. Here is the list of new features,
      introduced in the PostgreSQL 14:</p>
    <p><a class="moz-txt-link-freetext" \
href="https://www.postgresql.org/docs/14/release-14.html#id-1.11.6.7.5">https://www.postgresql.org/docs/14/release-14.html#id-1.11.6.7.5</a></p>
  <p>If you need any of the listed features, you should upgrade. If
      not, you can safely skip the release. Upgrade is something that
      has business repercussions, inconveniences the database users and
      should be subjected to the same cost-benefit analysis as every
      other major IT move. Upgrade policy is usually set by the
      management, not by the DBA, much to chagrin of the DBA personnel.
      I used to be a DBA for a very long time and I know.<br>
    </p>
    <pre class="moz-signature" cols="72">-- 
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
<a class="moz-txt-link-freetext" \
href="https://dbwhisperer.wordpress.com">https://dbwhisperer.wordpress.com</a> </pre>
  </body>
</html>



[prev in list] [next in list] [prev in thread] [next in thread]
Configure | About | News | Add a list | Sponsored by KoreLogic