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 dark...
Csaba.
On Mon, 2005-10-24 at 10:02, 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...).
>
> So we need to migrate back to postgres 7.4 and wait for a code upgrade.
> Is there a possible way to do this ?
>
> pg_dump output of 8.0 is not compatible with 7.4. But the output of
> "pg_dump -a" seems to be compatible.
> One solution would be to create tables with a 7.4 sql script. Then use
> pg_dump to get the data from the 8.0 database and fill them in the 7.4
> database. And finally restore all functions and triggers from a 7.4 sql
> script.
>
> Before testing this way, I would like your advise to know if our
> solution has a chance to work, if there is a better way or anything...
>
> Thanks for any help
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
