Merge pull request #6579 from EnterpriseDB/content/docs/epas/docs-1123

EPAS - Adding a note to upgrade

Author: nidhibhammar

product_docs/docs/epas/13/upgrading/04_upgrading_an_installation_with_pg_upgrade/03_upgrading_to_advanced_server.mdx

@@ -60,9 +60,7 @@ You must allow trust authentication for the previous Advanced Server installatio
 
 After editing each file, save the file and exit the editor.
 
-If the system is required to maintain `md5` authentication mode during the upgrade process, you can specify user passwords for the database superuser in a password file (`pgpass.conf` on Windows, `.pgpass` on Linux). For more information about configuring a password file, see the PostgreSQL Core Documentation, available at:
-
-<https://www.postgresql.org/docs/current/static/libpq-pgpass.html>
+If the system is required to maintain `md5` authentication mode during the upgrade process, you can specify user passwords for the database superuser in a password file (`pgpass.conf` on Windows, `.pgpass` on Linux). For more information about configuring a password file, see the [PostgreSQL Core Documentation](https://www.postgresql.org/docs/current/static/libpq-pgpass.html).
 
 **Step 4 - Stop All Component Services and Servers**
 
@@ -198,6 +196,10 @@ If `pg_upgrade` alerts you to a missing component, you can use StackBuilder Plus
 
 When `pg_upgrade` has confirmed that the clusters are compatible, you can perform a version upgrade.
 
+!!!note
+If you are using any extensions that maintain a constant connection to the database, such as `edb_wait_states`, please disable them before attempting the actual `pg_upgrade`. No connections should be established to the database during the upgrade.
+!!!
+
 **Step 7 - Run pg_upgrade**
 
 After confirming that the clusters are compatible, you can invoke `pg_upgrade` to upgrade the old cluster to the new version of Advanced Server.

product_docs/docs/epas/14/upgrading/04_upgrading_an_installation_with_pg_upgrade/03_upgrading_to_advanced_server.mdx

@@ -57,9 +57,7 @@ You must allow trust authentication for the previous EDB Postgres Advanced Serve
 
 After editing each file, save the file and exit the editor.
 
-If the system is required to maintain `md5` authentication mode during the upgrade process, you can specify user passwords for the database superuser in a password file (`pgpass.conf` on Windows, `.pgpass` on Linux). For more information about configuring a password file, see the PostgreSQL Core Documentation, available at:
-
-<https://www.postgresql.org/docs/current/static/libpq-pgpass.html>
+If the system is required to maintain `md5` authentication mode during the upgrade process, you can specify user passwords for the database superuser in a password file (`pgpass.conf` on Windows, `.pgpass` on Linux). For more information about configuring a password file, see the [PostgreSQL Core Documentation](https://www.postgresql.org/docs/current/static/libpq-pgpass.html).
 
 **Step 4 - Stop all component services and servers**
 
@@ -196,6 +194,10 @@ If `pg_upgrade` alerts you to a missing component, you can use StackBuilder Plus
 
 When `pg_upgrade` has confirmed that the clusters are compatible, you can perform a version upgrade.
 
+!!!note
+If you are using any extensions that maintain a constant connection to the database, such as `edb_wait_states`, please disable them before attempting the actual `pg_upgrade`. No connections should be established to the database during the upgrade.
+!!!
+
 **Step 7 - Run pg_upgrade**
 
 After confirming that the clusters are compatible, you can invoke `pg_upgrade` to upgrade the old cluster to the new version of EDB Postgres Advanced Server.

product_docs/docs/epas/15/upgrading/04_upgrading_an_installation_with_pg_upgrade/03_upgrading_to_advanced_server.mdx

@@ -186,6 +186,10 @@ If `pg_upgrade` alerts you to a missing component, you can use StackBuilder Plus
 
 After `pg_upgrade` confirms that the clusters are compatible, you can perform a version upgrade.
 
+!!!note
+If you are using any extensions that maintain a constant connection to the database, such as `edb_wait_states`, please disable them before attempting the actual `pg_upgrade`. No connections should be established to the database during the upgrade.
+!!!
+
 ## Step 7 - Run pg_upgrade
 
 After confirming that the clusters are compatible, you can invoke `pg_upgrade` to upgrade the old cluster to the new version of EDB Postgres Advanced Server.

product_docs/docs/epas/16/upgrading/major_upgrade/03_upgrading_to_advanced_server.mdx

@@ -186,6 +186,10 @@ If `pg_upgrade` alerts you to a missing component, you can use StackBuilder Plus
 
 After `pg_upgrade` confirms that the clusters are compatible, you can perform a version upgrade.
 
+!!!note
+If you are using any extensions that maintain a constant connection to the database, such as `edb_wait_states`, please disable them before attempting the actual `pg_upgrade`. No connections should be established to the database during the upgrade.
+!!!
+
 ## Step 7 - Run pg_upgrade
 
 After confirming that the clusters are compatible, you can invoke `pg_upgrade` to upgrade the old cluster to the new version of EDB Postgres Advanced Server.

product_docs/docs/epas/17/upgrading/major_upgrade/03_upgrading_to_advanced_server.mdx

@@ -180,6 +180,10 @@ If `pg_upgrade` alerts you to a missing component, you can use StackBuilder Plus
 
 After `pg_upgrade` confirms that the clusters are compatible, you can perform a version upgrade.
 
+!!!note
+If you are using any extensions that maintain a constant connection to the database, such as `edb_wait_states`, please disable them before attempting the actual `pg_upgrade`. No connections should be established to the database during the upgrade.
+!!!
+
 ## Step 7 - Run pg_upgrade
 
 After confirming that the clusters are compatible, you can invoke `pg_upgrade` to upgrade the old cluster to the new version of EDB Postgres Advanced Server.