docker-postgres-backup-local

Backup PostgresSQL to local filesystem with periodic backups and rotate backups.

Runssource: GitHubhomepageShellMITcommit d00896ab15f6

Shell, MIT licensed. The project labels itself: backup, docker, docker image, postgres and postgresql.

docker-postgres-backup-local runs. An Argusic agent installed it in 4 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The backup.sh script runs against a local PostgreSQL 16 instance, producing gzipped SQL dumps deployed into last/daily/weekly/monthly folders with correct hardlinks and symlinks; the docker-bake.hcl is correctly generated by generate-docker-bake.sh.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.04 (measured)
recorded runs
2
last tested
stars
1,215
forks
166
open issues
15
watchers
8
size
0 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.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing docker-postgres-backup-local, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • PostgreSQL failed to start: could not create lock file /var/run/postgresql/.s.PGSQL.5432.lock0.5 minutes
  • pg_dumpall failed: permission denied for table pg_authid (user is not superuser)0.5 minutes
Install time
4 minutes
Cold machine to finish
4 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
Exported POSTGRES_HOST=/tmp/pgsock with running postgres, ran 'bash backup.sh' for 3 scenarios: (1) pg_dump -Z0 produced /tmp/backups/last/database-*.sql.gz with plain SQL dump visible on cat; (2) pg_dump -Z0 -Fd produced a valid directory-format archive confirmed by 'pg_restore -l' showing TOC; (3) pg_dumpall produced a gzipped cluster dump confirmed by 'zcat | grep' showing 'PostgreSQL database cluster dump' and test_table. All three exited 0 with correct hardlink/symlink rotation structures.
Model tokens used
68,974
Exact commit tested
d00896ab15f6
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.

; Selected TOC Entries:
;
The directory-format backup is valid — `pg_restore -l` reads its TOC successfully. Let me stop Post…
exec
/bin/sh -lc 'export PGROOT=/tmp/pg_usr/usr/lib/postgresql/16 && export PATH="$PGROOT/bin:$PATH" && …
 succeeded in 0ms:
waiting for server to shut down.... done
server stopped
Here is the final structured result:
tokens used
68,974
Here is the final structured result:

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 4 minutes.
  • Recovered from all 2 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 MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 48 backup projects Argusic has installed and timed, docker-postgres-backup-local was the 21st fastest to reach a running state, and 32 of 48 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 4 minutes after the clone.

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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.04
Argusic Runner1/3Runs100.000.05

Topics (from GitHub)

backupdockerdocker-imagepostgrespostgresql

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/docker-postgres-backup-local.svg)](https://argusic.com/subject/docker-postgres-backup-local)

Questions

Does docker-postgres-backup-local run?
Yes. docker-postgres-backup-local runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test docker-postgres-backup-local?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit d00896ab15f6. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test docker-postgres-backup-local?
The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does docker-postgres-backup-local take to install?
4 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 docker-postgres-backup-local need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing docker-postgres-backup-local?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does docker-postgres-backup-local compare with the alternatives?
Of the 48 backup projects Argusic has installed and timed, docker-postgres-backup-local was the 21st fastest to reach a running state, and 32 of 48 reached one at all.
Where is the evidence for docker-postgres-backup-local?
All 2 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