Re: Built-in connection pooling
От | Robert Haas |
---|---|
Тема | Re: Built-in connection pooling |
Дата | |
Msg-id | CA+TgmoaySCD772T4aLHGkXfpRkbtzReDCukKO+ue_mantP7KFw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Built-in connection pooling (Bruce Momjian <bruce@momjian.us>) |
Ответы |
Re: Built-in connection pooling
|
Список | pgsql-hackers |
On Mon, Apr 23, 2018 at 7:59 PM, Bruce Momjian <bruce@momjian.us> wrote: > So, instead of trying to multiplex multiple sessions in a single > operating system process, why don't we try to reduce the overhead of > idle sessions that each have an operating system process? We already > use procArray to reduce the number of _assigned_ PGPROC entries we have > to scan. Why can't we create another array that only contains _active_ > sessions, i.e. those not in a transaction. In what places can procArray > scans be changed to use this new array? There are lots of places where scans would benefit, but the cost of maintaining the new array would be very high in some workloads, so I don't think you'd come out ahead overall. Feel free to code it up and test it, though. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: