pgmoneta
Backup / restore solution for PostgreSQL
Runssource: 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 runs. An Argusic agent installed it in 28 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
pgmoneta 0.22.0 builds from source on Ubuntu 24.04 with GCC 13; all 6 CLI binaries link and respond to --version/--help; the unit test binary (pgmoneta-test) compiles and runs individual tests successfully.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
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.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Missing -dev packages (libev-dev, liblz4-dev, libzstd-dev, libbz2-dev, libarchive-dev, libssh-dev, libyaml-dev, ncurses-dev)3 minutes
- Missing rst2man/docutils for man page generation3 minutes
- ncurses linker script fails to resolve libncurses.so.6 and -ltinfo3 minutes
- COLOR_* macro conflict between utils.h (ANSI strings) and ncurses.h (integer constants) in walinfo.c3 minutes
- libev header triggers GCC strict-aliasing -Werror failures1 minute
- Install time
- 28 minutes
- Cold machine to finish
- 28 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- pgmoneta --version printed 'pgmoneta 0.22.0'; pgmoneta --help printed usage; pgmoneta-cli --version printed 'pgmoneta-cli 0.22.0'; pgmoneta-admin --help printed usage; pgmoneta-walinfo --help printed usage; pgmoneta-test -t test_utils_compare_string exited 0 with 'Total tests: 1' and '[PASS]'
- Model tokens used
- 420,118
- Exact commit tested
- be594e442ee6
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Current time: 2026-10-24 20:10:44 exec /bin/sh -lc '# Verify one more binary LD_LIBRARY_PATH=/home/runner/.local/lib /work/repo/build6/src/pgmoneta-walinfo --help 2>&1 | head -… succeeded in 0ms: pgmoneta-walinfo 0.22.0 Command line utility to read and display Write-Ahead Log (WAL) files All binaries built and verified, unit tests pass. Here's the final report: tokens used 420,118 All binaries built and verified, unit tests pass. Here's the final report:
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 28 minutes.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed BSD-3-Clause, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
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
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.
[](https://argusic.com/subject/pgmoneta)Questions
- Does pgmoneta run?
- Yes. pgmoneta runs. Argusic installed and launched it on a clean machine in 28 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test pgmoneta?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit be594e442ee6. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test pgmoneta?
- The run that produced this verdict cost $0.63: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does pgmoneta take to install?
- 28 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does pgmoneta need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing pgmoneta?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for pgmoneta?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.