Christophe Pettus: All Your GUCs in a Row: client_min_messages
The article discusses the PostgreSQL parameter client_min_messages, which controls the verbosity of messages sent to the client. It highlights common confusions with similar parameters and explains the implications of setting different levels. The author advises using this parameter judiciously to avoid missing important warnings while silencing unnecessary notices.
- ▪client_min_messages controls the messages sent to the client, with levels ranging from DEBUG5 to ERROR.
- ▪There is a common confusion between client_min_messages and log_min_messages, as they rank the same terms differently.
- ▪Setting client_min_messages to WARNING can help reduce noise from schema tooling while still allowing important warnings to be seen.
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/9ke |
| Publication time | Tue, 26 May 2026 01:00:00 +0000 |
| Retrieval time | 2026-05-26T01:07:40.934Z |
| Last seen | 2026-05-26T01:07:40.934Z |
| 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-25 3 min PostgreSQL All Your GUCs in a Row: client_min_messages client_min_messages controls how much the server says to you: the messages that come back over the wire to your session. It is constantly confused with the parameter that controls what the server writes to its own log. Those are different concerns with different parameters, and the confusion is where most of the trouble starts. The default is NOTICE, the context is user (so any role can set it per session, per role, or per database, with no restart involved), and the levels run in increasing severity: DEBUG5 through DEBUG1, then LOG, NOTICE, WARNING, ERROR. Set the parameter to a level and you get that level plus everything more severe; the higher you set it, the quieter your session gets. ERROR is as high as it goes.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Postgr.
Discussion
0 commentsMore from Postgr
