X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 965ED3A3B5E for ; Tue, 2 Nov 2004 12:36:52 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 27464-07 for ; Tue, 2 Nov 2004 12:36:44 +0000 (GMT) Received: from frog.mt.lv (frog.mt.lv [159.148.172.197]) by svr1.postgresql.org (Postfix) with ESMTP id 2DA073A3AD6 for ; Tue, 2 Nov 2004 12:36:42 +0000 (GMT) Received: from [10.5.8.106] (edgars@[10.5.8.106]) by frog.mt.lv (8.12.11/8.12.11/Debian-3) with ESMTP id iA2CXWpU012727; Tue, 2 Nov 2004 14:34:07 +0200 Message-ID: <41877E56.4060504@inbox.lv> Date: Tue, 02 Nov 2004 14:32:22 +0200 From: Edgars User-Agent: Mozilla Thunderbird 0.7.1 (X11/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jaime Casanova , pgsql-admin@postgresql.org Subject: Re: postgres gets slower after some while References: <20041101153706.72523.qmail@web50001.mail.yahoo.com> In-Reply-To: <20041101153706.72523.qmail@web50001.mail.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-mikrotik.com-Virus_kerajs: Not scanned. X-mikrotik.com-Virus_un_spam-kerajs: X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.9 tagged_above=0.0 required=5.0 tests=FROM_ENDS_IN_NUMS, MAILTO_TO_SPAM_ADDR X-Spam-Level: * X-Archive-Number: 200411/20 X-Sequence-Number: 15405 Jaime, thanks for the response! yes, i have tried this VACUMM, it gives some effect but only for some time (2hours or so). Maybe you know why it is happening so? Edgars Jaime Casanova wrote: > --- Edgars escribió: > > >>Hey, >> >>make some futher testings regarding my previous post >>(subj) and >>discovered that even on v7.4.2 is the same problem, >>it means the problem >>is somewhere in the configuration. On another box >>this works ok. >>The only way how i'm solving it for now is by >>dumping the whole >>structure and data from DB, dropping it and creating >>again. Then >>everything works for some time (till one day). >> >> >> > >Are you running VACUUM periodically on the database? > >It has a similar effect (it's not the same thing) that >when you drop and recreate the database. > >Here is an explanation why VACUUM is necessary: >http://www.postgresql.org/docs/7.4/interactive/maintenance.html > >Here you can find some other performance-tips: >http://www.postgresql.org/docs/7.4/interactive/performance-tips.html > >regards, >Jaime Casanova > > > >_________________________________________________________ >Do You Yahoo!? >Información de Estados Unidos y América Latina, en Yahoo! Noticias. >Visítanos en http://noticias.espanol.yahoo.com > >---------------------------(end of broadcast)--------------------------- >TIP 8: explain analyze is your friend > > > >