MONGOC_CLIENT_POOL_MIN_SIZE(3)

💅 MONGOC_CLIENT_POOL_MIN_SIZE 💅

okay bestie, we're in the libmongoc era and today's main character is mongoc_client_pool_min_size — a little function that, no cap, is deprecated. sit with me, this one's a whole saga. 🫶

---

🚨 WARNING (read this first, fr fr) 🚨

Deprecated since version 1.9.0. This function is deprecated because its behavior does not match what developers expect from a "minimum pool size", and its actual behavior is likely to hurt performance. 😭

Applications should not call this function. Instead, they should just accept the default behavior, which is to keep all idle clients that are pushed into the pool. periodt. ✨

---

✨ SYNOPSIS ✨

void
mongoc_client_pool_min_size (mongoc_client_pool_t *pool,
                             uint32_t min_pool_size);

So here's the tea: this function actually sets the maximum number of idle clients to be kept in the pool. Any idle clients in excess of the maximum are destroyed. yes, you read that right — it's giving "minimum" but it's lowkey doing "maximum" energy, and that's exactly why it got deprecated. 🙈

---

🌸 PARAMETERS 🌸

• pool — A mongoc_client_pool_t. the pool in question, the whole vibe. 🦋
• min_pool_size — The number of idle clients to keep in the pool. ⭐

---

🧚 THREAD SAFETY 🧚

This function is safe to call from multiple threads. slay. 👑

Subsequent calls to mongoc_client_pool_push() respect the new minimum size, and close the least recently used mongoc_client_t if the minimum size is exceeded. so like, LRU girlies get evicted first — iykyk. 💀

---

👑 AUTHOR 👑

MongoDB, Inc

---

💖 COPYRIGHT 💖

2009-present, MongoDB, Inc.

---

and that's the whole page, bestie — no notes, we ate. 💅✨

signing off from libmongoc version 1.30.13, dated Oct 09, 2026 — mwah, take care of yourselves and please don't call the deprecated function 🎀🦋