Skip site navigation (1) Skip section navigation (2)

Re: Upgrade question, going from 8.3 to 9.1...

From: Kris Jurka <books(at)ejurka(dot)com>
To: Ned Wolpert <ned(dot)wolpert(at)gmail(dot)com>
Cc: Dave Cramer <pg(at)fastcrypt(dot)com>, Віталій Тимчишин <tivv00(at)gmail(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Upgrade question, going from 8.3 to 9.1...
Date: 2012-02-16 21:06:21
Message-ID: alpine.BSO.2.00.1202161602090.32496@leary.csoft.net (view raw or flat)
Thread:
Lists: pgsql-jdbc

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


In response to

Responses

pgsql-jdbc by date

Next:From: Ned WolpertDate: 2012-02-16 21:58:13
Subject: Re: Upgrade question, going from 8.3 to 9.1...
Previous:From: Dave CramerDate: 2012-02-16 21:04:31
Subject: Re: Upgrade question, going from 8.3 to 9.1...

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group