[](https://github.com/postgrespro/ptrack/releases/latest)

PTRACK saves changes of physical blocks in the memory. You can[effectively use](https://postgrespro.github.io/pg_probackup/#pbk-setting-up-ptrack-backups)`PTRACK` engine for taking incremental backups by[pg_probackup](https://github.com/postgrespro/pg_probackup).

PTRACKallows speed up incremental backups for the huge PostgreSQL databases. PTRACKsaves changes of physical blocks in the memory. You can[effectively use](https://postgrespro.github.io/pg_probackup/#pbk-setting-up-ptrack-backups)`PTRACK` engine for taking incremental backups by[pg_probackup](https://github.com/postgrespro/pg_probackup).

Current patch are available for[11](https://github.com/postgrespro/ptrack/blob/master/patches/REL_11_STABLE-ptrack-core.diff),[12](https://github.com/postgrespro/ptrack/blob/master/patches/REL_12_STABLE-ptrack-core.diff),[13](https://github.com/postgrespro/ptrack/blob/master/patches/REL_13_STABLE-ptrack-core.diff),[14](https://github.com/postgrespro/ptrack/blob/master/patches/REL_14_STABLE-ptrack-core.diff),[15](https://github.com/postgrespro/ptrack/blob/master/patches/REL_15_STABLE-ptrack-core.diff)

Enterprise PTRACK are part of[Postgres ProBackupEnterprise](https://postgrespro.ru/products/postgrespro/enterprise) and share posibility to track more than 100 000 tables and indexes per time without speed degradation with[CFS (compressed file system)](https://postgrespro.ru/docs/enterprise/15/cfs).

Enterprise PTRACK are part of[Postgres Pro Enterprise](https://postgrespro.ru/products/postgrespro/enterprise) and share posibility to track more than 100 000 tables and indexes per time without speed degradation with[CFS (compressed file system)](https://postgrespro.ru/docs/enterprise/current/cfs).

Benchmarks are x5 time faster and useful for ERP and DWH with huge amounth of tables and relations between them.

Feel free to[send pull requests](https://github.com/postgrespro/ptrack/compare),[fill up issues](https://github.com/postgrespro/ptrack/issues/new), or just reach one of us directly (e.g. <[Alexey Kondratov](mailto:a.kondratov@postgrespro.ru?subject=[GitHub]%20Ptrack),[@ololobus](https://github.com/ololobus)>) if you are interested in`PTRACK`.

Feel free to[send pull requests](https://github.com/postgrespro/ptrack/compare),[fill up issues](https://github.com/postgrespro/ptrack/issues/new).

Everything is tested automatically with[travis-ci.com](https://travis-ci.com/postgrespro/ptrack) and[codecov.io](https://codecov.io/gh/postgrespro/ptrack), but you can also run tests locally via`Docker`:

Available test modes (`MODE`) are`basic` (default) and`paranoia` (per-block checksum comparison of`PGDATA` content before and after backup-restore process). Available test cases (`TEST_CASE`) are`tap` (minimalistic PostgreSQL[tap test](https://github.com/postgrespro/ptrack/blob/master/t/001_basic.pl)),`all` or any specific[pg_probackup test](https://github.com/postgrespro/pg_probackup/blob/master/tests/ptrack.py), e.g.`test_ptrack_simple`.