Skip to content

Update manual overview for PGD 5 upgrade steps #7191

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mpfuster merged 2 commits into from
Jul 8, 2026
Merged

Update manual overview for PGD 5 upgrade steps #7191

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
16d9eb8
Update manual overview for PGD 5 upgrade steps
wind39 Jul 7, 2026
9e35170
Port to other versions and fix command on other occurrences
mpfuster Jul 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion product_docs/docs/pgd/5.9/connection-manager/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ Use the following steps to move from PGD Proxy to Connection Manager:
END LOOP;
END;
$$;
SELECT wait_slot_confirm_lsn(NULL, NULL);
SELECT bdr.wait_slot_confirm_lsn(NULL, NULL);
```
!!!Note

Expand Down
4 changes: 2 additions & 2 deletions product_docs/docs/pgd/6.1/upgrades/manual_overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -240,7 +240,7 @@ that the upgraded node is working as expected.

Use the following steps to move from PGD Proxy to Connection Manager:

1. From one of the PGD 5.9 nodes, run the following query to ensure that SCRAM hashes of all user passwords are the same across all nodes:
1. From one of the PGD 5.9 nodes, as a database superuser, and while connected to the PGD-enabled database, run the following query to ensure that SCRAM hashes of all user passwords are the same across all nodes:

- ```sql
DO $$
Expand All @@ -256,7 +256,7 @@ Use the following steps to move from PGD Proxy to Connection Manager:
END LOOP;
END;
$$;
SELECT wait_slot_confirm_lsn(NULL, NULL);
SELECT bdr.wait_slot_confirm_lsn(NULL, NULL);
```
- !!!Note

Expand Down
2 changes: 1 addition & 1 deletion product_docs/docs/pgd/6.1/upgrades/upgrading_major_rolling.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -262,7 +262,7 @@ BEGIN
END LOOP;
END;
$$;
SELECT wait_slot_confirm_lsn(NULL,NULL);
SELECT bdr.wait_slot_confirm_lsn(NULL,NULL);
```
### Enable routing
Enable node group routing as per your global or local routing requirement. For local routing enable it on subgroups, for global routing enable it on the top group.
Expand Down
4 changes: 2 additions & 2 deletions product_docs/docs/pgd/6.2/lifecycle/upgrades/manual_overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -243,7 +243,7 @@ that the upgraded node is working as expected.

Use the following steps to move from PGD Proxy to Connection Manager:

1. From one of the PGD 5.9 nodes, run the following query to ensure that SCRAM hashes of all user passwords are the same across all nodes:
1. From one of the PGD 5.9 nodes, as a database superuser, and while connected to the PGD-enabled database, run the following query to ensure that SCRAM hashes of all user passwords are the same across all nodes:

- ```sql
DO $$
Expand All @@ -259,7 +259,7 @@ Use the following steps to move from PGD Proxy to Connection Manager:
END LOOP;
END;
$$;
SELECT wait_slot_confirm_lsn(NULL, NULL);
SELECT bdr.wait_slot_confirm_lsn(NULL, NULL);
```
- !!!Note

Expand Down
2 changes: 1 addition & 1 deletion product_docs/docs/pgd/6.2/lifecycle/upgrades/upgrading_major_rolling.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -272,7 +272,7 @@ BEGIN
END LOOP;
END;
$$;
SELECT wait_slot_confirm_lsn(NULL,NULL);
SELECT bdr.wait_slot_confirm_lsn(NULL,NULL);
```
### Enable routing
Enable node group routing as per your global or local routing requirement. For local routing enable it on subgroups, for global routing enable it on the top group.
Expand Down
4 changes: 2 additions & 2 deletions product_docs/docs/pgd/6.3/lifecycle/upgrades/manual_overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -243,7 +243,7 @@ that the upgraded node is working as expected.

Use the following steps to move from PGD Proxy to Connection Manager:

1. From one of the PGD 5.9 nodes, run the following query to ensure that SCRAM hashes of all user passwords are the same across all nodes:
1. From one of the PGD 5.9 nodes, as a database superuser, and while connected to the PGD-enabled database, run the following query to ensure that SCRAM hashes of all user passwords are the same across all nodes:

- ```sql
DO $$
Expand All @@ -259,7 +259,7 @@ Use the following steps to move from PGD Proxy to Connection Manager:
END LOOP;
END;
$$;
SELECT wait_slot_confirm_lsn(NULL, NULL);
SELECT bdr.wait_slot_confirm_lsn(NULL, NULL);
```
- !!!Note

Expand Down
2 changes: 1 addition & 1 deletion product_docs/docs/pgd/6.3/lifecycle/upgrades/upgrading_major_rolling.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -272,7 +272,7 @@ BEGIN
END LOOP;
END;
$$;
SELECT wait_slot_confirm_lsn(NULL,NULL);
SELECT bdr.wait_slot_confirm_lsn(NULL,NULL);
```
### Enable routing
Enable node group routing as per your global or local routing requirement. For local routing enable it on subgroups, for global routing enable it on the top group.
Expand Down
4 changes: 2 additions & 2 deletions product_docs/docs/pgd/6.4/lifecycle/upgrades/manual_overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -243,7 +243,7 @@ that the upgraded node is working as expected.

Use the following steps to move from PGD Proxy to Connection Manager:

1. From one of the PGD 5.9 nodes, run the following query to ensure that SCRAM hashes of all user passwords are the same across all nodes:
1. From one of the PGD 5.9 nodes, as a database superuser, and while connected to the PGD-enabled database, run the following query to ensure that SCRAM hashes of all user passwords are the same across all nodes:

- ```sql
DO $$
Expand All @@ -259,7 +259,7 @@ Use the following steps to move from PGD Proxy to Connection Manager:
END LOOP;
END;
$$;
SELECT wait_slot_confirm_lsn(NULL, NULL);
SELECT bdr.wait_slot_confirm_lsn(NULL, NULL);
```
- !!!Note

Expand Down
2 changes: 1 addition & 1 deletion product_docs/docs/pgd/6.4/lifecycle/upgrades/upgrading_major_rolling.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -272,7 +272,7 @@ BEGIN
END LOOP;
END;
$$;
SELECT wait_slot_confirm_lsn(NULL,NULL);
SELECT bdr.wait_slot_confirm_lsn(NULL,NULL);
```
### Enable routing
Enable node group routing as per your global or local routing requirement. For local routing enable it on subgroups, for global routing enable it on the top group.
Expand Down
Loading