From: | Sébastien Lardière <sebastien(at)lardiere(dot)net> |
---|---|
To: | pgsql-pkg-debian(at)lists(dot)postgresql(dot)org |
Subject: | Upgrade packages - Control Instance |
Date: | 2019-05-21 09:58:15 |
Message-ID: | f4efadb7-ecb0-ba1f-383b-b9a38f988f87@lardiere.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-pkg-debian |
Hi,
I'm looking for a way to control the way instances are restarted when
`apt upgrade` run => sometime, if there is a large number of packages to
upgrade, the instances is stopped for a long time.
In the past, I used to use start.conf with manual setting, then restart
"manually" after the upgrade, which give downtime as short as I can ;
but now, it seems that "stop" is always done, even when i disable the
systemd service (ok,it is weird to disable service and to want the
service up, I know ) => I think that the fact we can't forbid the stop
is not correct.
I know that I can hold the postgresql packages, run the big `apt
upgrade` then unhold packages and do the postgresql upgrade, but I think
it's a more complicated way to do it.
Am I miss something ?
Am I the only one disturbed by the fact that we can't forbid stop ?
regards,
--
Sébastien
From | Date | Subject | |
---|---|---|---|
Next Message | Christoph Berg | 2019-05-21 10:09:40 | Re: Upgrade packages - Control Instance |
Previous Message | apt.postgresql.org Repository Update | 2019-05-20 14:19:42 | pg-partman updated to version 4.1.0-1.pgdg+1 |