HOWTO: PostgreSQL version upgrade - История изменений

Uscld2 в 06:11, 21 августа 2025

2025-08-21T06:11:43Z

Uscld2 в 12:13, 20 августа 2025

2025-08-20T12:13:47Z

← Предыдущая версия		Версия от 12:13, 20 августа 2025
Строка 1:		Строка 1:
	[[HOWTO:_PostgreSQL_version_upgrade\|en]] \| [[HOWTO:_Обновление_версии_PostgreSQL\|ru]]		[[HOWTO:_PostgreSQL_version_upgrade\|en]] \| [[HOWTO:_Обновление_версии_PostgreSQL\|ru]]

	This section describes how to upgrade PostgreSQL ''between major versions'' (e.g., from version 11 to version 16).		This section describes how to upgrade PostgreSQL ''between major versions'' (e.g., from version 11 to version 17).

	Upgrading within a version (e.g., from version 16.1 to version 16.2) ''is automatic and requires no additional steps.''		Upgrading within a version (e.g., from version 17.1 to version 17.2) ''is automatic and requires no additional steps.''

	'''We recommend reading the official upgrade instructions''' at [https://www.postgresql.org/docs/current/upgrading.html postgresql.org].		'''We recommend reading the official upgrade instructions''' at [https://www.postgresql.org/docs/current/upgrading.html postgresql.org].
Строка 11:		Строка 11:
	A [https://www.postgresql.org/docs/current/glossary.html database cluster] in PostgreSQL is a server instance together with all the maintained databases, not a distributed system as it may seem.		A [https://www.postgresql.org/docs/current/glossary.html database cluster] in PostgreSQL is a server instance together with all the maintained databases, not a distributed system as it may seem.

	The following example will show how to upgrade a database cluster from version 11 to version 16 using the tools in the '''postgresql-common''' package.		The following example will show how to upgrade a database cluster from version 11 to version 17 using the tools in the '''postgresql-common''' package.

	== Upgrade order ==		== Upgrade order ==
Строка 17:		Строка 17:
	# Upgrade the current version of postgresql within the major version (e.g., from 11.5 to 11.22).		# Upgrade the current version of postgresql within the major version (e.g., from 11.5 to 11.22).
	# Upgrade the postgis extension to the latest version (e.g. from 2.5 to 3.3.4). Also be sure to update the extension in the database itself.		# Upgrade the postgis extension to the latest version (e.g. from 2.5 to 3.3.4). Also be sure to update the extension in the database itself.
	# Install a new version of postgresql without uninstalling the old one (e.g. 16.1).		# Install a new version of postgresql without uninstalling the old one (e.g. 17.1).
	# Make a backup copy of the database and settings		# Make a backup copy of the database and settings
	# Delete the database cluster created automatically by the script when installing the new version		# Delete the database cluster created automatically by the script when installing the new version
Строка 44:		Строка 44:
	sudo -u postgres psql -d userside -A -t -c "SELECT VERSION()"		sudo -u postgres psql -d userside -A -t -c "SELECT VERSION()"
	sudo -u postgres psql -d userside -A -t -c "SELECT PostGIS_full_version()"		sudo -u postgres psql -d userside -A -t -c "SELECT PostGIS_full_version()"
			sudo -u postgres psql -d postgres -A -t -c "SELECT PostGIS_full_version()"

	sudo apt update		sudo apt update
Строка 51:		Строка 52:

	=== Upgrade the postgis extension to the latest version ===		=== Upgrade the postgis extension to the latest version ===
	Be sure to upgrade the extension in the database as well!		Be sure to upgrade the extension in the database as well! If the previous commands also showed the presence of an extension in the postgres database, then postgis needs to be updated for it as well.
	<pre>		<pre>
	sudo apt install -y postgresql-11-postgis-3		sudo apt install -y postgresql-11-postgis-3
Строка 57:		Строка 58:
	sudo -u postgres psql -d userside -A -t -c "ALTER EXTENSION postgis UPDATE"		sudo -u postgres psql -d userside -A -t -c "ALTER EXTENSION postgis UPDATE"
	sudo -u postgres psql -d userside -A -t -c "SELECT PostGIS_full_version()"		sudo -u postgres psql -d userside -A -t -c "SELECT PostGIS_full_version()"

			sudo -u postgres psql -d postgres -A -t -c "ALTER EXTENSION postgis UPDATE"
			sudo -u postgres psql -d postgres -A -t -c "SELECT PostGIS_full_version()"
	</pre>		</pre>

	=== Install a new version of postgresql without uninstalling the old one ===		=== Install a new version of postgresql without uninstalling the old one ===
	<pre>		<pre>
	sudo apt install -y postgresql-16 postgresql-16-postgis-3		sudo apt install -y postgresql-17 postgresql-17-postgis-3
	</pre>		</pre>

Строка 82:		Строка 86:
	Ver Cluster Port Status Owner Data directory Log file		Ver Cluster Port Status Owner Data directory Log file
	11 main 5432 online postgres /var/lib/postgresql/11/main /var/log/postgresql/postgresql-11.log		11 main 5432 online postgres /var/lib/postgresql/11/main /var/log/postgresql/postgresql-11.log
	16 main 5433 online postgres /var/lib/postgresql/16/main /var/log/postgresql/postgresql-16.log		17 main 5433 online postgres /var/lib/postgresql/17/main /var/log/postgresql/postgresql-17.log
	</pre>		</pre>
	The 16/main cluster was created automatically by the postgresql installation script. It needs to be stopped and deleted.		The 17/main cluster was created automatically by the postgresql installation script. It needs to be stopped and deleted.
	<pre>		<pre>
	sudo pg_dropcluster 16 main --stop		sudo pg_dropcluster 17 main --stop
	</pre>		</pre>
	Running the <code>pg_lsclusters</code> command again should show that you have one '''11/main''' cluster left.		Running the <code>pg_lsclusters</code> command again should show that you have one '''11/main''' cluster left.
Строка 103:		Строка 107:
	Ver Cluster Port Status Owner Data directory Log file		Ver Cluster Port Status Owner Data directory Log file
	11 main 5433 down postgres /var/lib/postgresql/11/main /var/log/postgresql/postgresql-11.log		11 main 5433 down postgres /var/lib/postgresql/11/main /var/log/postgresql/postgresql-11.log
	16 main 5432 online postgres /var/lib/postgresql/16/main /var/log/postgresql/postgresql-16.log		17 main 5432 online postgres /var/lib/postgresql/17/main /var/log/postgresql/postgresql-17.log
	</pre>		</pre>
	Start the postgres service		Start the postgres service
Строка 116:		Строка 120:
	sudo -u postgres psql -d userside -A -t -c "SELECT PostGIS_full_version()"		sudo -u postgres psql -d userside -A -t -c "SELECT PostGIS_full_version()"
	</pre>		</pre>
	You should see version 16 of postgresql and version 3.3.4 of postgis. Maybe by the time you read these lines, the postgis version will be newer.		You should see version 17 of postgresql and version 3.3.4 of postgis. Maybe by the time you read these lines, the postgis version will be newer.

	Now start the FPM service and go to USERSIDE through your browser.		Now start the FPM service and go to USERSIDE through your browser.

Uscld2: /* Step-by-step instructions */

2024-12-25T19:01:17Z

Step-by-step instructions

← Предыдущая версия		Версия от 19:01, 25 декабря 2024
Строка 97:		Строка 97:
	Start the '''11/main''' database cluster upgrade process using the <code>pg_upgradecluster</code> utility from the postgresql-common package. This may take a lot of time and disc space.		Start the '''11/main''' database cluster upgrade process using the <code>pg_upgradecluster</code> utility from the postgresql-common package. This may take a lot of time and disc space.
	<pre>		<pre>
	sudo pg_upgradecluster ~~-m upgrade~~ 11 main		sudo pg_upgradecluster 11 main
	</pre>		</pre>
	After the upgrade operation is complete, you will see the new state of the clusters (the old version should be in '''down''' mode):		After the upgrade operation is complete, you will see the new state of the clusters (the old version should be in '''down''' mode):

Uscld2: /* Perform an upgrade of the old version database cluster to the new version database cluster */

2024-01-24T06:59:27Z

Perform an upgrade of the old version database cluster to the new version database cluster

← Предыдущая версия		Версия от 06:59, 24 января 2024
Строка 99:		Строка 99:
	sudo pg_upgradecluster -m upgrade 11 main		sudo pg_upgradecluster -m upgrade 11 main
	</pre>		</pre>
	After the ~~procedure~~ is complete, ~~start~~ the ~~postgres service~~		After the upgrade operation is complete, you will see the new state of the clusters (the old version should be in '''down''' mode):
	~~<pre>~~
	~~sudo systemctl start postgresql~~
	~~</pre>~~
	~~Check what your database~~ clusters ~~look like~~
	~~<pre>~~
	~~sudo pg_lsclusters~~
	~~</pre>~~
	~~The~~ old version ~~must~~ be in '''down''' mode~~. The output of the command will be approximately as follows~~:
	<pre>		<pre>
	Ver Cluster Port Status Owner Data directory Log file		Ver Cluster Port Status Owner Data directory Log file
	11 main 5433 down postgres /var/lib/postgresql/11/main /var/log/postgresql/postgresql-11.log		11 main 5433 down postgres /var/lib/postgresql/11/main /var/log/postgresql/postgresql-11.log
	16 main 5432 online postgres /var/lib/postgresql/16/main /var/log/postgresql/postgresql-16.log		16 main 5432 online postgres /var/lib/postgresql/16/main /var/log/postgresql/postgresql-16.log
			</pre>
			Start the postgres service
			<pre>
			sudo systemctl start postgresql
	</pre>		</pre>

Uscld2 в 06:36, 23 января 2024

2024-01-23T06:36:52Z

← Предыдущая версия		Версия от 06:36, 23 января 2024
Строка 5:		Строка 5:
	Upgrading within a version (e.g., from version 16.1 to version 16.2) ''is automatic and requires no additional steps.''		Upgrading within a version (e.g., from version 16.1 to version 16.2) ''is automatic and requires no additional steps.''

	'''We recommend reading the official upgrade instructions''' at [https://www.postgresql.org/docs/16/upgrading.html postgresql.org].		'''We recommend reading the official upgrade instructions''' at [https://www.postgresql.org/docs/current/upgrading.html postgresql.org].

	In the Debian distribution and those based on it, there is a package [https://packages.debian.org/sid/postgresql-common postgresql-common] that is installed automatically when the PostgreSQL package is installed. Postgresql-common includes tools to simplify working with PostgreSQL database clusters. This includes updating database clusters.		In the Debian distribution and those based on it, there is a package [https://packages.debian.org/sid/postgresql-common postgresql-common] that is installed automatically when the PostgreSQL package is installed. Postgresql-common includes tools to simplify working with PostgreSQL database clusters. This includes updating database clusters.

	A ~~database cluster (~~[https://www.postgresql.org/docs/16/glossary.html ~~Database~~ cluster]) in PostgreSQL is a server instance together with all the maintained databases, not a distributed system as it may seem.		A [https://www.postgresql.org/docs/current/glossary.html database cluster] in PostgreSQL is a server instance together with all the maintained databases, not a distributed system as it may seem.

	The following example will show how to upgrade a database cluster from version 11 to version 16 using the tools in the '''postgresql-common''' package.		The following example will show how to upgrade a database cluster from version 11 to version 16 using the tools in the '''postgresql-common''' package.

N.Skrypnik в 17:37, 22 января 2024

2024-01-22T17:37:38Z

← Предыдущая версия		Версия от 17:37, 22 января 2024
Строка 52:		Строка 52:
	=== Upgrade the postgis extension to the latest version ===		=== Upgrade the postgis extension to the latest version ===
	Be sure to upgrade the extension in the database as well!		Be sure to upgrade the extension in the database as well!
			<pre>
			sudo apt install -y postgresql-11-postgis-3

			sudo -u postgres psql -d userside -A -t -c "ALTER EXTENSION postgis UPDATE"
			sudo -u postgres psql -d userside -A -t -c "SELECT PostGIS_full_version()"
			</pre>

			=== Install a new version of postgresql without uninstalling the old one ===
			<pre>
			sudo apt install -y postgresql-16 postgresql-16-postgis-3
			</pre>

			=== Make a backup of the database and settings ===
			The number 11 in the filename is the PostgreSQL version number to which this backup belongs.
			<pre>
			sudo -u postgres pg_dump --no-acl -Fp -Z 5 userside --file=/backup/userside_emergency_11.sql.gz
			sudo -u postgres pg_dump --no-acl -Fc userside --file=/backup/userside_emergency_11.dump
			sudo tar czf /backup/postgres_config_emergency_11.tgz -C /etc/postgresql/11/main .
			</pre>
			The /backup directory must exist and must be writable by all users.

			=== Remove the database cluster created automatically by the script when installing a new version ===
			Using the <code>pg_lsclusters</code> utility from postgresql-common, see what your database clusters look like:
			<pre>
			sudo pg_lsclusters
			</pre>
			The output of the command will be approximately as follows:
			<pre>
			Ver Cluster Port Status Owner Data directory Log file
			11 main 5432 online postgres /var/lib/postgresql/11/main /var/log/postgresql/postgresql-11.log
			16 main 5433 online postgres /var/lib/postgresql/16/main /var/log/postgresql/postgresql-16.log
			</pre>
			The 16/main cluster was created automatically by the postgresql installation script. It needs to be stopped and deleted.
			<pre>
			sudo pg_dropcluster 16 main --stop
			</pre>
			Running the <code>pg_lsclusters</code> command again should show that you have one '''11/main''' cluster left.

			=== Perform an upgrade of the old version database cluster to the new version database cluster ===
			Stop the postgresql service
			<pre>
			sudo systemctl stop postgresql
			</pre>
			Start the '''11/main''' database cluster upgrade process using the <code>pg_upgradecluster</code> utility from the postgresql-common package. This may take a lot of time and disc space.
			<pre>
			sudo pg_upgradecluster -m upgrade 11 main
			</pre>
			After the procedure is complete, start the postgres service
			<pre>
			sudo systemctl start postgresql
			</pre>
			Check what your database clusters look like
			<pre>
			sudo pg_lsclusters
			</pre>
			The old version must be in '''down''' mode. The output of the command will be approximately as follows:
			<pre>
			Ver Cluster Port Status Owner Data directory Log file
			11 main 5433 down postgres /var/lib/postgresql/11/main /var/log/postgresql/postgresql-11.log
			16 main 5432 online postgres /var/lib/postgresql/16/main /var/log/postgresql/postgresql-16.log
			</pre>

			=== Verify the operation of USERSIDE ===
			First run the commands displaying the versions to verify that the database is now running on the new version database cluster:
			<pre>
			sudo -u postgres psql -d userside -A -t -c "SELECT VERSION()"
			sudo -u postgres psql -d userside -A -t -c "SELECT PostGIS_full_version()"
			</pre>
			You should see version 16 of postgresql and version 3.3.4 of postgis. Maybe by the time you read these lines, the postgis version will be newer.

			Now start the FPM service and go to USERSIDE through your browser.
			<pre>
			sudo systemctl start php8.1-fpm
			</pre>
			Since the other services are stopped, you will probably see errors related to them, but the USERSIDE interface should open without database connection errors.
			If everything is successful, then uncomment the previously commented lines in crontab and start the external services under supervisor control:
			<pre>
			sudo supervisorctl start all
			sudo supervisorctl status
			</pre>

			=== Remove the old version database cluster, obsolete packages, and spare backups ===
			If USERSIDE is running correctly, and there are no database communication errors, you can remove the old cluster and packages. You can also optionally delete the emergency backups or wait a few days to make sure they are not needed.
			<pre>
			sudo pg_dropcluster 11 main --stop
			sudo apt purge -y postgresql-11 postgresql-11-postgis-2.5 postgresql-11-postgis-3
			sudo apt autoremove -y
			sudo rm /backup/userside_emergency_11* /backup/postgres_config_emergency_11.tgz
			sudo rm -rf /var/lib/postgresql/11/main
			</pre>

N.Skrypnik в 16:09, 22 января 2024

2024-01-22T16:09:40Z

Внесённые изменения

N.Skrypnik в 16:31, 27 февраля 2023

2023-02-27T16:31:24Z

← Предыдущая версия		Версия от 16:31, 27 февраля 2023
Строка 44:		Строка 44:
	sudo pg_dropcluster 11 main --stop		sudo pg_dropcluster 11 main --stop

	8. Stop the service		8. Stop the service:
	sudo systemctl stop postgresql		sudo systemctl stop postgresql

N.Skrypnik в 16:26, 27 февраля 2023

2023-02-27T16:26:38Z

← Предыдущая версия		Версия от 16:26, 27 февраля 2023
Строка 3:		Строка 3:
	This section describes how to upgrade PostgreSQL server to a new major version (e.g. from 9.x to 11.x). You can also upgrade to the maximum version available at the time of the upgrade - they are all backwards compatible.		This section describes how to upgrade PostgreSQL server to a new major version (e.g. from 9.x to 11.x). You can also upgrade to the maximum version available at the time of the upgrade - they are all backwards compatible.

	We recommend that the server upgrade procedure is performed by a qualified person using the official instructions: https://~~postgrespro~~.ru/docs~~/postgresql~~/11/upgrading.		We recommend that the server upgrade procedure is performed by a qualified person using the official instructions: https://www.postgresql.org/docs/11/upgrading.html.

	Updating within a major version (e.g. from 11.1 to 11.3) is done without any additional steps.		Updating within a major version (e.g. from 11.1 to 11.3) is done without any additional steps.
Строка 9:		Строка 9:
	There are several ways of upgrading. Here we will cover the method with a full dump before the upgrade and then a recovery from the dump after the upgrade. The procedure will also be explained for Debian and its derivatives (Ubuntu etc.). For other distributions and operating systems the procedure is almost exactly the same, but other tools specific to a particular distribution or operating system are used.		There are several ways of upgrading. Here we will cover the method with a full dump before the upgrade and then a recovery from the dump after the upgrade. The procedure will also be explained for Debian and its derivatives (Ubuntu etc.). For other distributions and operating systems the procedure is almost exactly the same, but other tools specific to a particular distribution or operating system are used.

	It is assumed that PostgreSQL was installed following these instructions and PostgreSQL repositories were added to the system, providing access to different versions of PostgreSQL and extensions, and that the installation followed these instructions and installed the ''postgresql-9.6'' package rather than the ''postgresql metapackage''. If you have a metapackage installed, the upgrade should happen automatically when you upgrade the metapackage, but it is not certain that it will go through correctly. We recommend using specific packages (specifying the version) instead of metapackages.		It is assumed that PostgreSQL was installed following these instructions and PostgreSQL repositories were added to the system, providing access to different versions of PostgreSQL and extensions, and that the installation followed these instructions and installed the '''postgresql-9.6''' package rather than the ''postgresql metapackage''. If you have a metapackage installed, the upgrade should happen automatically when you upgrade the metapackage, but it is not certain that it will go through correctly. We recommend using specific packages (specifying the version) instead of metapackages.

	If the upgrade process fails to successfully execute any command, please do not continue with the remaining items until the problem has been resolved. Unfortunately, we are not experts in all problems of PostgreSQL and the other services, so we will not always be able to give a qualified answer.		If the upgrade process fails to successfully execute any command, please do not continue with the remaining items until the problem has been resolved. Unfortunately, we are not experts in all problems of PostgreSQL and the other services, so we will not always be able to give a qualified answer.

N.Skrypnik в 16:22, 27 февраля 2023

2023-02-27T16:22:37Z

← Предыдущая версия		Версия от 16:22, 27 февраля 2023
Строка 1:		Строка 1:
	[[HOWTO:_PostgreSQL_version_upgrade\|en]] \| [[HOWTO:_Обновление_версии_PostgreSQL\|ru]]		[[HOWTO:_PostgreSQL_version_upgrade\|en]] \| [[HOWTO:_Обновление_версии_PostgreSQL\|ru]]

			This section describes how to upgrade PostgreSQL server to a new major version (e.g. from 9.x to 11.x). You can also upgrade to the maximum version available at the time of the upgrade - they are all backwards compatible.

			We recommend that the server upgrade procedure is performed by a qualified person using the official instructions: https://postgrespro.ru/docs/postgresql/11/upgrading.

			Updating within a major version (e.g. from 11.1 to 11.3) is done without any additional steps.

			There are several ways of upgrading. Here we will cover the method with a full dump before the upgrade and then a recovery from the dump after the upgrade. The procedure will also be explained for Debian and its derivatives (Ubuntu etc.). For other distributions and operating systems the procedure is almost exactly the same, but other tools specific to a particular distribution or operating system are used.

			It is assumed that PostgreSQL was installed following these instructions and PostgreSQL repositories were added to the system, providing access to different versions of PostgreSQL and extensions, and that the installation followed these instructions and installed the ''postgresql-9.6'' package rather than the ''postgresql metapackage''. If you have a metapackage installed, the upgrade should happen automatically when you upgrade the metapackage, but it is not certain that it will go through correctly. We recommend using specific packages (specifying the version) instead of metapackages.

			If the upgrade process fails to successfully execute any command, please do not continue with the remaining items until the problem has been resolved. Unfortunately, we are not experts in all problems of PostgreSQL and the other services, so we will not always be able to give a qualified answer.

			1. Stop all database-using systems from running. Stop php-fpm or apache2, and temporarily disable tasks in cron and stop usm_* modules from running.

			2. Check which versions of PostgreSQL and PostGIS you currently have installed:
			sudo -u postgres psql -d userside -A -c "SELECT VERSION()"
			sudo -u postgres psql -d userside -A -c "SELECT PostGIS_full_version()"

			3. Upgrade the current versions, and if you have PostGIS 2.4 installed, install PostGIS 2.5 and upgrade this extension in the database, then make sure the extension in the database is upgraded:
			sudo apt-get update
			sudo apt-get --only-upgrade install postgresql-9.6 postgresql-9.6-postgis-2.4 -y
			sudo apt-get install postgresql-9.6-postgis-2.5 -y
			sudo -u postgres psql -d userside -A -c "ALTER EXTENSION postgis UPDATE"
			sudo -u postgres psql -d postgres -A -c "ALTER EXTENSION postgis UPDATE"
			sudo -u postgres psql -d userside -A -c "SELECT PostGIS_full_version()"
			sudo -u postgres psql -d postgres -A -c "SELECT PostGIS_full_version()"

			4. Install the new version of PostgreSQL and PostGIS without removing the old one(!).
			sudo apt-get install postgresql-11 postgresql-11-postgis-2.5 -y

			5. Perform a backup of all server databases (in this case the latest version of the pg_dumpall utility will be used, but the database will still be used as before):
			sudo -u postgres pg_dumpall > /tmp/dump_9.6_before_update.dump

			6. Look at how your clusters look. You should now see two versions, both in an online state:
			pg_lsclusters
			You should see a table:
			Ver Cluster Port Status Owner Data directory
			9.6 main 5432 online postgres /var/lib/postgresql/9.6/main
			11 main 5433 online postgres /var/lib/postgresql/11/main

			7. When installing PostgreSQL, the installer automatically creates a cluster with the configuration and databases so that you can start working with the database immediately. In case of an upgrade this is an unnecessary operation and the cluster for version 11 needs to be removed. We will create it based on the version 9.6 cluster:
			sudo pg_dropcluster 11 main --stop

			8. Stop the service
			sudo systemctl stop postgresql

			9. Make a backup of the current directories with database files and configuration files. Be careful, the database files may take up a lot of storage space, so it may be best to choose a different location for them. Later, if the upgrade is successful, these directories will have to be removed:
			sudo cp -r /var/lib/postgresql/9.6/main/ /tmp/pg9.6-lib
			sudo cp -r /etc/postgresql/9.6/main/ /tmp/pg9.6-etc

			10. Start the procedure to create a new cluster based on the old cluster (cluster version upgrade):
			sudo pg_upgradecluster -m upgrade 9.6 main

			11. Start the service:
			sudo systemctl start postgresql

			12. Look at how your clusters look:
			pg_lsclusters
			Now you should see a table like this one, with version 9.6 in the down state:
			Ver Cluster Port Status Owner Data directory
			9.6 main 5433 down postgres /var/lib/postgresql/9.6/main
			11 main 5432 online postgres /var/lib/postgresql/11/main

			13. Check the versions:
			sudo -u postgres psql -d userside -A -c "SELECT VERSION()"
			sudo -u postgres psql -d userside -A -c "SELECT PostGIS_full_version()"

			14. Run all the services you stopped in step 1 and check that USERSIDE and modules are working. Check that everything is working correctly.

			15. After you have ensured that everything works correctly, you can remove the temporary backups as well as the old packages:
			sudo pg_dropcluster 9.6 main --stop
			sudo apt-get purge postgresql-9.6 postgresql-9.6-postgis-2.4 postgresql-9.6-postgis-2.5 -y
			sudo apt autoremove -y
			sudo rm -rf /tmp/pg9.6-* /tmp/dump_9.6_before_update.dump

			PostgreSQL upgrade completed.

			Video guide: https://youtu.be/c9ULVSz8yQM