gregs1104/pgbent

PostgreSQL Benchmarking Toolkit

This repository also configures its own agents. See what pgbent tells them →

268Stars on the repository
6Mods indexed here, across every type
yesterdayLast push, which is what freshness is scored on
customA LICENSE file GitHub cannot name, so bodies are not copied

gregs1104/pgbent

Skill Claude CodeCodex

Tune Matplotlib labels on pgbent PG18 charts: scatter point placement, horizontal bar value labels (inside bar with contrast color when they fit), overlap avoidance, and PNG regeneration. Use when fixing crowded scatter or bar labels, pg18-osm-power-.png, pg18-osm-relation-power.png, pg18-osm-relation-scatter.png…

not rated 268 yesterday A 89 tokens

pg-release-config

02

gregs1104/pgbent

Skill Claude Code

Prepare and evolve the per-release PostgreSQL configuration set (conf/ /conf.d) for a new pgbent release study such as PG19. Covers copying forward from the prior release, deploying to a server's conf.d, retuning during the cycle, and recording why each setting changed. Use when starting a new major-version test cycle…

not rated 268 changed today B 81 tokens

pg-release-publish

03

gregs1104/pgbent

Skill Claude Code

Assemble and publish pgbent studies for a PostgreSQL release cycle such as PG19: turn newset-flagged test sets into study SQL, graph with reports/.py --pg N, write getbent.io pages under docs/results-summary/pg /, and close the cycle with static snapshots. Use when a study's data is in (via upload/download) and needs…

not rated 268 changed today A 102 tokens

pg-release-runs

04

gregs1104/pgbent

Skill Claude Code

Open and run pgbent studies during a PostgreSQL release cycle such as PG19: flag a study with newset on each participating machine, run the workload (osm2pgsql planet load, pgbench grids, or custom), validate, and ship the results with upload/download for assembly. Use when a new study topic comes up, when preparing a…

not rated 268 changed today B 90 tokens

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: