From: | rihad <rihad(at)mail(dot)ru> |
---|---|
To: | Kevin Brannen <KBrannen(at)efji(dot)com> |
Cc: | pgsql-general General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Upgrade procedure |
Date: | 2019-10-31 05:27:29 |
Message-ID: | 1aa84860-22f1-e85e-02a2-71b1d6a27e46@mail.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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).
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2019-10-31 06:57:43 | Re: Getting following error in using cursor to fetch the records from a large table in c language |
Previous Message | M Tarkeshwar Rao | 2019-10-31 05:21:06 | Can you please suggest how to configure hot_standby_feedback? |