pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: best practice to patch a postgresql version?
Date: Fri, 6 Jan 2023 04:21:26 -0600
Message-ID: <ff521f81-a078-ae5b-a9a0-4d06ee8f6294@gmail.com> (raw)
In-Reply-To: <802bc09b7fa07f9fd1d7d8907a4b988f42af8d95.camel@cybertec.at>
References: <CAPoYtoLOipP1fUHhAcZYc_D-YE-nreFzMas=F0U_620QsjGMLA@mail.gmail.com>
	<db241bf1-c454-cf80-319d-d2028456c48d@gmail.com>
	<CAPoYtoJYwQ4Mxou3w0KSsKRSdJyuJHps5rKfW5u22XG2rwOSwQ@mail.gmail.com>
	<0a9d2078-1900-1e0c-be96-f4d5bdc6df22@gmail.com>
	<802bc09b7fa07f9fd1d7d8907a4b988f42af8d95.camel@cybertec.at>

On 1/5/23 23:43, Laurenz Albe wrote:
> On Tue, 2022-12-27 at 00:48 -0600, Ron wrote:
>> If it really is a critical production database, you will have a CAT/UAT (customer/user acceptance testing)
>> server on which you rigorously run regression tests on a point release for a month before updating the production server.
>>
>> Otherwise, it's a hope-and-pray database.
> No, that is wrong.
>
> You should not test your application when you install a minor update.  The reason is that
> few people are willing to test the application thoroughly every few months, and the outcome
> is that minor releases are *not* applied regularly, as they should be.
>
> You are supposed to trust PostgreSQL development that they don't introduce new bugs.
> Sure, this can happen, even though all possible care is taken with backpatches.  I have
> seen it happen once or twice in the 15+ years I have been dealing with PostgreSQL.
> In that case, a new minor release will come out soon afterwards.

It's absolutely standard practice "in the enterprise" to install the latest 
patch on the UAT (and possibly Dev and Staging) servers before rolling out 
to production.

Have I aver seen a problem in Postgresql?  No.  But I've seen problems with 
other RDBMSs.  If a problem did happen, and caused for example, an important 
report to suddenly take 3 hours instead of 3 minutes, the client will 
scream; there might even be SLA penalties.

Thus, we're cautious with "critical production databases".

-- 
Born in Arizona, moved to Babylonia.





view thread (8+ messages)

Message-ID: <ff521f81-a078-ae5b-a9a0-4d06ee8f6294@gmail.com>
Permalink:  ../ff521f81-a078-ae5b-a9a0-4d06ee8f6294@gmail.com/
Also on:    postgresql.org/message-id/ff521f81-a078-ae5b-a9a0-4d06ee8f6294@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: ronljohnsonjr@gmail.com
  Subject: Re: best practice to patch a postgresql version?
  In-Reply-To: <ff521f81-a078-ae5b-a9a0-4d06ee8f6294@gmail.com>
  References: <CAPoYtoLOipP1fUHhAcZYc_D-YE-nreFzMas=F0U_620QsjGMLA@mail.gmail.com> <db241bf1-c454-cf80-319d-d2028456c48d@gmail.com> <CAPoYtoJYwQ4Mxou3w0KSsKRSdJyuJHps5rKfW5u22XG2rwOSwQ@mail.gmail.com> <0a9d2078-1900-1e0c-be96-f4d5bdc6df22@gmail.com> <802bc09b7fa07f9fd1d7d8907a4b988f42af8d95.camel@cybertec.at> <ff521f81-a078-ae5b-a9a0-4d06ee8f6294@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox