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: Tue, 27 Dec 2022 00:48:49 -0600
Message-ID: <0a9d2078-1900-1e0c-be96-f4d5bdc6df22@gmail.com> (raw)
In-Reply-To: <CAPoYtoJYwQ4Mxou3w0KSsKRSdJyuJHps5rKfW5u22XG2rwOSwQ@mail.gmail.com>
References: <CAPoYtoLOipP1fUHhAcZYc_D-YE-nreFzMas=F0U_620QsjGMLA@mail.gmail.com>
	<db241bf1-c454-cf80-319d-d2028456c48d@gmail.com>
	<CAPoYtoJYwQ4Mxou3w0KSsKRSdJyuJHps5rKfW5u22XG2rwOSwQ@mail.gmail.com>

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.

On 12/26/22 23:33, qihua wu wrote:
> Thanks Ron,
>
> But on a critical production database, we need to cut down the downtime as 
> much as possible. If just remove a version, and then install a new 
> version, both of them need a downtime. If we can install several versions 
> on different location, switching version will have a shorter downtime: 
> just stop the old version and start using the new binary, and we have no 
> downtime when remove/install a new version.
>
> On Mon, Dec 26, 2022 at 11:54 PM Ron <ronljohnsonjr@gmail.com> wrote:
>
>     Just downgrade the packages if you need to revert to a previous version.
>
>     Remove the 14*.5* package, and install the 14*.4* package (because no
>     one's crazy enough to start with 14.0 in December 2022).  You'll have
>     to explicitly specify the version number.
>
>     On 12/26/22 03:29, qihua wu wrote:
>>     We are planning to use postgresq on production, but there is one
>>     question about how to patch a db. We don't want to overwrite the old
>>     version directly, so that we can rollback if the new version has
>>     issues. So we want to install it a different location such as
>>     /home/postgres/14.1 for version 14.1 (all binary should be under 14.1
>>     or sub-fold of 14.1) and /home/postgres/14.0 for 14.0, in this way we
>>     can easily switch between different versions. But apt install on
>>     ubuntu doesn't have the option for a customized location. So what's
>>     the best practice to patch postgres?
>
>     -- 
>     Born in Arizona, moved to Babylonia.
>

-- 
Born in Arizona, moved to Babylonia.

view thread (8+ messages)  latest in thread

Message-ID: <0a9d2078-1900-1e0c-be96-f4d5bdc6df22@gmail.com>
Permalink:  ../0a9d2078-1900-1e0c-be96-f4d5bdc6df22@gmail.com/
Also on:    postgresql.org/message-id/0a9d2078-1900-1e0c-be96-f4d5bdc6df22@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: <0a9d2078-1900-1e0c-be96-f4d5bdc6df22@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>

* 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