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.
Planet PostgreSQL files mainly under programming. We currently carry 28 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Postgr |
| Canonical URL | https://postgr.es/p/9ky |
| Publication time | Wed, 27 May 2026 01:00:00 +0000 |
| Retrieval time | 2026-05-27T01:07:56.169Z |
| Last seen | 2026-05-27T01:07:56.169Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | bWZbBUxGB0qj · 3 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
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
