Good point.
This is exactly my problem.
I tried to switch to the V2 protocol with the 8.0 JDBC driver. But in
this case, I have the same behavior than with the 7.4 driver working on
the 8.0 database.
To answer Richard Huxton : the problem of JDBC 7.4 driver with a 8.0
database is that autoc
Romain,
If you're using JDBC and the V3 protocol is hurting you (which was my
case at one point), you can force the 8.0 driver to use the V2 protocol
which does a lot of things differently. For a quick solution that could
work until you fix your code to properly work with V3.
Just shooting in the
Romain Vinot wrote:
Hi,
We've got a problem with postgres 8.0 (our own code is not ready yet for
the new driver) but a production database is already on postgres 8.0
(too bad, we didn't tested it enough...).
What "new driver"? I wasn't aware of 8.0 not being able to work with
drivers for 7.
Hi,
We've got a problem with postgres 8.0 (our own code is not ready yet for
the new driver) but a production database is already on postgres 8.0
(too bad, we didn't tested it enough...).
So we need to migrate back to postgres 7.4 and wait for a code upgrade.
Is there a possible way to do th
