Skip to content

Commit 7bd1aee

Browse files
committed
Added note from v13 to v16
1 parent fa3ffd6 commit 7bd1aee

File tree

4 files changed

+16
-0
lines changed

4 files changed

+16
-0
lines changed

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -198,6 +198,10 @@ If `pg_upgrade` alerts you to a missing component, you can use StackBuilder Plus
198198

199199
When `pg_upgrade` has confirmed that the clusters are compatible, you can perform a version upgrade.
200200

201+
!!!note
202+
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.
203+
!!!
204+
201205
**Step 7 - Run pg_upgrade**
202206

203207
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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -196,6 +196,10 @@ If `pg_upgrade` alerts you to a missing component, you can use StackBuilder Plus
196196

197197
When `pg_upgrade` has confirmed that the clusters are compatible, you can perform a version upgrade.
198198

199+
!!!note
200+
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.
201+
!!!
202+
199203
**Step 7 - Run pg_upgrade**
200204

201205
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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -186,6 +186,10 @@ If `pg_upgrade` alerts you to a missing component, you can use StackBuilder Plus
186186

187187
After `pg_upgrade` confirms that the clusters are compatible, you can perform a version upgrade.
188188

189+
!!!note
190+
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.
191+
!!!
192+
189193
## Step 7 - Run pg_upgrade
190194

191195
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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -186,6 +186,10 @@ If `pg_upgrade` alerts you to a missing component, you can use StackBuilder Plus
186186

187187
After `pg_upgrade` confirms that the clusters are compatible, you can perform a version upgrade.
188188

189+
!!!note
190+
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.
191+
!!!
192+
189193
## Step 7 - Run pg_upgrade
190194

191195
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.

0 commit comments

Comments
 (0)