Automatic restart while upgrade

Started by Stéphane Schildknechtabout 13 years ago3 messagesgeneral
Jump to latest
#1Stéphane Schildknecht
stephane.schildknecht@postgres.fr

Hello,

I discovered that while upgrading PostgreSQL binaries through 'yum
update', with PGDG RPMs, the service is automatically restarted.

ISTM that this was not the case before 9.2.

May you confirm that this is a new behaviour appearing in 9.2?

Is it intended, and is there a way to prevent the automatic restart?

Thanks in advance.

Best regards,
Stéphane Schildknecht
http://loxodata.com

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Stéphane Schildknecht (#1)
Re: Automatic restart while upgrade

stephane.schildknecht@postgres.fr writes:

I discovered that while upgrading PostgreSQL binaries through 'yum
update', with PGDG RPMs, the service is automatically restarted.

ISTM that this was not the case before 9.2.

I dunno whether Devrim's packages acted that way before 9.2, but
this is standard behavior for all services in Red Hat environments,
and always has been. Otherwise an intended security patch, for
instance, might not be activated till long past when the admin
thought he'd installed it.

regards, tom lane

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

#3Gavin Flower
GavinFlower@archidevsys.co.nz
In reply to: Tom Lane (#2)
Re: Automatic restart while upgrade

On 13/04/13 02:08, Tom Lane wrote:

stephane.schildknecht@postgres.fr writes:

I discovered that while upgrading PostgreSQL binaries through 'yum
update', with PGDG RPMs, the service is automatically restarted.
ISTM that this was not the case before 9.2.

I dunno whether Devrim's packages acted that way before 9.2, but
this is standard behavior for all services in Red Hat environments,
and always has been. Otherwise an intended security patch, for
instance, might not be activated till long past when the admin
thought he'd installed it.

regards, tom lane

As far as I can recall: that is standard yum behaviour for all packages
updated, rather than installed, for over 10 years, I first stared using
Red Hat, now Fedora, in about 2001.

Cheers,
Gavin