Re: Best practices for connection factory configurations when using connection pooling?
It is a valid assumption (secondary using smaller pool).
If you do all of your schema generation up front you won't need any secondary connections for those ops also.
If your chosen value generation strategies don't need a DB connection (e.g "identity", "uuid", "uuid-hex", "auid", etc) then you don't need any secondary connections for those ops also.
You could even get to not needing a pool for secondary in those situations