Repository navigation
docs: explain client reuse and replacement for waiting pool callers - #3816
Closed
tonyzedginidze wants to merge 2 commits into
Closed
tonyzedginidze wants to merge 2 commits into
tonyzedginidze wants to merge 2 commits into
Conversation
Repository owner
locked as spam and limited conversation to collaborators
Oct 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Explain how releasing the only checked-out client affects a waiting caller: a normal release reuses the healthy client, while an explicit error release removes it and connects a replacement. Add an accessible figure and downloadable editable SVG beside the existing release warning. Scope the example to an active pool with successful connections, no checkout timeout and no lifetime/usage expiry; it does not advise discarding on every query error.
Validation: actual current pg-pool with its supported injected Client verifies queue/idle counts, same-client normal handoff, different-client error handoff and cleanup. Complete MDX compiles and both public assets resolve. Inspected the 580 × 608 PNG. This exercises actual pool coordination using a test transport, not a real PostgreSQL integration test; the full website build was not run. Runtime files are unchanged.
I work on svgdiagram.ai, which generated the layout. SVG is editable without a service account. Embedded Inter font data carries its separate OFL copyright/license notice; the diagram follows the repository license. No service credit appears in the guide.