Обсуждение: Clarification of documentation detail for upgrading minor version
Hello I have a 9.6.6 system that misses some features. It is installed on a RHEL7 OS. Reading the 9.6 documentation to upgrade I find the following: " 18.6. Upgrading a PostgreSQL Cluster This section discusses how to upgrade your database data from one PostgreSQL release to a newer one. PostgreSQL major versions are represented by the first two digit groups of the version number, e.g., 8.4. PostgreSQL minor versions are represented by the third group of version digits, e.g., 8.4.2 is the second minor release of 8.4. Minor releases never change the internal storage format and are always compatible with earlier and later minor releases of the same major version number, e.g., 8.4.2 is compatible with 8.4, 8.4.1 and 8.4.6. To update between compatible versions, you simply replace the executables while the server is down and restart the server. The data directory remains unchanged — minor upgrades are that simple." Can someone please clarify what actions should be taken for this (see penultimate sentence)? If I install (yum upgrade for example) then I believe all updated files will be updated and that does not seem to be the message in the above. While I can install to a different area (and since I will be using the PGDG repo it WILL be different) I could do this and manually copy the 'bin' directory. However, I would have expected to have to copy the 'libs' directory as well and perhaps others (excluding doc etc.). I will be moving to a 9.6.16 version so that seems to comply with the restrictions mentioned in the documentation (and for the avoidance of good people saying use a later version and do a major upgrade that is not currently possible/feasible). Grateful for any detailed advice on the correct path for the above. Thanks. -- Phil Fisher -- This email is sent on behalf of Northgate Public Services (UK) Limited and its associated companies including Rave Technologies (India) Pvt Limited (together "Northgate Public Services") and is strictly confidential and intended solely for the addressee(s). If you are not the intended recipient of this email you must: (i) not disclose, copy or distribute its contents to any other person nor use its contents in any way or you may be acting unlawfully; (ii) contact Northgate Public Services immediately on +44(0)1442 768445 quoting the name of the sender and the addressee then delete it from your system. Northgate Public Services has taken reasonable precautions to ensure that no viruses are contained in this email, but does not accept any responsibility once this email has been transmitted. You should scan attachments (if any) for viruses. Northgate Public Services (UK) Limited, registered in England and Wales under number 00968498 with a registered address of Peoplebuilding 2, Peoplebuilding Estate, Maylands Avenue, Hemel Hempstead, Hertfordshire, HP2 4NW. Rave Technologies (India) Pvt Limited, registered in India under number U31900MH1998PTC117068 with a registered address of PLOT CS 445, 3 rd Floor, A-wing Madhu Corporate Park Ltd, Pandurang Budhkar Marg, Mumbai -400013
On 1/23/20 3:28 AM, Phil Fisher wrote: > Hello > > I have a 9.6.6 system that misses some features. It is installed on a > RHEL7 OS. Reading the 9.6 documentation to upgrade I find the > following: > > " > > 18.6. Upgrading a PostgreSQL Cluster > > This section discusses how to upgrade your database data from one > PostgreSQL release to a newer one. > > PostgreSQL major versions are represented by the first two digit > groups of the version number, e.g., 8.4. PostgreSQL minor versions are > represented by the third group of version digits, e.g., 8.4.2 is the > second minor release of 8.4. Minor releases never change the internal > storage format and are always compatible with earlier and later minor > releases of the same major version number, e.g., 8.4.2 is compatible > with 8.4, 8.4.1 and 8.4.6. To update between compatible versions, you > simply replace the executables while the server is down and restart > the server. The data directory remains unchanged — minor upgrades are > that simple." > > Can someone please clarify what actions should be taken for this (see > penultimate sentence)? If I install (yum upgrade for example) then I > believe all updated files will be updated and that does not seem to be > the message in the above. While I can install to a different area > (and since I will be using the PGDG repo it WILL be different) I could Are you currently using the PGDG repos? If so then the files will be installed in the same locations. They will just be the new versions. > do this and manually copy the 'bin' directory. However, I would have > expected to have to copy the 'libs' directory as well and perhaps > others (excluding doc etc.). I will be moving to a 9.6.16 version so > that seems to comply with the restrictions mentioned in the > documentation (and for the avoidance of good people saying use a later > version and do a major upgrade that is not currently > possible/feasible). > > Grateful for any detailed advice on the correct path for the above. > Thanks. > -- Adrian Klaver adrian.klaver@aklaver.com
Thanks to Adrian I have managed to get around this issue. Essentially I had to go old school and create a tar archive of the install on another comparable system, copy that around and then install via an untar. (the repo access was not available as it is a server behind many FW and in a secure vDatacentre). The one issue I ended up with (since the system runs under systemd) was that the directory /var/run/postgresql did not exist for some reason and I had to create it as when I tried to restart it there was a failure message. I am not sure if that was an artefact from moving from 9.6.6 to 9.6.16 or not but I mention it in case someone has a similar issue when starting up after the "upgrade". Phil On Thu, 23 Jan 2020 at 15:46, Adrian Klaver <adrian.klaver@aklaver.com> wrote: > > On 1/23/20 3:28 AM, Phil Fisher wrote: > > Hello > > > > I have a 9.6.6 system that misses some features. It is installed on a > > RHEL7 OS. Reading the 9.6 documentation to upgrade I find the > > following: > > > > " > > > > 18.6. Upgrading a PostgreSQL Cluster > > > > This section discusses how to upgrade your database data from one > > PostgreSQL release to a newer one. > > > > PostgreSQL major versions are represented by the first two digit > > groups of the version number, e.g., 8.4. PostgreSQL minor versions are > > represented by the third group of version digits, e.g., 8.4.2 is the > > second minor release of 8.4. Minor releases never change the internal > > storage format and are always compatible with earlier and later minor > > releases of the same major version number, e.g., 8.4.2 is compatible > > with 8.4, 8.4.1 and 8.4.6. To update between compatible versions, you > > simply replace the executables while the server is down and restart > > the server. The data directory remains unchanged — minor upgrades are > > that simple." > > > > Can someone please clarify what actions should be taken for this (see > > penultimate sentence)? If I install (yum upgrade for example) then I > > believe all updated files will be updated and that does not seem to be > > the message in the above. While I can install to a different area > > (and since I will be using the PGDG repo it WILL be different) I could > > Are you currently using the PGDG repos? > > If so then the files will be installed in the same locations. They will > just be the new versions. > > > do this and manually copy the 'bin' directory. However, I would have > > expected to have to copy the 'libs' directory as well and perhaps > > others (excluding doc etc.). I will be moving to a 9.6.16 version so > > that seems to comply with the restrictions mentioned in the > > documentation (and for the avoidance of good people saying use a later > > version and do a major upgrade that is not currently > > possible/feasible). > > > > Grateful for any detailed advice on the correct path for the above. > > Thanks. > > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com -- Phil Fisher DevOPS/Linux Engineer T: +44 1473 731230 (office) i2N Ltd A NEC Company Unit 3 Appletree Business Centre Folly Lane Copdock Suffolk IP8 3JQ Tel: +44 (0)1429 558255 (Hartlepool Service Desk) Please consider the environment before printing this email -- This email is sent on behalf of Northgate Public Services (UK) Limited and its associated companies including Rave Technologies (India) Pvt Limited (together "Northgate Public Services") and is strictly confidential and intended solely for the addressee(s). If you are not the intended recipient of this email you must: (i) not disclose, copy or distribute its contents to any other person nor use its contents in any way or you may be acting unlawfully; (ii) contact Northgate Public Services immediately on +44(0)1442 768445 quoting the name of the sender and the addressee then delete it from your system. Northgate Public Services has taken reasonable precautions to ensure that no viruses are contained in this email, but does not accept any responsibility once this email has been transmitted. You should scan attachments (if any) for viruses. Northgate Public Services (UK) Limited, registered in England and Wales under number 00968498 with a registered address of Peoplebuilding 2, Peoplebuilding Estate, Maylands Avenue, Hemel Hempstead, Hertfordshire, HP2 4NW. Rave Technologies (India) Pvt Limited, registered in India under number U31900MH1998PTC117068 with a registered address of PLOT CS 445, 3 rd Floor, A-wing Madhu Corporate Park Ltd, Pandurang Budhkar Marg, Mumbai -400013
On 1/24/20 12:27 AM, Phil Fisher wrote: Please reply to list also. Ccing list. > Hi Adrian > > no the version currently installed came from a RHEL repo I believe so > binaries etc. are not in same place, /usr/local IIRC. > > If there is a an easy/simple way of describing an approach it would be > good as I am being pressured to complete this work today. > (While understanding that is not how it works ...) > > Phil > > On Thu, 23 Jan 2020 at 15:46, Adrian Klaver <adrian.klaver@aklaver.com> wrote: >> >> On 1/23/20 3:28 AM, Phil Fisher wrote: >>> Hello >>> >>> I have a 9.6.6 system that misses some features. It is installed on a >>> RHEL7 OS. Reading the 9.6 documentation to upgrade I find the >>> following: >>> >>> " >>> >>> 18.6. Upgrading a PostgreSQL Cluster >>> >>> This section discusses how to upgrade your database data from one >>> PostgreSQL release to a newer one. >>> >>> PostgreSQL major versions are represented by the first two digit >>> groups of the version number, e.g., 8.4. PostgreSQL minor versions are >>> represented by the third group of version digits, e.g., 8.4.2 is the >>> second minor release of 8.4. Minor releases never change the internal >>> storage format and are always compatible with earlier and later minor >>> releases of the same major version number, e.g., 8.4.2 is compatible >>> with 8.4, 8.4.1 and 8.4.6. To update between compatible versions, you >>> simply replace the executables while the server is down and restart >>> the server. The data directory remains unchanged — minor upgrades are >>> that simple." >>> >>> Can someone please clarify what actions should be taken for this (see >>> penultimate sentence)? If I install (yum upgrade for example) then I >>> believe all updated files will be updated and that does not seem to be >>> the message in the above. While I can install to a different area >>> (and since I will be using the PGDG repo it WILL be different) I could >> >> Are you currently using the PGDG repos? >> >> If so then the files will be installed in the same locations. They will >> just be the new versions. >> >>> do this and manually copy the 'bin' directory. However, I would have >>> expected to have to copy the 'libs' directory as well and perhaps >>> others (excluding doc etc.). I will be moving to a 9.6.16 version so >>> that seems to comply with the restrictions mentioned in the >>> documentation (and for the avoidance of good people saying use a later >>> version and do a major upgrade that is not currently >>> possible/feasible). >>> >>> Grateful for any detailed advice on the correct path for the above. >>> Thanks. >>> >> >> >> -- >> Adrian Klaver >> adrian.klaver@aklaver.com > > > -- Adrian Klaver adrian.klaver@aklaver.com
On 1/24/20 6:40 AM, Phil Fisher wrote: > Thanks to Adrian I have managed to get around this issue. Essentially > I had to go old school and create a tar archive of the install on > another comparable system, copy that around and then install via an > untar. (the repo access was not available as it is a server behind > many FW and in a secure vDatacentre). So did you copy a RHEL repo install or a PGDG repo one? > The one issue I ended up with (since the system runs under systemd) > was that the directory /var/run/postgresql did not exist for some > reason and I had to create it as when I tried to restart it there was > a failure message. I am not sure if that was an artefact from moving > from 9.6.6 to 9.6.16 or not but I mention it in case someone has a > similar issue when starting up after the "upgrade". > > Phil > > On Thu, 23 Jan 2020 at 15:46, Adrian Klaver <adrian.klaver@aklaver.com> wrote: >> >> On 1/23/20 3:28 AM, Phil Fisher wrote: >>> Hello >>> >>> I have a 9.6.6 system that misses some features. It is installed on a >>> RHEL7 OS. Reading the 9.6 documentation to upgrade I find the >>> following: >>> >>> " >>> >>> 18.6. Upgrading a PostgreSQL Cluster >>> >>> This section discusses how to upgrade your database data from one >>> PostgreSQL release to a newer one. >>> >>> PostgreSQL major versions are represented by the first two digit >>> groups of the version number, e.g., 8.4. PostgreSQL minor versions are >>> represented by the third group of version digits, e.g., 8.4.2 is the >>> second minor release of 8.4. Minor releases never change the internal >>> storage format and are always compatible with earlier and later minor >>> releases of the same major version number, e.g., 8.4.2 is compatible >>> with 8.4, 8.4.1 and 8.4.6. To update between compatible versions, you >>> simply replace the executables while the server is down and restart >>> the server. The data directory remains unchanged — minor upgrades are >>> that simple." >>> >>> Can someone please clarify what actions should be taken for this (see >>> penultimate sentence)? If I install (yum upgrade for example) then I >>> believe all updated files will be updated and that does not seem to be >>> the message in the above. While I can install to a different area >>> (and since I will be using the PGDG repo it WILL be different) I could >> >> Are you currently using the PGDG repos? >> >> If so then the files will be installed in the same locations. They will >> just be the new versions. >> >>> do this and manually copy the 'bin' directory. However, I would have >>> expected to have to copy the 'libs' directory as well and perhaps >>> others (excluding doc etc.). I will be moving to a 9.6.16 version so >>> that seems to comply with the restrictions mentioned in the >>> documentation (and for the avoidance of good people saying use a later >>> version and do a major upgrade that is not currently >>> possible/feasible). >>> >>> Grateful for any detailed advice on the correct path for the above. >>> Thanks. >>> >> >> >> -- >> Adrian Klaver >> adrian.klaver@aklaver.com > > > -- Adrian Klaver adrian.klaver@aklaver.com