It's standard procedure for package managers to stop daemons before update
and then start them back up afterward.
On 2/23/21 8:22 AM, Haas, Scott wrote:
Tickling this thread to see if I can get a confirmation of the described
behavior for rpm update via yum.
I do not want to cross-post (but if this is not the correct forum, please
let me know).
Thanks,
Scott
----------------------------------------------------------------------------
*From:* Haas, Scott
*Sent:* Thursday, February 18, 2021 11:23 AM
*To:* pgsql-gene...@postgresql.org <pgsql-gene...@postgresql.org>
*Subject:* yum update for postgresql rpms
RHEL 7.9
PostgreSQL 12 (12.5.1 to 12.6.1)
I am updating RPMs for postgres and was interested to know whether this is
indeed expected behavior for the rpm update:
When the "yum update" is executed, postgresql rpms are updated. It looks
at that point, postgresql (postmaster) processes automatically restart.
In the procedure I was building, I figured I'd need to stop/start postgres
(systemctl stop postgresql-12, systemctl start postgresql-12), but that
doesn't look to be necessary.
I don't recall this automatic postmaster restart occurring a few weeks ago
when I went from 12.4.1 to 12.5.1 - perhaps it did, but I just
stopped/re-started postgres unnecessarily.
Thanks,
Scott
--
Scott Haas
Enterprise Applications
sah...@psu.edu 814-863-3526 https://keybase.io/sah209
--
Angular momentum makes the world go 'round.
