@@ -101,14 +101,16 @@ some overhead to PostgreSQL performance. On our experiments it appears to be
101101less than 3%.
102102
103103These two approaches were implemented in this fork of pg_probackup. The second
104- approach requires[ patch for PostgreSQL 9.5 ] ( https://gist.github.com/stalkerg/44703dbcbac1da08f448b7e6966646c0 ) or
105- [ patch for PostgreSQL 10] ( https://gist.github.com/stalkerg/ab833d94e2f64df241f1835651e06e4b ) .
104+ approach requires[ patch for PostgreSQL 9.6.2 ] ( https://gist.github.com/alubennikova/9daacf35790eca1a09b63a1bca86d836 ) or
105+ [ patch for PostgreSQL 10 (master) ] ( https://gist.github.com/alubennikova/d24f61804525f0248fa71a1075158c21 ) .
106106
107107Testing block level incremental backup
108108--------------------------------------
109109
110- You need build and install[ PGPRO9_5 or PGPRO9_6 branch of PostgreSQL] ( https://github.com/postgrespro/postgrespro ) or apply this patch to
111- [ PostgreSQL 9.5] ( https://gist.github.com/stalkerg/44703dbcbac1da08f448b7e6966646c0 ) or[ PostgreSQL 10] ( https://gist.github.com/stalkerg/ab833d94e2f64df241f1835651e06e4b ) .
110+ You need to apply ptrack patch to[ PostgreSQL 9.6.2] ( https://gist.github.com/alubennikova/9daacf35790eca1a09b63a1bca86d836 )
111+ or[ PostgreSQL 10 (master)] ( https://gist.github.com/alubennikova/d24f61804525f0248fa71a1075158c21 ) .
112+ Or you can build and install[ PGPRO9_5 or PGPRO9_6 branch of PostgreSQL] ( https://github.com/postgrespro/postgrespro ) .
113+ Note that PGPRO branches currently contain old version of ptrack.
112114
113115###Retrieving changed blocks from WAL archive
114116