Christophe Pettus: All Your GUCs in a Row: client_connection_check_interval
The article discusses the PostgreSQL parameter 'client_connection_check_interval', which was introduced in version 14. This parameter helps detect when a client connection is lost during long-running queries, preventing unnecessary resource usage. It is recommended to enable this parameter for better management of analytics workloads.
- ▪The 'client_connection_check_interval' parameter polls the client socket during query execution to check for closed connections.
- ▪The default setting for this parameter is 0, meaning it is disabled, which can lead to wasted resources on long-running queries.
- ▪Enabling this parameter can significantly improve performance for workloads with long queries, especially in managed PostgreSQL environments.
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/9jR |
| Publication time | Mon, 25 May 2026 01:00:00 +0000 |
| Retrieval time | 2026-05-25T01:07:35.186Z |
| Last seen | 2026-05-25T01:07:35.186Z |
| 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-24 4 min PostgreSQL All Your GUCs in a Row: client_connection_check_interval A genuinely useful parameter that almost nobody knows about. Added in PostgreSQL 14, off by default, fixes a specific pathology that anyone who has run analytics workloads has lived through at least once. The pathology A user runs an expensive query — a multi-hour analytics scan, a runaway report — and walks away. Or their laptop dies. Or their VPN drops. The TCP connection is gone, but PostgreSQL doesn’t know. The backend continues executing the query at full cost for the full duration, eventually completes, attempts to send the result to a socket that closed two hours ago, and only at that point notices the client is gone.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Postgr.
Discussion
0 commentsMore from Postgr
