Re: [HACKERS] Mixing library versions

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: meskes(at)usa(dot)net (Michael Meskes)
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Mixing library versions
Date: 1998-11-04 14:04:31
Message-ID: 199811041404.JAA09674@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Wed, Nov 04, 1998 at 12:09:21AM +0000, Oliver Elphick wrote:
> > I'm currently experimenting with the Debian packaging of 6.4.
> >
> > The question arises of how to handle the change in library versions from
> > 1.0 to 2.0. It has been suggested that I should keep libpq.so.1 around
> > for the benefit of those who need to communicate with an older database
> > server.
> >
> > Is it possible to use libpq.so.2.0 to query a remote database whose
> > server is running PostgreSQL 6.3? What would be the consequences of
>
> No. Let's just try /usr/local/pgsql/bin/psql(6.4) on my running 6.3 server:
>
> Connection to database 'mm' failed.
> Unsupported frontend protocol.
>
> > using libpq.so.1 to query a 6.4 server?
>
> Never tried that until now. But it appears to work. I hvae no idea though
> where it could break things.

2.0 and 1.0 libpq can connect to 6.4, but 2.0 libpq can not connect to
older databases. In other words, the backend can communicate with old
libpq, but old backends can not communicate with 2.0 libpq.

--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message A James Lewis 1998-11-04 14:57:52 Re: [HACKERS] Warning!!
Previous Message Lyn K. Finman 1998-11-04 14:03:50 cache lookup failed