Skip to content
Hallway
0:00 / 0:00

#postgresql#writetuning#wal

Tuning PostgreSQL for High Write Workloads

Postgres Open

6.1K subscribers • 3 videos on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • Presented by Grant McAlister

Advanced. Deep dive for people who know the field.

56K views9 years ago2 recommendations

Databases and dataSystems programmingPostgresDatabase internalsPerformance and optimization

Grant McAlister explains how to optimize PostgreSQL performance for write-heavy applications, covering WAL, checkpointing, and index design.

Tuning PostgreSQL for High Write Workloads - Grant McAlister

Why it's here

2 people recommend this

What people say. Recommended for understanding how to optimize PostgreSQL write performance and mitigate index thrashing.

Moments people linked to

u/Frozen_Turtlein r/programming • Recommends

On “GUIDs are globally unique, but substrings of GUIDs aren't”

ULIDs are super useful to use as a PK in database that uses B-trees (e.g. PostGres) since it reduces index thrashing. i.e. it appends to the tree rather that inserting randomly into the middle of the tree. The video here is good, though it's not about ULIDs specifically.
2View on Reddit

u/CSI_Tech_Deptin r/PostgreSQL • Recommends

On “Huge DB with hash index usecase”

…hough hash index wasn't operated through WAL, but that was fixed I believe in version 10. You probably would also want to do sharding, which was also improved in version 10. This is actually a good talk about understanding how to get high write performance in postgresql (there is a pitch about aws Aurora at the end, but the information applies): link to this video Also your use case is what key/value stores supposed to specialize in, they concentrate on that and drop other features to make this use case faster. I would recommend Riak for this, since I used it and fits this use case well. The potential conflicts you could address through CRDTs. The problem with it is that the company behind it no lon…
1View on Reddit

u/CSI_Tech_Deptin r/PostgreSQL • Recommends

On “UUID field with BIGINT primary key write performance”

There's another concern: link to this video link to this video
1View on Reddit

u/CSI_Tech_Deptin r/PostgreSQL • Recommends

On “Table with unpredictable id”

Regarding performance my concern was about this: link to this video
1View on Reddit