I noticed in the 2.7.1 war distro that it is using postgresql-8.4-701.jdbc3.jar. I plan on using GeoServer with the latest PostgreSQL 9.4/PostGIS 2.1 releases.
I found this discussion a few years back about the topic: http://sourceforge.net/p/geoserver/mailman/message/30164784/
Stating that the reason for using the 8.4 driver is backwards compatibility. But from what I understand, all Postgres JDBC drivers are backwards compatible. My concern now is forward compatibility. So my question is what kind of test coverage does GeoServer have with regard to PostgreSQL 9.x / PostGIS 2.1 datastores? What would be your concerns about using an updated driver?
I’m looking at configuring a connection pool using JNDI with Jetty 9.x and using the latest 9.4 jdbc driver. So I would probably remove the 8.4 driver from war libs to avoid conflicts.
We have recently restored automated postgis testing on our build box, Torben has the details on what versions are used (I imagine it is the latest since that is what are working against).
If you would like to build and test geotools and geoserver with a more recent driver we would be interested in your feedback. The GeoTools developers guide has some instructions on setting up the “online tests” used to work against your local PostGIS. The tests are self contained and will create the tables required before use.
I noticed in the 2.7.1 war distro that it is using postgresql-8.4-701.jdbc3.jar. I plan on using GeoServer with the latest PostgreSQL 9.4/PostGIS 2.1 releases.
I found this discussion a few years back about the topic: http://sourceforge.net/p/geoserver/mailman/message/30164784/
Stating that the reason for using the 8.4 driver is backwards compatibility. But from what I understand, all Postgres JDBC drivers are backwards compatible. My concern now is forward compatibility. So my question is what kind of test coverage does GeoServer have with regard to PostgreSQL 9.x / PostGIS 2.1 datastores? What would be your concerns about using an updated driver?
I’m looking at configuring a connection pool using JNDI with Jetty 9.x and using the latest 9.4 jdbc driver. So I would probably remove the 8.4 driver from war libs to avoid conflicts.
We have recently restored automated postgis testing on our build box, Torben has the details on what versions are used (I imagine it is the latest since that is what are working against).
If you would like to build and test geotools and geoserver with a more recent driver we would be interested in your feedback. The GeoTools developers guide has some instructions on setting up the “online tests” used to work against your local PostGIS. The tests are self contained and will create the tables required before use.
I noticed in the 2.7.1 war distro that it is using postgresql-8.4-701.jdbc3.jar. I plan on using GeoServer with the latest PostgreSQL 9.4/PostGIS 2.1 releases.
I found this discussion a few years back about the topic: http://sourceforge.net/p/geoserver/mailman/message/30164784/
Stating that the reason for using the 8.4 driver is backwards compatibility. But from what I understand, all Postgres JDBC drivers are backwards compatible. My concern now is forward compatibility. So my question is what kind of test coverage does GeoServer have with regard to PostgreSQL 9.x / PostGIS 2.1 datastores? What would be your concerns about using an updated driver?
I’m looking at configuring a connection pool using JNDI with Jetty 9.x and using the latest 9.4 jdbc driver. So I would probably remove the 8.4 driver from war libs to avoid conflicts.
Hey Torben, thanks for the research So Jason it looks like we test both geotools and this driver with a newer PostgreSQL / PostGIS combination.
Jason if you want we can ask about using a newer driver (of course your downstream applications is free to choose an appropriate driver through careful use of maven dependency and excludes).
We have recently restored automated postgis testing on our build box, Torben has the details on what versions are used (I imagine it is the latest since that is what are working against).
If you would like to build and test geotools and geoserver with a more recent driver we would be interested in your feedback. The GeoTools developers guide has some instructions on setting up the “online tests” used to work against your local PostGIS. The tests are self contained and will create the tables required before use.
I noticed in the 2.7.1 war distro that it is using postgresql-8.4-701.jdbc3.jar. I plan on using GeoServer with the latest PostgreSQL 9.4/PostGIS 2.1 releases.
I found this discussion a few years back about the topic: http://sourceforge.net/p/geoserver/mailman/message/30164784/
Stating that the reason for using the 8.4 driver is backwards compatibility. But from what I understand, all Postgres JDBC drivers are backwards compatible. My concern now is forward compatibility. So my question is what kind of test coverage does GeoServer have with regard to PostgreSQL 9.x / PostGIS 2.1 datastores? What would be your concerns about using an updated driver?
I’m looking at configuring a connection pool using JNDI with Jetty 9.x and using the latest 9.4 jdbc driver. So I would probably remove the 8.4 driver from war libs to avoid conflicts.
There are two or three tests that fail if you go to the latest version of the JDBC driver, 9.4-1201-jdbc41. I haven’t had a chance to look at them yet.
We have recently restored automated postgis testing on our build box, Torben has the details on what versions are used (I imagine it is the latest since that is what are working against).
If you would like to build and test geotools and geoserver with a more recent driver we would be interested in your feedback. The GeoTools developers guide has some instructions on setting up the “online tests” used to work against your local PostGIS. The tests are self contained and will create the tables required before use.
I noticed in the 2.7.1 war distro that it is using postgresql-8.4-701.jdbc3.jar. I plan on using GeoServer with the latest PostgreSQL 9.4/PostGIS 2.1 releases.
I found this discussion a few years back about the topic: http://sourceforge.net/p/geoserver/mailman/message/30164784/
Stating that the reason for using the 8.4 driver is backwards compatibility. But from what I understand, all Postgres JDBC drivers are backwards compatible. My concern now is forward compatibility. So my question is what kind of test coverage does GeoServer have with regard to PostgreSQL 9.x / PostGIS 2.1 datastores? What would be your concerns about using an updated driver?
I’m looking at configuring a connection pool using JNDI with Jetty 9.x and using the latest 9.4 jdbc driver. So I would probably remove the 8.4 driver from war libs to avoid conflicts.
There are two or three tests that fail if you go to the latest version of the JDBC driver, 9.4-1201-jdbc41. I haven’t had a chance to look at them yet.
Hey Torben, thanks for the research So Jason it looks like we test both geotools and this driver with a newer PostgreSQL / PostGIS combination.
Jason if you want we can ask about using a newer driver (of course your downstream applications is free to choose an appropriate driver through careful use of maven dependency and excludes).
We have recently restored automated postgis testing on our build box, Torben has the details on what versions are used (I imagine it is the latest since that is what are working against).
If you would like to build and test geotools and geoserver with a more recent driver we would be interested in your feedback. The GeoTools developers guide has some instructions on setting up the “online tests” used to work against your local PostGIS. The tests are self contained and will create the tables required before use.
I noticed in the 2.7.1 war distro that it is using postgresql-8.4-701.jdbc3.jar. I plan on using GeoServer with the latest PostgreSQL 9.4/PostGIS 2.1 releases.
I found this discussion a few years back about the topic: http://sourceforge.net/p/geoserver/mailman/message/30164784/
Stating that the reason for using the 8.4 driver is backwards compatibility. But from what I understand, all Postgres JDBC drivers are backwards compatible. My concern now is forward compatibility. So my question is what kind of test coverage does GeoServer have with regard to PostgreSQL 9.x / PostGIS 2.1 datastores? What would be your concerns about using an updated driver?
I’m looking at configuring a connection pool using JNDI with Jetty 9.x and using the latest 9.4 jdbc driver. So I would probably remove the 8.4 driver from war libs to avoid conflicts.
So Jason it looks like we test both geotools and this driver with a newer PostgreSQL / PostGIS combination.