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.
Feature
Introducing plugins.
The idea is to perform an action based on a query.
Currently, the actions I'm thinking of could be:
The last one isn't supported yet, but maybe someone with a use case could contribute a PR.
Why
Well, a couple reasons. First, I want to block users from querying certain system tables. Postgres doesn't let me do that, and that's fine. The query planner may need them, but the user doesn't need to explicitly query them, so that solves that problem.
Another reason, I just discovered the joy of using IDEs like DataGrip (IntelliJ), and they get pretty upset when they are talking to a pooler. The included
fool_datagrip
function returns fake information about the "database" It's connected to, so DataGrip doesn't complain.Bug fixes
Increase default pool reaper rate to match
min(idle_timeout, server_lifetime)
.