The information says that the jdbc4.1 is specific to jdk1.7 and jdk1.8.

but I believe it to be:
the jdbc4.1 is specific to jdk1.7;
the jdbc4.2 is specific to jdk1.8;

Please correct me if I'm wrong.

New connection property: autosave

conservative (default) -- rollback to savepoint only in case of "prepared statement does not exist" and "cached plan must not change result type". Then the driver would re-execute the statement ant it would pass through
never -- never set automatic safepoint. Note: in this mode statements might still fail with "cached plan must not change result type" in autoCommit=FALSE mode
always -- always rollback to "before statement execution" state in case of failure. This mode prevents "current transaction aborted" errors. It is similar to psql's ON_ERROR_ROLLBACK.
For autocommit=true the savepoint is not used.
In conservative mode, savepoint is used only for queries that return something.

It's unclear if I can query range types or insert range values via the driver (either through 'normal' mechanisms like setObject or through extensions).

If it's impossible, a short blurb somewhere stating that you can't use range types via JDBC would also help clarify things for future searchers too.

In changelog the release date of 9.4.1211 is (2016-16-16) and should be (2016-09-18)

The website needs the new build 1003 with new release notes, I haven't been able to find release notes for recent release.

Currently the URL https://jdbc.postgresql.org/documentation/publicapi/index.html does not display the Javadoc API documentation.
I think this happened after the recent release of the new JDBC driver revision.

The documentation doesn’t mention the parameter sslmode. While setting up a PostgreSQL environment, I came across http://www.postgresql.org/docs/9.4/static/libpq-ssl.html#LIBPQ-SSL-SSLMODE-STATEMENTS. I included sslmode=verify-full in my JDBC connection parameters which does affect the JDBC driver (a different SSLSocketFactory is used). The most obvious effect was that the server CA certificate in the default Java truststore is ignored, instead it has to be in ~/.postgresql/root.crt.

The web site is ambiguous is ambiguous in the license:

The PostgreSQL JDBC driver is distributed under the BSD license, same as the server.

The JDBC Driver does not use the same license as the PostgreSQL Server.

Change the text to be clear that it use the BSD 3-Clause License.

jdbc.postgresql.org points to http://mvnrepository.com/artifact/org.postgresql which is wrong, as this is NOT the central maven repository. Instead it must certainly point to http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.postgresql%22%20AND%20a%3A%22postgresql%22 which not only IS the central maven repository, but moreover direclty lists all available versions of pgjdbc.

fix documentation that says building requires ant

Acutally it is possible to connect without providing "database" parameter in the URL. PostgreSQL server will then try to connect to a database named like the "username" attempting the connect.

Will provide PR in few minutes.

There are 4 references to github/com.