Adding onto the above: I’ve tried this out locally, and it almost works.

One sticking point is in Poolex.Private.Monitoring on line 9:

This crashes if pool_id is a tuple because the tuple doesn’t work with String.Chars.

“Fixing” it by using :"#{inspect(pool_id)}_references" seems to work, but ends up right back at the making-atoms-dynamically-at-runtime mess we were trying to avoid.

Going to poke at this a bit more when I’ve got time this week.

Full support for GenServer.name() was implemented in version 1.0.0-rc.0. I’m testing the version in our applications, and so far everything looks good. If you check it yourself, please share the results.

Skimming the source of Poolex, it seems like the pool_id value is always used as the first argument to GenServer.call and GenServer.cast.

Dialyzer will complain, but you could pass anything from GenServer.name() there - for instance, a :via tuple against a Registry that tracks pools by UUID.

This is an excellent point about the Registry and :via tuples. It can be the best solution for supporting this kind of pool ID.