Re: WITH HOLD and pooled connections
От | Tom Lane |
---|---|
Тема | Re: WITH HOLD and pooled connections |
Дата | |
Msg-id | 878.1060378438@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: WITH HOLD and pooled connections (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: WITH HOLD and pooled connections
|
Список | pgsql-hackers |
Andrew Dunstan <andrew@dunslane.net> writes: > Tom Lane wrote: >> Prepared statements would be just as much of a problem. I think the >> correct answer is simply "don't use those features in a pooled >> environment". > Ouch. Double ouch in fact. I'm using prepared statements extensively in > my current (pooled conn) app. All pure selects. > Can this be narrowed down a bit? Is it a problem on all query types? The point is just that there's no infrastructure to manage prepared statements, eg for a thread to discover whether someone has already prepped a particular statement on the current connection. Evidently you have set things up so that you don't need to do that. Panic not. regards, tom lane
В списке pgsql-hackers по дате отправления: