PGFILEDESC = "ptrack - block-level incremental backup engine"

EXTENSION = ptrack

EXTVERSION = 2.3

DATA = ptrack--2.1.sql ptrack--2.0--2.1.sql ptrack--2.1--2.2.sql ptrack--2.2--2.3.sql

EXTVERSION = 2.4

DATA = ptrack--2.1.sql ptrack--2.0--2.1.sql ptrack--2.1--2.2.sql ptrack--2.2--2.3.sql\

ptrack--2.3--2.4.sql

TAP_TESTS = 1

postgres=# SELECT ptrack_version();

ptrack_version

2.3

2.4

(1 row)

postgres=# SELECT ptrack_init_lsn();

* Start server

* Do`ALTER EXTENSION 'ptrack' UPDATE;`.

* Stop your server

* Update ptrack binaries

* Start server

* Do`ALTER EXTENSION 'ptrack' UPDATE;`.

1. You can only use`ptrack` safely with`wal_level >= 'replica'`. Otherwise, you can lose tracking of some changes if crash-recovery occurs, since[certain commands are designed not to write WAL at all if wal_level is minimal](https://www.postgresql.org/docs/12/populate.html#POPULATE-PITR), but we only durably flush`ptrack` map at checkpoint time.

\echo Use"ALTER EXTENSION ptrack UPDATE;" to load this file. \quit

# ptrack extension

comment = 'block-level incremental backup engine'

default_version = '2.3'

default_version = '2.4'

module_pathname = '$libdir/ptrack'

relocatable = true

#definePTRACK_VERSION "2.3"

#definePTRACK_VERSION "2.4"

#definePTRACK_MAP_FILE_VERSION_NUM 220