Christophe Pettus: All Your GUCs in a Row: cluster_name
The article discusses the importance of the cluster_name parameter in PostgreSQL for distinguishing between multiple instances. While it primarily serves as a cosmetic label, it also plays a crucial role in synchronous replication for standby servers. Properly managing this parameter can prevent operational issues and improve clarity in process listings.
- ▪The cluster_name parameter helps differentiate between multiple PostgreSQL instances in process listings.
- ▪On standby servers, the cluster_name can affect synchronous replication decisions.
- ▪Changing the cluster_name on a replica without proper consideration can lead to operational issues.
Opening excerpt (first ~120 words) tap to expand
2026-05-26 3 min PostgreSQL All Your GUCs in a Row: cluster_name cluster_name looks like a cosmetic: a label that shows up in ps output so you can tell your three postgres instances apart. On a primary, that’s all it is. On a standby, it can quietly become the name the primary uses to decide whether synchronous replication is satisfied, which is a much bigger job for a parameter most people set and forget. The default is the empty string, meaning no name and no change to the process title. The context is postmaster, so setting it costs a restart; that’s fine, because this is a label rather than a knob, and you set a label once at provisioning time. It arrived in PostgreSQL 9.5.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Postgr.
Discussion
0 commentsMore from Postgr
