alex shapalov's banner
alex shapalov's profile picture

alex shapalov

@alxshp • 2,400 subscribers

building infra for devs & agents daily PostgreSQL updates fast Postgres → @pgrun_dev

Shorts

Just launched today 🤖🐘 Postgres intelligence for agents & apps. Free. Open source. Written in Go. Nobody wants to stare at PostgreSQL dashboards all day. So I built a bot that does it for you. → finds what’s wrong → explains what changed → tells you what to fix first Metrics are data. pgbot gives you answers pgbot can: +PostgreSQL health monitoring +Query performance analysis +Slow query and regression detection +Locks and blocking query insights +Table and index analytics +Vacuum and autovacuum visibility +Database growth tracking +AI root-cause analysis +AI-powered recommendations +Direct connection or agent-based private access

Just launched today 🤖🐘 Postgres intelligence for agents & apps. Free. Open source. Written in Go. Nobody wants to stare at PostgreSQL dashboards all day. So I built a bot that does it for you. → finds what’s wrong → explains what changed → tells you what to fix first Metrics are data. pgbot gives you answers pgbot can: +PostgreSQL health monitoring +Query performance analysis +Slow query and regression detection +Locks and blocking query insights +Table and index analytics +Vacuum and autovacuum visibility +Database growth tracking +AI root-cause analysis +AI-powered recommendations +Direct connection or agent-based private access

96,420 Aufrufe

Postgres 19 handles traffic spikes the way infrastructure should. Not with one fixed I/O pool sized for an imaginary average day. But dynamically. → Traffic spikes → The I/O queue grows → PostgreSQL notices → More workers launch → The queue clears → Extra workers disappear when demand drops No manual intervention. No permanent overprovisioning. No tiny worker pool choking under production traffic. PostgreSQL is becoming infrastructure that adapts instead of infrastructure you babysit.

Postgres 19 handles traffic spikes the way infrastructure should. Not with one fixed I/O pool sized for an imaginary average day. But dynamically. → Traffic spikes → The I/O queue grows → PostgreSQL notices → More workers launch → The queue clears → Extra workers disappear when demand drops No manual intervention. No permanent overprovisioning. No tiny worker pool choking under production traffic. PostgreSQL is becoming infrastructure that adapts instead of infrastructure you babysit.

95,726 Aufrufe

Postgres 19 can query relationships like a GRAPH NOT with a long manual join chain. With a path: customer → bought → product product ← bought ← similar customer similar customer → follows → brand That is a recommendation system in one readable pattern. SQL/PGQ finds the relationship. COLUMNS decides what comes back. Postgres keeps eating the backend stack.

Postgres 19 can query relationships like a GRAPH NOT with a long manual join chain. With a path: customer → bought → product product ← bought ← similar customer similar customer → follows → brand That is a recommendation system in one readable pattern. SQL/PGQ finds the relationship. COLUMNS decides what comes back. Postgres keeps eating the backend stack.

55,524 Aufrufe