feat(pg-parser): ignore deletion of startup request mocks during match #1341
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.
Related Issue
Closes: #[issue number that will be closed through this PR]
Describe the changes you've made
Some applications are making more connections with Postgres during test mode than it did during record mode. So there are also more auth requests from the application during test mode, but we didn't have sufficient auth packets - which leads to auth failures in some requests.
Why did this happen?
Since the application is able to execute much faster during testmode, it tries to increase the connection pool to handle higher request throughput. This seems to be normal application behaviour for psycog3
Fix: We are making database connection related properties like authentication re-useable to handle cases where more connections are created during test mode.
Type of change
Please let us know if any test cases are added
Please describe the tests(if any). Provide instructions how its affecting the coverage.
Describe if there is any unusual behaviour of your code(Write
NA
if there isn't)A clear and concise description of it.
Checklist:
Screenshots (if any)