Обсуждение: Upgrade question, going from 8.3 to 9.1...

On Wed, Feb 15, 2012 at 2:20 PM, Ned Wolpert <ned.wolpert@gmail.com> wrote:
> Folks-
>
>   We're in the process of upgrading our postgresql install from 8.3 to
> 9.1.2. Our main application is using postgresql-8.3-606.jdbc3.jar against
> the existing postgresql database. (Java jdk1.6.0_29, Oracle's version, not
> OpenJDK.  Its in use by hibernate. (Other Java applications use the database
> too, but mostly via hibernate or rbatis)
>
>   My questions are:
> 1) is it necessary to upgrade the jdbc jar file to the 9.1 version, or is
> the 8.3 version 'upwards' compatible? If it is, can someone point out me to
> what I would fail in apps that did not upgrade?
> 2) Even though we are not using features from the JDBC4 version, should we
> still use the JDBC4 variant due to the 1.6 JDK version?
> 3) Is there any potential issues if an application is using the latest 9.1
> JDBC driver against postgresql 8.3.x database?
>
> Obviously, we're hoping not to require an updated jar file, and just delay
> the upgrade until the next application release. But I need to know if
> upgrading the JDBC driver with the database upgrade cannot be avoided.
>

Ned,

Largely depends on what you are doing. If you are using any
databasemeta data functions then you may run into issues, if you are
just doing select, insert, update, delete you should be OK


Dave Cramer

dave.cramer(at)credativ(dot)ca
http://www.credativ.ca

My memory seems to be failing, yes, you will probably need a newer driver.
Dave Cramer

dave.cramer(at)credativ(dot)ca
http://www.credativ.ca



2012/2/15 Віталій Тимчишин <tivv00@gmail.com>:
> I do remember some problems discussed with 9.1. AFAIR here it
> is: http://grokbase.com/t/postgresql/pgsql-hackers/114jz3zdpb/jdbc-connections-to-9-1
> According to the thread, driver was fixed, so you need 9.1 driver to handle
> this problem.
>
>
> 2012/2/15 Ned Wolpert <ned.wolpert@gmail.com>
>>
>> Folks-
>>
>>   We're in the process of upgrading our postgresql install from 8.3 to
>> 9.1.2. Our main application is using postgresql-8.3-606.jdbc3.jar against
>> the existing postgresql database. (Java jdk1.6.0_29, Oracle's version, not
>> OpenJDK.  Its in use by hibernate. (Other Java applications use the database
>> too, but mostly via hibernate or rbatis)
>>
>>   My questions are:
>> 1) is it necessary to upgrade the jdbc jar file to the 9.1 version, or is
>> the 8.3 version 'upwards' compatible? If it is, can someone point out me to
>> what I would fail in apps that did not upgrade?
>> 2) Even though we are not using features from the JDBC4 version, should we
>> still use the JDBC4 variant due to the 1.6 JDK version?
>> 3) Is there any potential issues if an application is using the latest 9.1
>> JDBC driver against postgresql 8.3.x database?
>>
>> Obviously, we're hoping not to require an updated jar file, and just delay
>> the upgrade until the next application release. But I need to know if
>> upgrading the JDBC driver with the database upgrade cannot be avoided.
>>
>> Thanks
>>
>> --
>> Virtually, Ned Wolpert
>> http://codehead.tumblr.com/
>> http://codeheadsystems.wordpress.com/
>>
>> "Settle thy studies, Faustus, and begin..."   --Marlowe
>
>
>
>
> --
> Best regards,
>  Vitalii Tymchyshyn

Ned,

If you can make a connection then you should be fine, other than the
meta data issues

Dave Cramer

dave.cramer(at)credativ(dot)ca
http://www.credativ.ca



