X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 26E23D1F0D7 for ; Mon, 10 May 2004 11:00:12 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 38544-08 for ; Mon, 10 May 2004 10:59:53 -0300 (ADT) Received: from ibague.terra.com.br (ibague.terra.com.br [200.154.55.225]) by svr1.postgresql.org (Postfix) with ESMTP id 23260D1E6A7 for ; Mon, 10 May 2004 10:59:49 -0300 (ADT) Received: from pasto.terra.com.br (pasto.terra.com.br [200.154.55.137]) by ibague.terra.com.br (Postfix) with ESMTP id CF49AEC161 for ; Mon, 10 May 2004 10:59:52 -0300 (BRT) Received: from suport01 (mlsrj200152101p142.mls.com.br [200.152.101.142]) (authenticated user teouique) by pasto.terra.com.br (Postfix) with ESMTP id 06A5F3C00A for ; Mon, 10 May 2004 10:59:51 -0300 (BRT) Message-ID: <00b901c43697$333ec5d0$5f00a8c0@suport01> From: "Anderson Boechat Lopes" To: Subject: Why queries takes too much time to execute? Date: Mon, 10 May 2004 11:00:43 -0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00B6_01C4367E.0A0A8FA0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.5 tagged_above=0.0 required=5.0 tests=HTML_40_50, HTML_MESSAGE X-Spam-Level: X-Archive-Number: 200405/56 X-Sequence-Number: 6887 This is a multi-part message in MIME format. ------=_NextPart_000_00B6_01C4367E.0A0A8FA0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi. I=B4m new here and i=B4m not sure if this is the right email to solve m= y problem. Well, i have a very large database, with vary tables and very registers= . Every day, too many operations are perfomed in that DB, with queries that= insert, delete and update. Once a week some statistics are collected using= vacuum analyze. =20=20=20=20 The problem is after a period of time (one month, i think), the queries= takes too much time to perform. A simple update can take 10 seconds or mor= e to perform. If i make a backup, drop and recreate the DB, everything goes back norm= al. Could anyone give me any guidance? ------=_NextPart_000_00B6_01C4367E.0A0A8FA0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Hi.
 
    I=B4m n= ew here and=20 i=B4m not sure if this is the right email to solve my problem.
 
    Well, i= have a=20 very large database, with vary tables and very registers. Every day, t= oo=20 many operations are perfomed in that DB, with queries that insert, delete a= nd=20 update. Once a week some statistics are collected using vacuum=20 analyze.
    =
    The pro= blem is=20 after a period of time (one month, i think), the queries takes too muc= h=20 time to perform. A simple update can take 10 seconds or more to=20 perform.
 
    If i ma= ke a=20 backup, drop and recreate the DB, everything goes back=20 normal.
 
    Could= =20 anyone give me any guidance?
------=_NextPart_000_00B6_01C4367E.0A0A8FA0--