Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 5CBDF476D2E for ; Wed, 15 Jan 2003 16:21:18 -0500 (EST) Received: from davinci.ethosmedia.com (unknown [209.10.40.251]) by postgresql.org (Postfix) with ESMTP id D50AB476E7C for ; Wed, 15 Jan 2003 15:34:11 -0500 (EST) Received: from [66.219.92.2] (HELO chocolate-mousse) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 2315206; Wed, 15 Jan 2003 12:34:15 -0800 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Tomasz Myrta Subject: Re: complicated queries in pl/pgsql Date: Tue, 14 Jan 2003 12:36:15 -0800 X-Mailer: KMail [version 1.4] Cc: PgSQL Performance ML References: <3E23EC83.9060802@klaster.net> <200301131044.50424.josh@agliodbs.com> <3E25B29C.9040408@klaster.net> In-Reply-To: <3E25B29C.9040408@klaster.net> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200301141236.15915.josh@agliodbs.com> X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/124 X-Sequence-Number: 771 Tomasz, > Thanks a lot. > I'm asking, because I use some queries which are easy to change into=20 > views. Most of their execution time takes planning, they use 5-10=20 > explicit table joins with not too many rows in these tables and returns= =20 > few values. You might want to investigate the new "prepared query" functionality in 7.3= .1. I haven't used it yet, so I can't help much. --=20 -Josh Berkus Aglio Database Solutions San Francisco