From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: best practice to patch a postgresql version? |
Date: | 2022-12-26 15:54:20 |
Message-ID: | db241bf1-c454-cf80-319d-d2028456c48d@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | qihua wu | 2022-12-27 05:33:06 | Re: best practice to patch a postgresql version? |
Previous Message | Minh Van Le | 2022-12-26 11:03:48 | Sample schemas and data that correlate with all examples in PostgreSQL documentation |