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
Both the pgconfig and jdbcconfig examples store the Catalog and Config in a PostgreSQL database.
pgconfig
jdbcconfig
As the number of pods in a deployment increases, so do the chances of running out of server side connections.
At the geoserver-cloud side of the fence, we've tested using pgbouncer as a server-side connection pooler with several containers.
It'd be great if we can include such set up in the examples, especially due to the new support of auto-scaling.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Both the
pgconfig
andjdbcconfig
examples store the Catalog and Config in a PostgreSQL database.As the number of pods in a deployment increases, so do the chances of running out of server side connections.
At the geoserver-cloud side of the fence, we've tested using pgbouncer as a server-side connection pooler with several containers.
It'd be great if we can include such set up in the examples, especially due to the new support of auto-scaling.
The text was updated successfully, but these errors were encountered: