On Mon, Jan 17, 2011 at 09:05:40AM +0100, Federico Di Gregorio wrote:
> On 17/01/2011 07:59, Devrim GÜNDÜZ wrote:
> > As of PostgreSQL 9.0+, PostgreSQL RPMs can be installed in parallel,
> > e.g., you can use 9.0 along with 9.1. I updated most of the packages to
> > use that layout, but I'm stuck with psycopg2.
> >
> > psycopg2 is currently installed under this directory:
> >
> > `python -c "from distutils.sysconfig import get_python_lib; print
> > get_python_lib(1)"`/psycopg2
> >
> > For example,
> >
> > /usr/lib64/python2.7/site-packages/psycopg2/
> >
> > If I want to install two different psycopg2 versions which are compiled
> > against 9.0 and 9.1, they will overwrite each other.
> >
> > What is the best way to use separate directories for that? Is there a
> > setup.py parameter for that?
>
> You don't need that, because psycopg uses libpq that can connect to
> older versions of the backend.
>
> I don't know about RPMs but in Debian we have multiple versions of
> postgresql and only *one* libpqXX package (usually it comes from the
> most recent stable release). So my suggestion is to have only one
> version of psycopg linked to the most recent libpq package.
This is not really the final solution.
I've got a Debian/Squeeze machine which runs PG 9.0 from /Unstable.
I've got a second Debian/Squeeze machine running PG 8.4 from /Squeeze.
Both use the same psycopg2 from /Squeeze.
Transferring bytea data from the 9.0 machine to the 8.4 one
does not work (other datatypes work fine).
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346