Set Default Value of Queue_max_wait_ms to Zero, Because Current Value (five Seconds) Makes No Sense

Why it matters

The default value of queue_max_wait_ms was set to 5000 ms (five seconds), which rarely made sense in practice. This update sets it to zero by default to avoid unnecessary delays. Additionally, new separate settings replace_running_query_max_wait_ms, kafka_max_wait_ms, and connection_pool_max_wait_ms were introduced to provide clearer and more precise control over different wait scenarios, improving performance tuning and disambiguation.

How to use it

Users can rely on the new default value of queue_max_wait_ms = 0 without configuration. For finer control, they can set replace_running_query_max_wait_ms, kafka_max_wait_ms, and connection_pool_max_wait_ms explicitly in the server or client configurations to adjust wait time behavior for specific subsystems according to their needs.