Skip to content

Commit f37ed11

Browse files
Fixed typo
1 parent a270390 commit f37ed11

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
This scenario illustrates how the PostgreSQL JDBC driver behaves when either using the `socketTimeout` connection property or calling `java.sql.Statement.setQueryTimeout()`.
22

3-
When the `socketTimeout` is reached, the JDBC driver closes the underlying connection; whereas the `queryTimeout` leaves the connection in a usable state.
3+
When the `socketTimeout` is reached, the JDBC driver closes the underlying connection; whereas the `queryTimeout` leaves the connection in an usable state.
44

55
This basically forbids setting `socketTimeout` when connection pooling is used in a liberal fashion, as the pool is not informed that the connection is closed.
66
With "liberal fashion" I mean (using e.g. the [Tomcat JDBC pool](https://tomcat.apache.org/tomcat-8.0-doc/jdbc-pool.html), the default of Spring-Boot): you're not explicitly setting either `testOnReturn` or `testOnBorrow` along with an `validationInterval` less than the `socketTimeout`.

0 commit comments

Comments
 (0)