Re: Upgrade procedure
От | rihad |
---|---|
Тема | Re: Upgrade procedure |
Дата | |
Msg-id | 1aa84860-22f1-e85e-02a2-71b1d6a27e46@mail.ru обсуждение исходный текст |
Ответ на | Re: Upgrade procedure (Francisco Olarte <folarte@peoplecall.com>) |
Ответы |
RE: Upgrade procedure
|
Список | pgsql-general |
> >From: rihad <rihad(at)mail(dot)ru> > >> Hi, all. Why is it normally suggested to stop the server, upgrade it, >> then start it? Wouldn't it be easier & quicker to simply upgrade the >> package in-place and restart the service? On OSen that allow >> modification of currently running binaries, which is most Unix OS, M$ >> Windows being a notable exception ) >> > That might be possible on a minor upgrade, but quite probably not on a > major version upgrade. I'm reasonably sure I've read that a major > upgrade *can* change underlying data/structures for tables and other > things. I don't think you want version-X writing to the tables on disk > while version-Y writes a new layout to the same files at the same > time. 😊 > > Why would that matter if the server gets restarted after replacing the binaries? Aren't previous version's binaries "hard-wired" into memory while they are running? AFAIK on FreeBSD at least no attempt is made to stop the corresponding server or restart it when a package is upgraded by pkg(8).
В списке pgsql-general по дате отправления: