Configuring a `Pool` for unlimited open connections will result in no connection reuse about mobc HOT 3 CLOSED

Awesome. No rush let me know if I can help.

from mobc.

@dcormier Good investigating. Would you like to submit a fix for this?

from mobc.

Thank you, @garrensmith.

Yes, I would like to. Right now I'm looking at addressing two things:

1. Treat max_idle == 0 as unlimited idle connections. In this case, open connections will be limited by max_open.
2. Allow Builder to be configured with max_idle > max_open when max_open == 0, matching the behavior of Pool::set_max_idle_conns() (see snippet below).

    pub async fn set_max_idle_conns(&self, n: u64) {
        let mut internals = self.0.internals.lock().await;
        internals.config.max_idle =
            if internals.config.max_open > 0 && n > internals.config.max_open {
                internals.config.max_open
            } else {
                n
            };

I think it'll be a couple of days before I have time to get all the tests in place to ensure the behavior is what's expected.

from mobc.