Does creating readOnly connections, when possible, free upresources in Postgres?
От | David Kremer |
---|---|
Тема | Does creating readOnly connections, when possible, free upresources in Postgres? |
Дата | |
Msg-id | trinity-98ed82ed-5c4a-46ae-8f15-fcb75b13b3d7-1548612669012@3c-app-mailcom-bs03 обсуждение исходный текст |
Ответы |
Re: Does creating readOnly connections, when possible, free up resources in Postgres?
Re: Does creating readOnly connections, when possible, free upresources in Postgres? Re: Does creating readOnly connections, when possible, free upresources in Postgres? |
Список | pgsql-general |
(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?
В списке pgsql-general по дате отправления: