dbSlice sample: catch up a PostgreSQL replica after a network outage, from the command line
Article: https://dbslice.net/blog/replica-catch-up-after-network-outage

01-baseline.sql              SQL Server: 40,000 generic payments (no real data), the state before the outage. Run with sqlcmd.
02-baseline-postgres.sql     PostgreSQL: the same 40,000 payments (the replica in sync). Run with psql.
03-outage-source.sql         SQL Server: what the source received during the outage (2,160 new payments, 400 settled).
replica-payments-sync.json   Job: sync in Upsert mode with "watermark": "updated_at" (copies only what changed).
replica-payments-check.json  Job: compare data (read only), limited to the last 8 hours on the source.
run-linux.sh                 Linux (Docker edition): runs the jobs through the jobs API (curl + jq, token read from a file).
run-windows.ps1              Windows: runs the jobs with dbSlice.exe.

To repeat the example: load 01 and 02, run replica-payments-sync.json once while both sides are equal (it saves the
watermark), apply 03 on SQL Server to simulate the outage, then run run-linux.sh or run-windows.ps1.
The job files name connection profiles (MASTER, Server-dbPostg); rename them to your own profiles.
No job file holds a password or a token.
