pgmoneta

Backup / restore solution for PostgreSQL

Not yet testedsource: GitHubhomepageCBSD-3-Clausecommit be594e442ee6

C, BSD-3-Clause licensed. The project labels itself: archiving, backup, backup tool, checksum, compression, disaster recovery, encryption and incremental backups.

pgmoneta has not been verified yet.

Measured by Argusic on a fresh machine every time. Every number links to its evidence.

At a glance

verdict
Not yet tested
Argusic Score
not scored yet
recorded runs
0
last tested
-
stars
319
forks
124
open issues
87
watchers
12
size
9 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

No recorded runs.

Topics (from GitHub)

archivingbackupbackup-toolchecksumcompressiondisaster-recoveryencryptionincremental-backupspitrpoint-in-timepostgresqlpostgresql-backuppostgresql-restoreprometheusrecoveryrestoresymlinkswalwrite-ahead-log

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/pgmoneta.svg)](https://argusic.com/subject/pgmoneta)

Questions

Does pgmoneta run?
pgmoneta has not been fully verified yet. No recorded run has produced a verdict yet.
How did Argusic test pgmoneta?
On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
Where is the evidence for pgmoneta?
All 0 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion