User Tools

Site Tools


doc:appunti:linux:sa:postgresql_upgrade

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
doc:appunti:linux:sa:postgresql_upgrade [2020/03/02 17:45] – [Upgrade strategy] niccolodoc:appunti:linux:sa:postgresql_upgrade [2022/07/07 10:53] (current) niccolo
Line 1: Line 1:
-====== PostgreSQL/PostGIS Upgrade ======+====== PostgreSQL/PostGIS Upgrade from 9.6 to 11 ======
  
 The present notes are about upgrading PostgreSQL from **Debian 9 Stretch** to **Debian 10 Buster**, i.e. upgrading from **PostgreSQL 9.6** to version **11** and consequently upgrading **PostGIS 2.3** to **PostGIS 2.5**. The present notes are about upgrading PostgreSQL from **Debian 9 Stretch** to **Debian 10 Buster**, i.e. upgrading from **PostgreSQL 9.6** to version **11** and consequently upgrading **PostGIS 2.3** to **PostGIS 2.5**.
Line 40: Line 40:
 The **pg_upgradecluster** can safely upgrade standard databases, but the relative manpage clearly states that: //Some PostgreSQL extensions like PostGIS need metadata in auxiliary tables which must not be upgraded from the old version, but rather initialized for the new version before copying the table data//. The **pg_upgradecluster** can safely upgrade standard databases, but the relative manpage clearly states that: //Some PostgreSQL extensions like PostGIS need metadata in auxiliary tables which must not be upgraded from the old version, but rather initialized for the new version before copying the table data//.
  
-We have several standard (non-GIS) databases and a few PostGIS-enabled ones, so our strategy will be:+We have several standard (non-GIS) databases and a few PostGIS-enabled ones. You can see if the PostGIS extension is enabled issuing the **\dx** once connected to the database. So our strategy will be:
  
   - **Dump** the PostGIS-enabled databases into files.   - **Dump** the PostGIS-enabled databases into files.
Line 56: Line 56:
 </code> </code>
  
-now we can DROP them:+Then we DROP them:
  
 <code> <code>
Line 66: Line 66:
 ===== Upgrade cluster from 9.6 to 11 ===== ===== Upgrade cluster from 9.6 to 11 =====
  
-Drop the new 11 main cluster (which should be empty, actually):+Drop the new 11/main cluster (which should be indeed empty):
  
 <code> <code>
Line 82: Line 82:
 <code> <code>
 Fixing hardcoded library paths for stored procedures... Fixing hardcoded library paths for stored procedures...
-Upgrading database non_gis_database... +Upgrading database nongis_database... 
-Analyzing database non_gis_database...+Analyzing database nongis_database...
 </code> </code>
  
-Verify the new situation. Notice that the new 11 cluster was moved to the default **TCP** port **5432**:+Verify the new situation. Notice that the new **11/main** cluster was moved to the default **TCP** port **5432** and it is the only one running:
  
 <code> <code>
Line 101: Line 101:
 </code> </code>
  
-Now the **11 main cluster** is running, but **started by the postgres user**. We want it to be started by the regular **systemd** subsystem. To fix the situation run the following as the postgres user:+Now the **11/main cluster** is running, but **started by the postgres user**. We want it to be started by the regular **systemd** subsystem. To fix the situation run the following **as the postgres user**:
  
 <code> <code>
doc/appunti/linux/sa/postgresql_upgrade.1583167535.txt.gz · Last modified: 2020/03/02 17:45 by niccolo