Re: Built-in connection pooling
От | Robert Haas |
---|---|
Тема | Re: Built-in connection pooling |
Дата | |
Msg-id | CA+TgmobKj5AoEY=u+TatFed=fx3PD77QArJU7XSWKrSC8Qt5eA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Built-in connection pooling (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>) |
Ответы |
Re: Built-in connection pooling
|
Список | pgsql-hackers |
On Tue, Apr 24, 2018 at 1:00 PM, Konstantin Knizhnik <k.knizhnik@postgrespro.ru> wrote: > My expectation is that there are very few of them which has session-level > lifetime. > Unfortunately it is not so easy to locate all such places. Once such > variables are located, them can be saved in session context and restored on > reschedule. The difficulty of finding them all is really the problem. If we had a reliable way to list everything that needs to be moved into session state, then we could try to come up with a design to do that. Otherwise, we're just swatting issues one by one and I bet we're missing quite a few. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: