We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Related to #1, basically pg_pgbouncer.sql is now being used for testing. It always sets up a running pgbouncer in some way that makes it easy to test.
I think it does make sense to have an easy way to set up a simple pgbouncer, but it should not be done by CREATE EXTENSION imho.
CREATE EXTENSION
Maybe something like calling a function after CREATE EXTENSION to do that:
SELECT pg_pgbouncer.setup_default()
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Related to #1, basically pg_pgbouncer.sql is now being used for testing. It always sets up a running pgbouncer in some way that makes it easy to test.
I think it does make sense to have an easy way to set up a simple pgbouncer, but it should not be done by
CREATE EXTENSION
imho.Maybe something like calling a function after CREATE EXTENSION to do that:
The text was updated successfully, but these errors were encountered: