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
pg_probackup forkof pg_arman by Postgres Professional
2
2
========================================
3
3
4
-
This repository contains fork of pg_arman by Postgres Professional with
5
-
block level incremental backup support.
6
-
7
-
pg_arman is a backup and recovery manager for PostgreSQL servers able to do
4
+
pg_probackup is a backup and recovery manager for PostgreSQL servers able to do
8
5
differential and full backup as well as restore a cluster to a
9
6
state defined by a given recovery target. It is designed to perform
10
7
periodic backups of an existing PostgreSQL server, combined with WAL
@@ -13,41 +10,52 @@ server because of a reason or another. Its differential backup
13
10
facility reduces the amount of data necessary to be taken between
14
11
two consecutive backups.
15
12
13
+
Main features:
14
+
* incremental backup from WAL and PTRACK
15
+
* backup from replica
16
+
* multithreaded backup and restore
17
+
* autonomous backup without archive command (will need slot replication)
18
+
19
+
Requirements:
20
+
*>=PostgreSQL 9.5
21
+
*>=gcc 4.4 or >=clang 3.6 or >= XLC 12.1
22
+
* pthread
23
+
16
24
Download
17
25
--------
18
26
19
27
The latest version of this software can be found on the project website at
20
-
https://github.com/postgrespro/pg_arman. Original fork ofpg_arman can be
28
+
https://github.com/postgrespro/pg_probackup. Original fork ofpg_probackup can be
21
29
found athttps://github.com/michaelpq/pg_arman.
22
30
23
31
Installation
24
32
------------
25
33
26
-
Compilingpg_arman requires a PostgreSQL installation to be in place
34
+
Compilingpg_probackup requires a PostgreSQL installation to be in place
27
35
as well as a raw source tree. Pass the path to the PostgreSQL source tree
28
36
to make, in the top_srcdir variable:
29
37
30
38
make USE_PGXS=1 top_srcdir=<path to PostgreSQL source tree>
31
39
32
40
In addition, you must have pg_config in $PATH.
33
41
34
-
The current version ofpg_arman is compatible with PostgreSQL 9.5 and
42
+
The current version ofpg_probackup is compatible with PostgreSQL 9.5 and
35
43
upper versions.
36
44
37
45
Platforms
38
46
---------
39
47
40
-
pg_arman has been tested on Linux and Unix-based platforms.
48
+
pg_probackup has been tested on Linux and Unix-based platforms.
41
49
42
50
Documentation
43
51
-------------
44
52
45
-
All the documentation you can find[here](doc/pg_arman.md).
53
+
All the documentation you can find[here](doc/pg_probackup.md).
46
54
47
55
Regression tests
48
56
----------------
49
57
50
-
The test suite ofpg_arman is available in the code tree and can be
58
+
The test suite ofpg_probackup is available in the code tree and can be
51
59
launched in a way similar to common PostgreSQL extensions and modules:
52
60
53
61
make installcheck
@@ -74,50 +82,45 @@ of these approach is requirement to have WAL archive.
74
82
some overhead to PostgreSQL performance. On our experiments it appears to be
75
83
less than 3%.
76
84
77
-
These two approaches were implemented in this fork of pg_arman. The second
78
-
approach requires[patch for PostgreSQL 9.5](https://gist.github.com/stalkerg/44703dbcbac1da08f448b7e6966646c0).
85
+
These two approaches were implemented in this fork of pg_probackup. The second
86
+
approach requires[patch for PostgreSQL 9.5](https://gist.github.com/stalkerg/44703dbcbac1da08f448b7e6966646c0) or
87
+
[patch for PostgreSQL 10](https://gist.github.com/stalkerg/ab833d94e2f64df241f1835651e06e4b).
79
88
80
89
Testing block level incremental backup
81
90
--------------------------------------
82
91
83
-
You need build and install[PGPRO9_5 branch of PostgreSQL](https://github.com/postgrespro/postgrespro) or[apply this patch to PostgreSQL 9.5](https://gist.github.com/stalkerg/44703dbcbac1da08f448b7e6966646c0).
92
+
You need build and install[PGPRO9_5 or PGPRO9_6 branch of PostgreSQL](https://github.com/postgrespro/postgrespro) or apply this patch to
@@ -128,39 +131,33 @@ The advantage of this approach is that you don't have to save WAL archive. You
128
131
ptrack_enable = on
129
132
```
130
133
131
-
Also, some WALs still need to be fetched in order to get consistent backup.pg_arman can fetch them trough the streaming replication protocol. Thus, you also need to[enable streaming replication connection](https://wiki.postgresql.org/wiki/Streaming_Replication).
134
+
Also, some WALs still need to be fetched in order to get consistent backup.pg_probackup can fetch them trough the streaming replication protocol. Thus, you also need to[enable streaming replication connection](https://wiki.postgresql.org/wiki/Streaming_Replication).