You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ As compared to other backup solutions, `pg_probackup` offers the following benef
17
17
* Extended logging settings
18
18
* Custom commands to simplify WAL log archiving
19
19
* External to PGDATA directories, such as directories with config files and scripts, can be included in backup
20
-
* Remote backup, restore, archive-push and archive-get operations via ssh (beta)
20
+
* Remote backup, restore,add-instance,archive-push and archive-get operations via ssh (beta)
21
21
* Checking running PostgreSQL instance for the sights of corruption in read-only mode via`checkdb` command.
22
22
23
23
To manage backup data,`pg_probackup` creates a backup catalog. This directory stores all backup files with additional meta information, as well as WAL archives required for[point-in-time recovery](https://postgrespro.com/docs/postgresql/current/continuous-archiving.html). You can store backups for different instances in separate subdirectories of a single backup catalog.