{
  "id": 20488018,
  "title": "Beyond Disk and WAL: What Limits PostgreSQL Scaling?",
  "url": "https://urgent.news/2026/11/17/beyond-disk-and-wal-what-limits-postgresql-scaling",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-17T20:26:33.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/franckpachot/beyond-disk-and-wal-what-limits-postgresql-scaling-2ij0"
  },
  "original_language": "en",
  "account": "The investigation into PostgreSQL scaling reveals that while earlier tests improved read I/O and removed standby acknowledgment waiting, the primary node still experienced delays due to local WAL synchronization. This post revisits the diagnostic and examines the remaining bottlenecks. By setting session-level synchronous_commit=off, a successful commit response can be achieved before WAL is durable, potentially leading to data loss in the event of a crash. However, this method was used for diagnostic purposes in a controlled lab environment, deviating from the initial comparison with HorizonDB's high-availability features.\n\nThe study maintains both streaming replicas and enables WAL, fsync, and full_page_writes. Automatic Patroni failover is also paused during the diagnostic. To gather data, a Pgtcl connection with an override setting of synchronous_commit=off was used to execute a SHOW synchronous_commit query. The test revealed that 93.92% of sampled active-client observations were impacted by LWLock:BufferContent, indicating a wait for a lightweight lock protecting cached relation pages. This suggests that the primary bottleneck lies in managing access to in-memory pages within the PostgreSQL server.",
  "summary": "The earlier tests improved read I/O and removed standby acknowledgment waiting, but the primary still waited for local WAL synchronization. Separate, later durable-regime traces located substantial delay in guest-OS write admission. This post returns to the diagnostic where I stopped waiting for commit durability to see what remained. I used session-level synchronous_commit=off for the same…",
  "key_points": [
    "Primary node delays due to local WAL synchronization",
    "Setting synchronouscommit=off enables immediate commit response",
    "93.92% of active-client observations impacted by LWLock:BufferContent"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}