Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 2C1439FB6F9 for ; Thu, 12 Jul 2007 16:46:04 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 32099-01 for ; Thu, 12 Jul 2007 16:44:46 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.238]) by postgresql.org (Postfix) with ESMTP id EFAE39FB720 for ; Thu, 12 Jul 2007 16:44:51 -0300 (ADT) Received: by wx-out-0506.google.com with SMTP id h29so242071wxd for ; Thu, 12 Jul 2007 12:44:47 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JV4u/hv680QHlBZjol9fOG5E6nJeUCKuOaSpA37CC4/jy0/kE8tCvrQaeFlx28MlrdIrb5+HGEQDc6p3pO1GMqP4PLMiYXZePecXPLYPV7vwIJB1NTymcqG56OoxYOyirEtLn8m22m7EIpfwP0rf8ZUYj0OUgjcFW6ZWkYIl0iU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GoOLjqRMNEPf2wptC9OuIzmpV4rad0RqFq8IcKj5hypBUtFh7asSeDgUAolgDsGoyQ5szNJIkNeFHAbxoO959HEwzTsknLGXrA5gvuvdl2a2ZZBdk0vNYh5OXwy6O4Qq0pQB6BMhSZvRAITXTJFK71U4EwTqI5I2wVBZWycgUhw= Received: by 10.90.49.1 with SMTP id w1mr947165agw.1184269486560; Thu, 12 Jul 2007 12:44:46 -0700 (PDT) Received: by 10.90.106.16 with HTTP; Thu, 12 Jul 2007 12:44:46 -0700 (PDT) Message-ID: <33cb339b0707121244r73251341u7e5718fbbba448d9@mail.gmail.com> Date: Thu, 12 Jul 2007 12:44:46 -0700 From: "Ned Wolpert" To: pgsql-admin@postgresql.org Subject: Re: Anyone seen this message? In-Reply-To: <20070712191856.GK13778@alvh.no-ip.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <0F9A4731-717A-4F53-B758-1474EA4EF419@indiana.edu> <20070712191856.GK13778@alvh.no-ip.org> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/125 X-Sequence-Number: 26106 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 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