Re: libpq WSACleanup is not needed
От | James Mansion |
---|---|
Тема | Re: libpq WSACleanup is not needed |
Дата | |
Msg-id | 4973C226.7080102@mansionfamily.plus.com обсуждение исходный текст |
Ответ на | Re: libpq WSACleanup is not needed (Magnus Hagander <magnus@hagander.net>) |
Ответы |
Re: libpq WSACleanup is not needed
Re: libpq WSACleanup is not needed |
Список | pgsql-hackers |
Magnus Hagander wrote: > The use-case of rapidly creating and dropping connections isn't > particularly common, I think. And there is a perfectly functioning > workaround - something that we should perhaps document in the FAQ or > somewhere in the documentation? > Would it be accetable to do initialise if the number of connections is changing from 0, and tidy if the cumber goes back to 0? Applications that retain a connection would not suffer the cost on subsequent connect/disconnect. The init/term is the tidiest way to do it, but the above might help - perhaps init could just add a phantom usecount and work the same way. If you have a DLL for libpq, could you do it in process attach and detach? Wouldn't that be the most common case anyway? James
В списке pgsql-hackers по дате отправления: