Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id EACA837BD1B for ; Thu, 2 Oct 2008 12:15:01 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 26667-07-2 for ; Thu, 2 Oct 2008 12:14:48 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from wayr.org (wayr.org [88.191.18.57]) by postgresql.org (Postfix) with ESMTP id 5515237C072 for ; Thu, 2 Oct 2008 12:14:36 -0300 (ADT) Received: by wayr.org (Postfix, from userid 1005) id A464F5AE5; Thu, 2 Oct 2008 17:14:35 +0200 (CEST) Received: from imp.wayr.org (localhost.localdomain [127.0.0.1]) by wayr.org (Postfix) with ESMTP id 7682D55E4; Thu, 2 Oct 2008 17:14:34 +0200 (CEST) MIME-Version: 1.0 Date: Thu, 2 Oct 2008 17:14:34 +0200 From: To: Tommy Gildseth Cc: Richard Huxton , pgsql-performance@postgresql.org Subject: Re: dedicated server & postgresql 8.1 conf tunning In-Reply-To: <48E48822.5060009@usit.uio.no> References: <48E48822.5060009@usit.uio.no> Message-ID: <1f85e3205b1395eaa2ac64a295a226ba@localhost> X-Sender: paul@wayr.org User-Agent: RoundCube Webmail/0.1-rc1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.1.3 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200810/18 X-Sequence-Number: 31599 I played with work_mem and setting work_mem more than 256000 do not change the performance. I try to upgrade to 8.3 using etch-backports but it's a new install not an upgrade. So i have to create users, permissions, import data again, it scared me so i want to find another solutions first. But now i'll try 8.3 On Thu, 02 Oct 2008 10:36:50 +0200, Tommy Gildseth wrote: > Richard Huxton wrote: >> paul@wayr.org wrote: >>> Thanks, >>> >>> Unfornatly, i can't update pgsql to 8.3 since it's not in debian > stable. >> >> That's why backports.org was invented :-) >> Or does can't mean "not allowed to"? > > > Well, running production servers from backports can be a risky > proposition too, and can land you in situations like the one discussed > in "Debian packages for Postgres 8.2" from the General list. > > > -- > Tommy Gildseth