Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 8BCA09FB350 for ; Tue, 7 Aug 2007 11:07:17 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 14297-02-2 for ; Tue, 7 Aug 2007 11:07:03 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.187]) by postgresql.org (Postfix) with ESMTP id AA88E9FB972 for ; Tue, 7 Aug 2007 11:07:11 -0300 (ADT) Received: by rv-out-0910.google.com with SMTP id f1so1179080rvb for ; Tue, 07 Aug 2007 07:07:09 -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:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=mMV4/XKXxqb4uxOeDUUnmVMQlWBX/o7w2RgewcBeGEP+8IxdbLJRgB6OysCSJWNieX8sxDbq1/UZWWClEMkpFnmMxG27mBjGOqQIVt/ZqRG1yd8Qo9p5rIwLRipayj3k+ONsb6m/PK0eyBvy++dFuazEi56OhXdHKv05+A2v6bo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=rtemLyiSb4h/Wrad8i9ymJXGojo6K2AYTkCNXtH7e7bSAt6ODSqBkwfPxKTOPuMIXa0vysqc2uR0IJ9OQok3/zxOBGBogepWJOgaosYly1JRT5ZD8vRPHzTQnN+7RTZya+SsoLFeipPR6SL92Hb6pqgDnUklr/NcNldi8YUfuyQ= Received: by 10.141.85.13 with SMTP id n13mr2155583rvl.1186495629732; Tue, 07 Aug 2007 07:07:09 -0700 (PDT) Received: by 10.141.162.12 with HTTP; Tue, 7 Aug 2007 07:07:09 -0700 (PDT) Message-ID: Date: Tue, 7 Aug 2007 09:07:09 -0500 From: "Scott Marlowe" To: "Sven Clement" Subject: Re: Performance problems with large telemetric datasets on 7.4.2 Cc: "Heikki Linnakangas" , "Tom Lane" , "Andrew Kroeger" , "Mark Lewis" , pgsql-performance@postgresql.org In-Reply-To: <881035ea0708060254w32fa164di32d3579c2b0ebf14@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <881035ea0708030652r37b25a86g61e88e1f5e95eab2@mail.gmail.com> <1186150836.19184.194.camel@archimedes> <881035ea0708030857s621af020r4d3d7b994e2ca9a3@mail.gmail.com> <46B39A77.8050105@sprocks.gotdns.com> <4770.1186180449@sss.pgh.pa.us> <881035ea0708041303h4ea256b3q4b40c5291f8cd3b7@mail.gmail.com> <46B5F5C7.1070901@enterprisedb.com> <881035ea0708060010u1bbb4b58r57bdf6f51b12f7d9@mail.gmail.com> <46B6EF0D.6030501@enterprisedb.com> <881035ea0708060254w32fa164di32d3579c2b0ebf14@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/57 X-Sequence-Number: 26187 On 8/6/07, Sven Clement wrote: > Ok thanks everybody for the calrification, after all now I allready learned > something new... ;) > > My employer is currently thinking about migration to 8.2.x because of your > feedback, so I think that the problem could be resolved... ;) Note that whether the 8.2 migration is forthcoming, you should definitely update to the latest patch version of 7.4. The update is pretty much painless, although I remember there being a change around 7.4.13 that might have changed db behaviour for security reasons. Release notes here: http://www.postgresql.org/docs/8.2/static/release-7-4-13.html Note that there are settings to work around the change in behaviour should it create a problem.