Does creating readOnly connections, when possible, free upresources in Postgres?

(resending to remove HTML formatting)

I have an API server and I'm trying to be conscientious managing Postgres's resources carefully. On the client side, I
havea Hikari Pool. 

Usually when I need a connection, I simply create a default read/write connection, even if I don't plan to make any
updatesor inserts or hold any locks. But most of my database connections are in fact read-only. 

I saw that when you create a JDBC connection, you can specify readOnly=true. Would doing so somehow help Postgres
manageits other connections? Perhaps Postgres, knowing that a connection is readOnly and will never even attempt to do
anupdate, will free up some internal resources for other connections. Is this accurate?