Received: from megazone.bigpanda.com (megazone.bigpanda.com [63.150.15.178]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fBH3fHm56457 for ; Sun, 16 Dec 2001 22:41:17 -0500 (EST) (envelope-from sszabo@megazone23.bigpanda.com) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id D5A99D5E8; Sun, 16 Dec 2001 19:41:21 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id CB4EF5BF1; Sun, 16 Dec 2001 19:41:21 -0800 (PST) Date: Sun, 16 Dec 2001 19:41:21 -0800 (PST) From: Stephan Szabo To: MindTerm Cc: Subject: Re: performance tuning in large function / transaction In-Reply-To: <20011217025856.23363.qmail@web20204.mail.yahoo.com> Message-ID: <20011216194044.L46323-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200112/171 X-Sequence-Number: 5994 > --- Stephan Szabo > wrote: > > > > On Fri, 14 Dec 2001, MindTerm wrote: > > > > > Hi all, > > > > > > table : > > > application : 220 rows ; > > > usermenu : 6055 rows ; > > > > Well, I'd need the other tables involved in the > > function > > too, but to start with, try rewriting the queries in > > the > > function to use EXISTS rather than IN (see the faq), > > or > > bring them into a normal join with the other tables > > where > > possible. As a note, does rewriting the queries in the function to use exists rather than in help any?