c8c80cfbbd
## Description A few users noticed that Appsmith was creating surplus connections in their database even when connected through a single datasource. Ideally, this number should start from 5 and not exceed beyond total concurrent requests in the app/workspace. However, it seems like HikariCP tends to send the following query outside of the connection pool size for every query that we try to run. ``` SET application_name = 'PostreSQL JDBC Driver' ``` This PR has introduced a custom set application name to all connections to avoid sending this set query along with every execution request, according to this [post](https://seethawenner.medium.com/improve-the-performance-of-your-aws-rds-postgres-database-by-avoiding-session-pinning-a4f010109bed). Unfortunately, while this solution has lowered the number of such set queries, they have not disappeared entirely. There is another alternative [here](https://github.com/appsmithorg/appsmith/pull/21780) that requires us to let users know about minimum version support for PG so we will not be opting for that solution at this time. Fixes #14117 ## Type of change - Bug fix (non-breaking change which fixes an issue) ## How Has This Been Tested? - Manual - JUnit ### Test Plan > Add Testsmith test cases links that relate to this PR ### Issues raised during DP testing > Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR) ## Checklist: ### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag ### QA activity: - [ ] Test plan has been approved by relevant developers - [ ] Test plan has been peer reviewed by QA - [ ] Cypress test cases have been added and approved by either SDET or manual QA - [ ] Organized project review call with relevant stakeholders after Round 1/2 of QA - [ ] Added Test Plan Approved label after reveiwing all Cypress test |
||
|---|---|---|
| .. | ||
| src | ||
| plugin.properties | ||
| pom.xml | ||