From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: best practice to patch a postgresql version?
Date: Mon, 26 Dec 2022 09:54:20 -0600
Message-ID: <db241bf1-c454-cf80-319d-d2028456c48d@gmail.com> (raw)
In-Reply-To: <CAPoYtoLOipP1fUHhAcZYc_D-YE-nreFzMas=F0U_620QsjGMLA@mail.gmail.com>
References: <CAPoYtoLOipP1fUHhAcZYc_D-YE-nreFzMas=F0U_620QsjGMLA@mail.gmail.com>
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.
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: <db241bf1-c454-cf80-319d-d2028456c48d@gmail.com>
References: <CAPoYtoLOipP1fUHhAcZYc_D-YE-nreFzMas=F0U_620QsjGMLA@mail.gmail.com> <db241bf1-c454-cf80-319d-d2028456c48d@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