diff options
| author | Hector Oswaldo Caballero <hector.caballero@ericsson.com> | 2016-11-01 12:33:42 -0400 |
|---|---|---|
| committer | Kaushik Lingarkar <kaushik.lingarkar@gmail.com> | 2019-12-17 19:15:22 +0000 |
| commit | 7b81b32a08fb5e711236c2a51871208025574135 (patch) | |
| tree | 02b27ed3eb94b1a13780bec199e7ea65109e4844 | |
| parent | a53bbb050b1fb54cb52a11b8046072a88abdb769 (diff) | |
Fix Postgresql JDBC driver leaking memory
Older versions of Postgresql JDBC driver rely on finalize() methods in
order to avoid leaking unclosed database objects. Given finalize
methods are unpredictable (no guarantee about prompt execution, if at
all), in some high load environments this could lead to a memory leak
with millions of JDBC objects pending finalization.
Newer versions of the Postgresql JDBC driver removed the use of finalize
methods to avoid this kind of issues.
Also provides an implementation of setQueryTimeout.
Bug: Issue 4848
Change-Id: Ia143f1df1d8e41686362fd76b9bc82e0046f9894
(cherry picked from commit 80476a51df8361814e9cd5d91ceb60e8bf41cae5)
| -rw-r--r-- | lib/BUCK | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -156,8 +156,8 @@ maven_jar( maven_jar( name = 'postgresql', - id = 'postgresql:postgresql:9.1-901-1.jdbc4', - sha1 = '9bfabe48876ec38f6cbaa6931bad05c64a9ea942', + id = 'org.postgresql:postgresql:9.4.1211.jre7', + sha1 = '56b01e9e667f408818a6ef06a89598dbab80687d', license = 'postgresql', attach_source = False, ) |