From: | "Ned Wolpert" <ned(dot)wolpert(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Anyone seen this message? |
Date: | 2007-07-12 19:44:46 |
Message-ID: | 33cb339b0707121244r73251341u7e5718fbbba448d9@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Let me ask a further question for clarification on this point, just to
be sure... though I'm going to bet I know the answer... just want to
be sure.
In my current production environment, the PostgreSQL database server
is the latest, 8.2.4. The apps that communicate with it are planned
to be running on stock CentOS5 servers, with the default 8.1.x (8.1.9)
client libraries. So, not only is psql 8.1.9 (which I don't use on
that server) but the libpq.so is from the 8.1.9 install. Apache 2.2
package uses the DBDriver module from the apr-util that was installed
from CentOS, and we are planning to connect it to our PostgreSQL
server. Is that a 'bad thing' considering the libpq.so is a different
major version?
In the case of Java JDBC drivers, is this also a problem? (Using the
JDBC driver from the 8.1 release against the 8.2 server)
And thanks for clarification.
On 7/12/07, Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
>
> Don't use a mismatching psql version with the server version.
>
--
Virtually, Ned Wolpert
http://www.codeheadsystems.com/blog/
"Settle thy studies, Faustus, and begin..." --Marlowe
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-07-12 19:53:54 | Re: Anyone seen this message? |
Previous Message | Alvaro Herrera | 2007-07-12 19:18:56 | Re: Anyone seen this message? |