X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id D15309F9CAA for ; Tue, 13 Jun 2006 05:17:26 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 41865-10 for ; Tue, 13 Jun 2006 05:17:22 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.rentalia.net (mail.rentalia.com [213.192.209.8]) by postgresql.org (Postfix) with ESMTP id 1CB7F9F9316 for ; Tue, 13 Jun 2006 05:17:21 -0300 (ADT) Received: (qmail 26176 invoked by uid 514); 13 Jun 2006 10:17:19 +0200 Received: from 62.37.216.115 by rigodon (envelope-from , uid 512) with qmail-scanner-1.25-st-qms (clamdscan: 0.88/1284. spamassassin: 3.0.2. perlscan: 1.25-st-qms. Clear:RC:0(62.37.216.115):SA:0(-2.2/5.0):. Processed in 4.822127 secs); 13 Jun 2006 08:17:19 -0000 X-Antivirus-MYDOMAIN-Mail-From: ruben@rentalia.com via rigodon X-Antivirus-MYDOMAIN: 1.25-st-qms (Clear:RC:0(62.37.216.115):SA:0(-2.2/5.0):. Processed in 4.822127 secs Process 26083) Received: from 62-37-216-115.mad1.adsl.uni2.es (HELO ?192.168.2.28?) (ruben@rentalia.com@62.37.216.115) by mail.rentalia.net with SMTP; 13 Jun 2006 10:17:14 +0200 Message-ID: <448E7484.2020100@rentalia.com> Date: Tue, 13 Jun 2006 10:17:08 +0200 From: Ruben Rubio Rey User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060503) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Guido Neitzer CC: pgsql-performance@postgresql.org Subject: Re: Posrgres speed problem - solved? References: <448D7C81.1000108@rentalia.com> <448D8940.4050209@aeccom.com> <448E5ECF.5090100@rentalia.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/169 X-Sequence-Number: 19526 Guido Neitzer wrote: > On 13.06.2006, at 8:44 Uhr, Ruben Rubio Rey wrote: > >> Tonight database has been vacumm full and reindex (all nights >> database do it) >> >> Now its working fine. Speed is as spected. I ll be watching that sql >> ... >> Maybe the problem exists when database is busy, or maybe its solved ... > > > Depending on the usage pattern the nightly re-index / vacuum analyse > is suboptimal. If you have high insert/update traffic your > performance will decrease over the day and will only be good in the > morning hours and I hope this is not what you intend to have. > > Autovacuum is the way to go, if you have "changing content". Perhaps > combined with vacuum analyse in a nightly or weekly schedule. We do > this weekly. > > cug > > I ll configure autovacum. I ll write if problem is solved.