Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 2AC639FB70C for ; Wed, 28 Feb 2007 17:26:33 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 41742-01 for ; Wed, 28 Feb 2007 17:26:09 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by postgresql.org (Postfix) with ESMTP id 4FA929FB683 for ; Wed, 28 Feb 2007 17:26:29 -0400 (AST) Received: from [207.253.108.123] by VL-MO-MR004.ip.videotron.ca (Sun Java System Messaging Server 6.2-2.05 (built Apr 28 2005)) with ESMTP id <0JE600HAXZK28S80@VL-MO-MR004.ip.videotron.ca> for pgsql-performance@postgresql.org; Wed, 28 Feb 2007 16:26:28 -0500 (EST) Date: Wed, 28 Feb 2007 16:33:23 -0500 From: Carlos Moreno Subject: Re: Upgraded to 8.2.3 --- still having performance issues In-reply-to: <45E5EBCC.7090206@mochima.com> Cc: PostgreSQL Performance Message-id: <45E5F523.1020306@mochima.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en References: <45E5B7D2.5020306@mochima.com> <5279.1172683250@sss.pgh.pa.us> <45E5D9D7.5090608@mochima.com> <45E5E419.5050804@gmail.com> <45E5EBCC.7090206@mochima.com> User-Agent: Mozilla Thunderbird 1.0.8-1.1.fc4 (X11/20060501) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.591 tagged_above=0 required=5 tests=AWL, BAYES_50, RCVD_IN_NJABL_PROXY, RCVD_IN_SORBS_WEB, SPF_HELO_PASS X-Spam-Level: * X-Archive-Number: 200702/348 X-Sequence-Number: 23402 Are there any issues with client libraries version mismatching backend version? I'm just realizing that the client software is still running on the same machine (not the same machine where PG is running) that has PG 7.4 installed on it, and so it is using the client libraries 7.4 Any chance that this may be causing trouble on the performance side? (I had been monitoring the logs to watch for SQLs now failing when they worked before... But I was thinking rather incompatibilities on the backend side ... ) Thanks, Carlos --