postgres=# select * from sessions where video_id = 'woTqRL0Zh3A';
AI or not AI; GSoC 2026; improving pglz compression
Evaluate agentic hacking, develop GSoC project ideas, and experiment with pglz compression.
session summary
The first half examined AI-assisted Postgres development: community overload, specification-first agent workflows, independent review, and personal responsibility for generated work. The second half audited an agent-produced pglz optimization series. Existing benchmarks mixed runtime and work done, while some optimizations changed compressed output. The group therefore narrowed the project to byte-compatible changes, required old-versus-new output tests, fixed-transaction-count and multi-platform benchmarks, and a small reproducible pgsql-hackers result; a reported 14% workload gain still needed verification.
timecodes
- AI risks for the Postgres community
- Specification-first autonomous agent workflows
- Quality, review, and ownership of AI output
- AI policy for Google Summer of Code
- Reviewing the pglz optimization project
- Why the benchmark methodology was misleading
- Compression correctness and corruption tests
- Byte-compatible scope and revised benchmark plan