pglite
Embeddable Postgres with real-time, reactive bindings.
Runssource: GitHubhomepageTypeScriptApache-2.0commit ae182ff8bd5b
TypeScript, Apache-2.0 licensed. The project labels itself: database, postgres and wasm.
pglite runs. An Argusic agent installed it in 3 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
PGlite v0.5.8 installed and built successfully; all 58 test suites (294 tests) pass; the in-memory Postgres WASM instance runs correctly in Node.js 20, executing queries, DDL, and DML.
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.
- Install time
- 3 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- pnpm test:basic: 58 test files passed, 284 passed / 1 skipped (145s). pnpm test:node: 2 test files passed, 10 passed (5s). Manual Node.js query: new PGlite() executed 'select Hello world as message' returning [{message:'Hello world'}] then CREATE TABLE + INSERT + SELECT returned [{id:2,name:'beta',value:20},{id:3,name:'gamma',value:30}]
- Model tokens used
- 131,031
- Exact commit tested
- ae182ff8bd5b
- 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.
const res = await db.query('SELECT * FROM test WHERE value > 15 ORDER BY name');
console.log('Records:', JSON.stringify(res.rows));
console.log('Row count:', res.rows.length);
await db.close();
\"" in /work/repo
succeeded in 1905ms:
Records: [{"id":2,"name":"beta","value":20},{"id":3,"name":"gamma","value":30}]
Row count: 2
Everything works. Now I'll compile the final structured result.
tokens used
131,031
Everything works. Now I'll compile 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 3 minutes, faster than the median of the 18 comparable projects Argusic has measured.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, 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.
Of the 19 database projects Argusic has installed and timed, pglite was the 8th fastest to reach a running state, and 16 of 19 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 3 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
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/pglite)Questions
- Does pglite run?
- Yes. pglite runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test pglite?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ae182ff8bd5b. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test pglite?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does pglite take to install?
- 3 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 pglite need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing pglite?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does pglite compare with the alternatives?
- Of the 19 database projects Argusic has installed and timed, pglite was the 8th fastest to reach a running state, and 16 of 19 reached one at all.
- Where is the evidence for pglite?
- 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.