A dump-and-restore that refuses to start if the copy could lose data — then counts every row on both sides to show you it didn't.
Every one of these has cost somebody a weekend. dbclone checks for all of them before it writes a single byte.
A clone is only reported as successful when all three match. Anything that differs is listed by name.
| Copy server-level roles and passwords | pg_dump works per database. Create application users yourself. |
| Downgrade across major versions | 18 → 16 is impossible in PostgreSQL itself. Rejected up front, not halfway. |
| Move a 50 GB database quickly | It works, but replication-based tooling is the right answer at that size. |
| Store your credentials | Connection strings live in memory for one job, then they are gone. |
Pick both ends, then clone with verification — or just compare what is already there.
Source
Read only — never modified.
Destination
Connect to any database on that server.
Run
Pre-flight runs first. If anything could be lost, nothing starts.
Only your own runs are listed. Connection strings are stored masked.