Skip to content

Commit cba4f6c

Browse files
authored
Update Migration topic with fixed material and better formatting (#889)
This PR fixes some minor visual issues in migration.md
1 parent 9a37501 commit cba4f6c

File tree

1 file changed

+10
-15
lines changed

1 file changed

+10
-15
lines changed

docs/migration.md

Lines changed: 10 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,16 @@
1-
# Migrate from PostgreSQL to Percona Distribution for PostgreSQL
2-
1+
# Migrate from PostgreSQL to Percona Distribution for PostgreSQL
32

43
Percona Distribution for PostgreSQL includes the PostgreSQL database and additional extensions that have been selected to cover the needs of the enterprise and are guaranteed to work together. Percona Distribution for PostgreSQL is available as a software collection that is easy to deploy.
54

6-
We encourage users to migrate from their PostgreSQL deployments based on community binaries to Percona Distribution for PostgreSQL. This document provides the migration instructions.
5+
We encourage users to migrate from their PostgreSQL deployments based on community binaries to Percona Distribution for PostgreSQL. This document provides the migration instructions.
76

8-
Depending on your business requirements, you may migrate to Percona Distribution for PostgreSQL either [on the same server](#migrate-on-the-same-server) or [onto a different server](#migrate-on-a-different-server).
7+
Depending on your business requirements, you may migrate to Percona Distribution for PostgreSQL either [on the same server](#migrate-on-the-same-server) or [onto a different server](#migrate-on-a-different-server).
98

109
## Migrate on the same server
1110

12-
=== ":material-debian: :material-debian: On Debian and Ubuntu Linux"
11+
=== ":material-debian: On Debian and Ubuntu Linux"
1312

14-
>To ensure that your data is safe during the migration, we recommend to make a backup of your data and all configuration files (such as `pg_hba.conf`, `postgresql.conf`, `postgresql.auto.conf`) using the tool of your choice. The backup process is out of scope of this document. You can use `pg_dumpall` or other tools of your choice. For more information, see the blog post [PostgreSQL Upgrade Using pg_dumpall](https://www.percona.com/blog/postgresql-upgrade-using-pg_dumpall/) by _Avinash Vallarapu_, _Fernando Laudares Camargos_, _Jobin Augustine_ and _Nickolay Ihalainen_.
13+
>To ensure that your data is safe during the migration, we recommend to make a backup of your data and all configuration files (such as `pg_hba.conf`, `postgresql.conf`, `postgresql.auto.conf`) using the tool of your choice. The backup process is out of scope of this document. You can use `pg_dumpall` or other tools of your choice. For more information, see the blog post [PostgreSQL Upgrade Using pg_dumpall :octicons-link-external-16:](https://www.percona.com/blog/postgresql-upgrade-using-pg_dumpall/) by _Avinash Vallarapu_, _Fernando Laudares Camargos_, _Jobin Augustine_ and _Nickolay Ihalainen_.
1514

1615
Run **all** commands as root or via **sudo**:
1716
{.power-number}
@@ -49,7 +48,6 @@ Depending on your business requirements, you may migrate to Percona Distribution
4948
$ sudo systemctl start postgresql.service
5049
```
5150

52-
5351
=== ":material-redhat: On RHEL and derivatives"
5452

5553
> To ensure that your data is safe during the migration, we recommend to make a backup of your data and all configuration files (such as `pg_hba.conf`, `postgresql.conf`, `postgresql.auto.conf`) using the tool of your choice. The backup process is out of scope of this document. You can use `pg_dumpall` or other tools of your choice.
@@ -84,15 +82,13 @@ Depending on your business requirements, you may migrate to Percona Distribution
8482
$ sudo systemctl start postgresql-{{pgversion}}
8583
```
8684

87-
8885
## Migrate on a different server
8986

9087
In this scenario, we will refer to the server with PostgreSQL Community as the "source" and to the server with Percona Distribution for PostgreSQL as the "target".
9188

9289
To migrate from PostgreSQL Community to Percona Distribution for PostgreSQL on a different server, do the following:
9390

94-
**On the source server**:
95-
{.power-number}
91+
### **On the source server** {.power-number}
9692

9793
1. Back up your data and all configuration files (such as `pg_hba.conf`, `postgresql.conf`, `postgresql.auto.conf`) using the tool of your choice.
9894
2. Stop the `postgresql` service
@@ -109,12 +105,11 @@ To migrate from PostgreSQL Community to Percona Distribution for PostgreSQL on a
109105
$ sudo systemctl stop postgresql-{{pgversion}}
110106
```
111107

112-
3. Optionally, remove PostgreSQL Community packages
108+
3. Optionally, remove PostgreSQL Community packages
113109

114-
**On the target server**:
115-
{.power-number}
110+
### **On the target server** {.power-number}
116111

117-
1. [Install percona-release :octicons-link-external-16:](https://docs.percona.com/percona-software-repositories/installing.html)
112+
1. [Install percona-release :octicons-link-external-16:](https://docs.percona.com/percona-software-repositories/installing.html)
118113
2. Enable the repository
119114

120115
```{.bash data-prompt="$"}
@@ -135,4 +130,4 @@ To migrate from PostgreSQL Community to Percona Distribution for PostgreSQL on a
135130

136131
```{.bash data-prompt="$"}
137132
$ sudo systemctl start postgresql-{{pgversion}}
138-
```
133+
```

0 commit comments

Comments
 (0)