DevOps, CI/CD and Automation

Greetings!

Do you agree that the Oracle "Shared Server" technology (MTS) is a totally separate concept from connection pooling?

The following is an excerpt from the below listed web page.

"For even better resource management, shared server can be configured for connection pooling. Connection pooling lets a dispatcher support more users by enabling the database server to time-out protocol connections and to use those connections to service an active session."

http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14231/manproc.htm#i1010000

Does that excerpt refer to how Shared Server can be configured to work in conjunction with connection pooling, not to deliver connection pooling?

My understanding is that the SHARED_SERVERS capability in Oracle can help a database server that is at risk of becoming overloaded with processes. And, that is very seperate from connection pooling, which can result in potentially fewer connection objects consuming memory depending on how many users there are and how much idle time those users have. But, mainly, since connections in the pool remain open for quite some time waiting around for a user to make use of them, the processing-time expense of opening a brand new database connection every time a web page is requested is saved with connection pooling in place.

What are your thoughts? Did I misinterpret the excerpt I pasted from the above Oracle URL?

Thanks for your help!

Rachel