Postgres Hacking 101 with Andrey

session summary

After explaining CommitFest and release-cycle mechanics, the group designed extensible command-completion tags instead of changing PostgreSQL's long-stable protocol output directly. A format string could optionally include timestamps and affected relations, especially for readable dump and restore progress. They postponed implementation, then reviewed a libpq patch that randomizes a multi-host connection list. The Fisher-Yates shuffle appeared correct despite confusing code and minor whitespace issues, but they noted that randomization alone cannot avoid a slow replica and suggested future latency-aware selection.

timecodes

1. 00:30 CommitFest cadence and the PostgreSQL release cycle
2. 07:00 What command-completion tags currently report
3. 11:00 Relation names and compatibility constraints
4. 19:00 Designing a configurable command-tag format
5. 24:30 Reviewing libpq multi-host load balancing
6. 27:00 Random ordering cannot avoid a slow replica
7. 32:30 Refactoring addresses out of PGconn
8. 35:00 Checking the Fisher-Yates shuffle implementation