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 393FBD1B215 for ; Thu, 17 Jun 2004 10:58:13 -0300 (ADT) 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 15899-07 for ; Thu, 17 Jun 2004 13:58:08 +0000 (GMT) Received: from 200.152.196.42.cardsystem.com.br (unknown [200.152.196.42]) by svr1.postgresql.org (Postfix) with SMTP id A19E8D1B1B7 for ; Thu, 17 Jun 2004 10:58:02 -0300 (ADT) Received: from csusppro12.csu.com.br ([191.167.4.5]) by 200.152.196.42.cardsystem.com.br (SAVSMTP 3.1.0.29) with SMTP id M2004061710570219548 for ; Thu, 17 Jun 2004 10:57:02 -0300 Received: by csusppro12.csu.com.br with Internet Mail Service (5.5.2653.19) id ; Thu, 17 Jun 2004 10:59:54 -0300 Message-ID: <31A2FFCFAF95D51189790002A57568FA116E8EAB@csusppro12.csu.com.br> From: Alessandro Meneguelli Coutinho To: pgsql-admin@postgresql.org Subject: Performance 7.3.4 Date: Thu, 17 Jun 2004 10:59:52 -0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C45473.5CD8E20A" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.8 tagged_above=0.0 required=5.0 tests=HTML_30_40, HTML_MESSAGE X-Spam-Level: X-Archive-Number: 200406/220 X-Sequence-Number: 13880 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C45473.5CD8E20A Content-Type: text/plain; charset="iso-8859-1" We are trying to upgrade postgres 7.2 to postgres 7.3.4. We are having problems with some reports that have an excellent performance in 7.2 and now, in 7.3.4 the performance is too bad. Did someone have this problem? What should we do? ------_=_NextPart_001_01C45473.5CD8E20A Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Performance 7.3.4

  We are trying to upgrade postgres 7.2 to postgres = 7.3.4. We are having problems with some reports that have an excellent perf= ormance in 7.2 and now, in 7.3.4 the performance is too bad. Did someone ha= ve this problem? What should we do?


 

------_=_NextPart_001_01C45473.5CD8E20A--