Received: from megazone.bigpanda.com (megazone.bigpanda.com [63.150.15.178]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fBE6gLm35742 for ; Fri, 14 Dec 2001 01:42:21 -0500 (EST) (envelope-from sszabo@megazone23.bigpanda.com) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id EB8CFD5F4; Thu, 13 Dec 2001 22:42:20 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id E13315BF0; Thu, 13 Dec 2001 22:42:20 -0800 (PST) Date: Thu, 13 Dec 2001 22:42:20 -0800 (PST) From: Stephan Szabo To: MindTerm Cc: Subject: Re: performance tuning in large function / transaction In-Reply-To: <20011214033428.93468.qmail@web20203.mail.yahoo.com> Message-ID: <20011213224101.U8121-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200112/139 X-Sequence-Number: 5962 On Thu, 13 Dec 2001, MindTerm wrote: > Hi all, > > I will try to assign more memory to shared memory, > say 50M ~ 100M . > > I am runing something like that .. > > cursor loop 1 > cursor loop 2 > cursor loop 3 > tmp = primary key > delete tmp .... > insert tmp .... > end loop 3 > end loop 2 > end loop 3 > > will delete and insert record with same primary key > within a transaction reduce the performance ? Hmm, that might, is the tmp different for each combination of 1,2 and 3? I'm not really sure. You might also want to watch the backend's memory usage during the call to see how big it gets just to make sure there's not something bad happening.