Re: Problem with JTA/JTS
От | Tom Lane |
---|---|
Тема | Re: Problem with JTA/JTS |
Дата | |
Msg-id | 6378.1024065974@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Problem with JTA/JTS (Dave Cramer <Dave@micro-automation.net>) |
Ответы |
Re: Problem with JTA/JTS
|
Список | pgsql-jdbc |
Dave Cramer <Dave@micro-automation.net> writes: > Ok, the problem is that PostgresDataSource does NOT pool connections. Well, that answers that ... On reflection though, the behavior Johan reports seems curious. Is it really possible that new connections could be launched faster than old ones shut down? The backend startup time is not trivial, and he is executing a query on each connection too. It's hard to believe that the backend shutdown time exceeds startup + query time. Can you think of any reason why the client-side connection closure might not get signaled to the backend immediately? If, say, there were some kind of TCP timeout involved, then the report would make a whole lot more sense. regards, tom lane
В списке pgsql-jdbc по дате отправления: