RE: Upgrade procedure - Mailing list pgsql-general

From Kevin Brannen
Subject RE: Upgrade procedure
Date
Msg-id DM6PR19MB34512033DC48473B1F40731BA4600@DM6PR19MB3451.namprd19.prod.outlook.com
Whole thread Raw
In response to Upgrade procedure  (rihad <rihad@mail.ru>)
List pgsql-general
>From: rihad <rihad@mail.ru>

>Hi, all. Why is it normally suggested to stop the server, upgrade it, then start it? Wouldn't it be easier & quicker
tosimply 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
readthat a major upgrade *can* change underlying data/structures for tables and other things. I don't think you want
version-Xwriting to the tables on disk while version-Y writes a new layout to the same files at the same time. 😊
 

As always, see the fine manual, especially the part on upgrades and release notes.

Kevin

This e-mail transmission, and any documents, files or previous e-mail messages attached to it, may contain confidential
information.If you are not the intended recipient, or a person responsible for delivering it to the intended recipient,
youare hereby notified that any disclosure, distribution, review, copy or use of any of the information contained in or
attachedto this message is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately
notifyus by reply e-mail, and destroy the original transmission and its attachments without reading them or saving them
todisk. Thank you.
 

pgsql-general by date:

Previous
From: Andres Freund
Date:
Subject: Re: Automatically parsing in-line composite types
Next
From: Mitar
Date:
Subject: Re: Automatically parsing in-line composite types