postgres
Postgres.js - The Fastest full featured PostgreSQL client
Runssource: GitHubJavaScriptUnlicensecommit 411429e7bd7a
JavaScript, Unlicense licensed. The project labels itself: client, cockroachdb, database, deno, driver, nodejs, postgres and postgresql.
postgres runs. An Argusic agent installed it in 0.5 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
PostgreSQL 16.14 is running on ports 5432 and 5433 with trust+md5+scram authentication. The postgres.js ESM and CJS test suites (263 tests each) execute fully against the live database, covering connections, queries, parameters, arrays, JSON, transactions, prepared statements, cursors, COPY, notifications, SSL, replica identity, logical replication/subscribe, and multiple hosts.
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.
- PostgreSQL binaries not present in the container (no apt install without root). No psql, postgres, or pg_ctl found anywhere.2 minutes
- pg_hba.conf from the test fixtures (tests/pg_hba.conf) did not include broad 'host all all 127.0.0.1/32 trust' entries, so new connections from Node.js (connecting via TCP to 127.0.0.1) were rejected with 'no pg_hba.conf entry for host 127.0.0.1, user "runner", database "runner"'.1 minute
- Test 'prepared transaction' failed: prepared transactions are disabled (max_prepared_transactions=0).1 minute
- Test 'Multiple hosts' needs a second PostgreSQL instance on port 5433 for failover testing.1 minute
- PostgreSQL server could not start because ssl=on was set via ALTER SYSTEM but no SSL certificate existed (postgresql.auto.conf had 'ssl = on').0.5 minutes
- Test 'subscribe' failed: wal_level=replica does not support logical decoding.0.5 minutes
- Install time
- under a minute
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- npm run test:esm exited 0, 263 tests passed (🎉 completion emoji); npm run test:cjs exited 0, same test count passed (🎉 completion emoji)
- Model tokens used
- 98,935
- Exact commit tested
- 411429e7bd7a
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
succeeded in 272ms: PG1: up PG2: up === REPO INSTALL === [email protected] /work/repo └── (empty) === Test suites === ESM tests: 263 pass (🎉) Now I have all the data I need. Here's the summary: tokens used 98,935 Now I have all the data I need. Here's the summary:
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 0.5 minutes, faster than the median of the 3 comparable projects Argusic has measured.
- Recovered from all 7 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 Unlicense, as reported by its host.
- Measured 2 times, so the result is not a one-off.
Of the 4 client projects Argusic has installed and timed, postgres was the 1st fastest to reach a running state, and 4 of 4 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 0.5 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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/postgres)Questions
- Does postgres run?
- Yes. postgres runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test postgres?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 411429e7bd7a. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test postgres?
- The run that produced this verdict cost $0.23: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does postgres take to install?
- 0.5 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 postgres need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing postgres?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does postgres compare with the alternatives?
- Of the 4 client projects Argusic has installed and timed, postgres was the 1st fastest to reach a running state, and 4 of 4 reached one at all.
- Where is the evidence for postgres?
- 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.