2012/2/16 Ned Wolpert <ned.wolpert@gmail.com>:
> So, the driver issue was only in dealing with UNICODE issues? Is it true
> that if we are always set with UNICODE client_encoding we should be fine?
> (Or, another way to put it, we have already tested connection from the
> existing java apps using the 8.3 driver to the new 9.1 database test
> instance, and they worked 'just fine' for initial queries... is that where
> this problem would manifest itself? Only in connecting?) Or was there
> something else I missed in that thread?
>
>
> 2012/2/15 Dave Cramer <pg@fastcrypt.com>
>>
>> My memory seems to be failing, yes, you will probably need a newer driver.
>> Dave Cramer
>>
>> dave.cramer(at)credativ(dot)ca
>> http://www.credativ.ca
>>
>>
>>
>> 2012/2/15 Віталій Тимчишин <tivv00@gmail.com>:
>> > I do remember some problems discussed with 9.1. AFAIR here it
>> >
>> > is: http://grokbase.com/t/postgresql/pgsql-hackers/114jz3zdpb/jdbc-connections-to-9-1
>> > According to the thread, driver was fixed, so you need 9.1 driver to
>> > handle
>> > this problem.
>> >
>> >
>> > 2012/2/15 Ned Wolpert <ned.wolpert@gmail.com>
>> >>
>> >> Folks-
>> >>
>> >>   We're in the process of upgrading our postgresql install from 8.3 to
>> >> 9.1.2. Our main application is using postgresql-8.3-606.jdbc3.jar
>> >> against
>> >> the existing postgresql database. (Java jdk1.6.0_29, Oracle's version,
>> >> not
>> >> OpenJDK.  Its in use by hibernate. (Other Java applications use the
>> >> database
>> >> too, but mostly via hibernate or rbatis)
>> >>
>> >>   My questions are:
>> >> 1) is it necessary to upgrade the jdbc jar file to the 9.1 version, or
>> >> is
>> >> the 8.3 version 'upwards' compatible? If it is, can someone point out
>> >> me to
>> >> what I would fail in apps that did not upgrade?
>> >> 2) Even though we are not using features from the JDBC4 version, should
>> >> we
>> >> still use the JDBC4 variant due to the 1.6 JDK version?
>> >> 3) Is there any potential issues if an application is using the latest
>> >> 9.1
>> >> JDBC driver against postgresql 8.3.x database?
>> >>
>> >> Obviously, we're hoping not to require an updated jar file, and just
>> >> delay
>> >> the upgrade until the next application release. But I need to know if
>> >> upgrading the JDBC driver with the database upgrade cannot be avoided.
>> >>
>> >> Thanks
>> >>
>> >> --
>> >> Virtually, Ned Wolpert
>> >> http://codehead.tumblr.com/
>> >> http://codeheadsystems.wordpress.com/
>> >>
>> >> "Settle thy studies, Faustus, and begin..."   --Marlowe
>> >
>> >
>> >
>> >
>> > --
>> > Best regards,
>> >  Vitalii Tymchyshyn
>
>
>
>
> --
> Virtually, Ned Wolpert
> http://codehead.tumblr.com/
> http://codeheadsystems.wordpress.com/
>
> "Settle thy studies, Faustus, and begin..."   --Marlowe

On Thu, 16 Feb 2012, Ned Wolpert wrote:

> So, the driver issue was only in dealing with UNICODE issues? Is it true
> that if we are always set with UNICODE client_encoding we should be fine?
> (Or, another way to put it, we have already tested connection from the
> existing java apps using the 8.3 driver to the new 9.1 database test
> instance, and they worked 'just fine' for initial queries... is that where
> this problem would manifest itself? Only in connecting?) Or was there
> something else I missed in that thread?

The end result of that thread was that the server folks ended up fixing
the server to allow older JDBC clients to connect, so that was only an
issue in the development version of the server for a short period of
time, never in a released version.

The big backwards compatibility change that occurred between 8.3 and 9.1
servers was the bytea escaping option.  If you want to use an older driver
you must set the bytea_output config option to escape on the server.

http://www.postgresql.org/docs/9.1/static/runtime-config-client.html#GUC-BYTEA-OUTPUT

Kris Jurka