Skip to content
New issue

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

thoughts on : "automatically query for @@max_allowed_packet,@@wait_timeout to determine useful defaults #294

Open
jonnytest1 opened this issue Sep 25, 2024 · 2 comments

Comments

@jonnytest1
Copy link

ive had some connection problems for a while now and today i figured out that my server had lower wait_timeout than the default

but i was wondering : why just run a small
SELECT @@max_allowed_packet,@@wait_timeout

query to get those values directly from the server and include them accordingly
(unless of cause user provided parameters overwrite them)

@Orel-A
Copy link

Orel-A commented Nov 14, 2024

I suspect it's because the library waits for the first query to be made to add connections to the pool.
So if what you suggest needs to be implemented, then createPool() function will need to run this query as soon as it's called.

@jonnytest1
Copy link
Author

probably yes , but i can also imagine running it with the first query in an optimistic attempt 🤔 and wait_time can also be run with the first query either way

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants