Comment 3 for bug 280145

My patch relies on proper exception chaining, which was introduced in Java 1.4. PostgreSQL's JDBC-driver tries to autodetect during its config phase whether to build it with or without exception chaining, mostly based on Java version.

On Debian, it seems the packaged driver isn't built with Java 1.4 or newer, because it doesn't properly chain exceptions.

This means substring searching still has to be a fallback option for the connection loss detection routine. A PostgreSQL JDBC-driver built with Java < 1.4 will add tracebacks to the error message to indicate chained exceptions, instead of using proper chaining.

*frustrated*