hacking.postgres.tv
./menu

postgres=# select * from sessions where topic = 'commitfest';

#CommitFest

3 related sessions.

· 78:44 · details · youtube ↗

Agentic Hacking Postgres with Andrey, Kirk, and Nik

Review the PG20-2 backlog: minor upgrades, global temporary tables, wait instrumentation, and pg_stat_log.

The group turned a tour of the PG20-2 CommitFest into concrete review homework. They reconciled Andrey Borodin's prolific August as 25 currently authored entries, explored bounded pre-shutdown checkpoints and safe cache handoff for minor upgrades, and examined why global temporary tables require deep catalog, relcache, planner, statistics, and lifecycle work. They then compared Ilmar Yunusov's EXPLAIN wait-event patch with Dmitry Fomin's broader timing/tracing series, insisting on honest attribution and workload benchmarks. The most actionable outcome was pg_stat_log: Nikolay will independently benchmark and review its SQL-queryable error counters, Kirk will support the thread, Andrey will revisit Dmitry's series, and Kirk will revise his pg_dump placeholder interface.

[timecodes · 12]
  1. AI-assisted hacking and the PG20-2 review backlog
  2. Andrey's 25 authored patches and a September of reviews
  3. Making minor upgrades operationally safer
  4. Adaptive checkpoints before shutdown
  5. Can a restart preserve shared-buffer page data?
  6. Global temporary tables and their real use cases
  7. Why the GTT patch is more than ten thousand lines
  8. Revisiting the pg_dump table-data placeholder patch
  9. EXPLAIN waits versus general wait timing and tracing
  10. Assembly evidence, observer effect, and benchmark design
  11. pg_stat_log: SQL-queryable counters instead of log parsing
  12. Assigning reviews and concrete homework
#wait events#SQL#monitoring#AI-assisted hacking#hacking process#minor upgrades#temporary tables#CommitFest@Nikolay Samokhvalov@Andrey Borodin@Kirk Wolak
PG20-2GTT #6918EXPLAIN waits #6753wait timing #6984pg_stat_log #7162pg_dump patch
active

direct mapping
· 77:12 · details · youtube ↗

Agent hacking Postgres

Agent-assisted patch work around the wait-event timing submission.

The group reviewed Kirk Wolak's pg_dump patch for keeping loadable placeholders when table data is excluded, grounding the discussion in his large-table restore workflow. They debated a positive interface, filter-file actions, arbitrary dump queries, PII transformation, and referential-integrity risks, then posted supportive review feedback to pgsql-hackers. The final segment examined Salma El-Sayed's B-tree leaf-page merge design, including merged-page markers, scan correctness, vacuum cleanup, and review plans.

[timecodes · 8]
  1. Postgres 19 development opens and patches await review
  2. Kirk introduces the pg_dump placeholder patch
  3. Large-table dump and one-command restore use case
  4. Reviewing the option name and user interface
  5. Using AI to review design and mailing-list history
  6. Parallel chunks for restoring one large table
  7. Custom dump queries, filtering, and PII transformation
  8. B-tree leaf-page merge design and scan safety
#wait events#B-tree#AI-assisted hacking#hacking process#CommitFest@Nikolay Samokhvalov@Andrey Borodin@Kirk Wolak
-hackersCF #6984
active

correlated mapping
· 93:47 · details · youtube ↗

Wait-event tracing

Independent benchmarks, observer effect, coverage, and patch restructuring.

Dmitry Fomin presented a seven-patch wait-event tracing series, split for review but intended to provide complete transition timing and query attribution. The group designed an independent benchmark ladder covering vanilla, compiled-disabled, stats, and full trace modes; corrected pgbench workloads; and distinguished static overhead from observer effect. Preliminary runs showed no clear slowdown, but they added pg_stat_statements, wait-event counts, repeated rounds, raw results, and independent review before submission.

[timecodes · 8]
  1. Why sampled wait events miss short transitions
  2. Seven-patch tracing series and review structure
  3. Planning an independent overhead benchmark
  4. Designing high-transition pgbench workloads
  5. Five measurement levels and observer effect
  6. Stats versus full trace capture modes
  7. Correcting workload duration, rate limits, and logging
  8. Preliminary results and adding pg_stat_statements
#wait events#monitoring#CommitFest@Nikolay Samokhvalov@Kirk Wolak@Dmitry Fomin
benchmark #48coverage #49PR #2benchmark briefCF #6984
active

direct mapping