Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 30F6C475EE2 for ; Tue, 14 Jan 2003 05:50:54 -0500 (EST) Received: from serwer.skawsoft.com.pl (serwer.skawsoft.com.pl [213.25.37.66]) by postgresql.org (Postfix) with ESMTP id 625A6475DBC for ; Tue, 14 Jan 2003 05:50:53 -0500 (EST) Received: from klaster.net (pc43.krakow.cvx.ppp.tpnet.pl [213.76.38.43]) by serwer.skawsoft.com.pl (Postfix) with ESMTP id 3A0062B267 for ; Tue, 14 Jan 2003 11:48:02 +0100 (CET) Message-ID: <3E23EC83.9060802@klaster.net> Date: Tue, 14 Jan 2003 11:54:59 +0100 From: Tomasz Myrta User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.2b) Gecko/20021016 X-Accept-Language: en-us, en MIME-Version: 1.0 To: PgSQL Performance ML Subject: complicated queries in pl/pgsql Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/82 X-Sequence-Number: 729 Hi Sometimes my pl/pgsql functions have pretty complicated queries inside - most of their execution time takes postgresql query planning. I was wondering if I should change these queries into views? Does it speed up function execution? Pl/pgsql saves execution plan for connection lifetime. What happens to view planning - is it performed during view creation, or rather each time view is quered? Regards, Tomasz Myrta