BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//HasGeek//NONSGML Funnel//EN
DESCRIPTION:Hands-on workshop - Rootconf Topical Edition on Databases
X-WR-CALDESC:Hands-on workshop - Rootconf Topical Edition on Databases
NAME:Write path in OLTP workloads (PostgreSQL)
X-WR-CALNAME:Write path in OLTP workloads (PostgreSQL)
REFRESH-INTERVAL;VALUE=DURATION:PT12H
SUMMARY:Write path in OLTP workloads (PostgreSQL)
TIMEZONE-ID:Asia/Kolkata
X-PUBLISHED-TTL:PT12H
X-WR-TIMEZONE:Asia/Kolkata
BEGIN:VEVENT
SUMMARY:Write path in OLTP workloads (PostgreSQL)
DTSTART:20260612T043000Z
DTEND:20260612T070000Z
DTSTAMP:20260607T060315Z
UID:session/PEyDDwtNiAjaA1iwgAj1AE@hasgeek.com
SEQUENCE:6
CREATED:20260607T020825Z
DESCRIPTION:## 🎯 Target audience\n- Engineers who work with PostgreSQL 
 or other OLTP databases and want to understand what happens during writes\
 n- Those looking to reason about durability\, performance\, and isolation 
 trade-offs in production systems\n\n## 📘 Workshop overview\nThis worksh
 op uses PostgreSQL as a concrete example to explore the full write path in
  OLTP workloads — from durability guarantees to high availability. Each 
 section builds on the last: once you have durability\, how do you get perf
 ormance? Once you have both\, how do you handle concurrent writes? And onc
 e all of that works\, how do you keep it running when a node goes down?\n\
 nThe workshop pairs internals with observability — what to measure\, how
  to debug\, and how to tune — at each stage.\n\n## ✅ Learning outcomes
 \nBy the end of the workshop\, participants will be able to understand:\n-
  How PostgreSQL implements durability using WAL\, fsync\, and group commit
 \n- How the background writer and checkpointer manage write throughput\n- 
 How MVCC provides concurrent readers a consistent view during writes\n- Ho
 w visibility checks\, hint bits\, and hot row contention show up in practi
 ce\n- How streaming replication extends the write path to standby nodes\n-
  Operational lessons from running PostgreSQL in production for write-heavy
  workloads\n\n## 🧩 Workshop modules\n**1. Write durability guarantees**
 \nHow PostgreSQL ensures committed transactions survive crashes. Covers WA
 L record structure\, the lifecycle of a WAL record from generation to flus
 h\, fsync and group commit\, and parameters like `synchronous_commit`\, `w
 al_sync_method`\, and `commit_delay`. Storage characteristics (SSD vs HDD\
 , write cache) and their effect on durability expectations.\n\n**2. Write 
 performance**\nHow to sustain high write throughput without compromising g
 uarantees. Covers how WAL bounds maximum throughput\, group commit under c
 oncurrent workloads\, batching and transaction sizing\, and how the backgr
 ound writer and checkpointer manage dirty buffers. Observability via `pg_s
 tat_bgwriter`.\n\n**3. Concurrency control**\nHow PostgreSQL handles concu
 rrent writes correctly. Covers SQL isolation levels\, MVCC — how row ver
 sions are created\, visibility rules\, and where WAL fits in — visibilit
 y checks using transaction snapshots\, hint bits and clog lookups\, hot ro
 w contention\, lock waits via `pg_locks` and `pg_stat_activity`\, and prev
 enting lost updates with `SELECT FOR UPDATE` and optimistic concurrency co
 ntrol.\n\n**4. High availability**\nHow the write path extends into replic
 ation and failover. Covers streaming replication\, physical vs logical rep
 lication\, synchronous vs asynchronous modes\, replication slots\, WAL ret
 ention\, and operational pitfalls like disk bloat from inactive slots.\n\n
 **5. Operational lessons from production**\nWar stories and concrete scena
 rios from running PostgreSQL in production for write-heavy OLTP workloads.
  Covers WAL volume and checkpoint tuning\, bulk ingest and bursty workload
  patterns\, write contention from centralized counters and hot partitions\
 , and mitigation strategies including schema changes\, sharding\, and quer
 y rewrites.\n\n## 🛠 Tooling & prerequisites\n*To be shared by the instr
 uctor.*\n\n## About the instructor\n[**Amit Prabhudesai**](https://www.lin
 kedin.com/in/amitprabhudesai/)\, Engineering Manager at Microsoft.\n\n## H
 ow to attend\nThis workshop is open for **[Rootconf members](https://hasge
 ek.com/rootconf#memberships)** and for **[Rootconf Data Edition ticket buy
 ers](https://hasgeek.com/rootconf/topical-edition-on-databases#tickets)**\
 n\n**This workshop is open to 30 participants (in-person) & hybrid access 
 for remote attendees. Seats for in-person participants will be available o
 n first-come-first-served basis.** 🎟️    \n\n## Contact information 
 ☎️\nFor inquiries about the workshop\, contact [+91-7676332020](tel:+9
 17676332020) or write to [info@hasgeek.com](mailto:info@hasgeek.com).
LAST-MODIFIED:20260607T020825Z
LOCATION:Bangalore - https://hasgeek.com/rootconf/oltp-workloads-postgresq
 l-workshop/
ORGANIZER;CN=Rootconf:MAILTO:no-reply@hasgeek.com
URL:https://hasgeek.com/rootconf/oltp-workloads-postgresql-workshop/
BEGIN:VALARM
ACTION:display
DESCRIPTION:Write path in OLTP workloads (PostgreSQL) in 5 minutes
TRIGGER:-PT5M
END:VALARM
END:VEVENT
END:VCALENDAR