Conversation
Keep NOTICE responses informational and restore built-in client RESET suppression. Avoid replaying Greengage startup metadata and remove duplicate cleanup warnings. Add a disposable pinned Greengage cluster to the Docker Nix runner and CI, cover cleanup and RELOAD behavior with BDD, and update Russian and English documentation.
Track the actual frontend bundle through the existing directory and recursive file watches. Remove the nonexistent index.html dependency that made every Cargo invocation rebuild pg_doorman.
This branch has not been deployed
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add global and per-pool
cleanup_server_querywithadaptive,always, andoffpolicies, so deployments can choose reset SQL supported by their backend. The default remains selective built-in cleanup; existing boolean settings remain compatible.Cleanup failures retire the backend while preserving completed client responses, including successful
COMMIT. NOTICE messages remain informational. Client reset batches continue to suppress redundant built-in cleanup, while configured cleanup retains its own policy.make test-greengageand a CI job using a pinned Greengage 7.5 image, a coordinator, and two primary segments. Tests cover backend reuse, distributed reset behavior, and the partial effect of Greengage'sDISCARD ALL.