jhg03a opened a new issue, #7018: URL: https://github.com/apache/trafficcontrol/issues/7018
<!-- ************ STOP!! ************ If this issue identifies a security vulnerability, DO NOT submit it! Instead, contact the Apache Traffic Control Security Team at [email protected] and follow the guidelines at https://apache.org/security regarding vulnerability disclosure. - For *SUPPORT QUESTIONS*, use the #traffic-control channel on the ASF slack (https://s.apache.org/tc-slack-request) or the Traffic Control Users mailing list (send an email to [email protected] to subscribe). - Before submitting, please **SEARCH GITHUB** for a similar issue or PR * https://github.com/apache/trafficcontrol/issues * https://github.com/apache/trafficcontrol/pulls --> <!-- Do not submit security vulnerabilities or support requests here - see above --> ## This Improvement request (usability, performance, tech debt, etc.) affects these Traffic Control components: <!-- delete all those that don't apply --> - Traffic Ops ## Current behavior: <!-- Describe how the current features are insufficient. --> The current TO implementation uses prepared queries when interacting with the server objects. The use of prepared queries is incompatible with pgBouncer in transaction pooling mode. As a result, only session mode is available which still requires the use of TO-side database connection caps. ## New behavior: <!-- Describe how this change would improve Traffic Control --> I'd like to see this removed so that transaction pooling will work with pgBouncer and therefore can uncap TO's database connection limits for significantly more efficient transaction throughput. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
