» Tag
postgresql
65 postsPGSimCity: an explorable 3D city that visualizes PostgreSQL internals
PGSimCity visualizes PostgreSQL internals as an explorable 3D city, covering WAL, checkpoints, autovacuum, buffers and replication in real time.
Idempotency Fundamentals: Engineering API Guarantees at Scale
A practical breakdown of idempotency in distributed systems: request flow, failure boundaries, key state machines, and storage trade-offs.
PostgreSQL 19 Preview: Property Graph Queries and Temporal Updates
PostgreSQL 19 beta introduces SQL/PGQ graph queries, temporal FOR PORTION OF updates, and ON CONFLICT DO SELECT, shown through runnable examples.
CommitBrief — AI code reviews, right in your terminal
A provider-agnostic, local-first CLI that reviews your staged changes, a historic range, or a whole GitHub pull request. Zero telemetry, no server. Free and open source.
commitbrief.comDiagnosing Slow Postgres Queries: Planning Time vs Execution Time
Learn to read EXPLAIN ANALYZE buffer stats to tell if a slow Postgres query needs partition/plan fixes or memory/storage fixes.
pgColumnar 1.0-alpha2 Ships Read-Only Iceberg and S3 Object Storage
pgColumnar 1.0-alpha2 adds read-only Apache Iceberg support, S3-compatible object storage, a maintenance daemon, and six security fixes.
PostgreSQL and the Linux OOM Killer: A Safer Default
How strict Linux memory overcommit (vm.overcommit_memory=2) prevents OOM-killer-driven crashes in PostgreSQL, backed by a direct benchmark comparison.
Benchmarking How High Availability Affects Managed Postgres Speed
PostgresBench benchmarks the real throughput and latency cost of high availability across managed Postgres providers.
Synapsor Runner Lets AI Agents Propose Changes, Not Execute SQL
Synapsor Runner is an open-source MCP runtime giving AI agents reviewed semantic tools instead of raw SQL, keeping database write authority outside the model loop.
apitap: Rust-Based ELT Engine Moves 10M Rows in 9.9s
Open-source Rust engine apitap moves 10M database rows in 9.9 seconds via a single function call, benchmarked against dlt and ingestr.
Supabase's silent defaults: four incidents, one shared root cause
Four Supabase incidents in one week trace back to one cause: silent vendor defaults. Three rules for documenting, linting, and monitoring them.