Received: from megazone.bigpanda.com (megazone.bigpanda.com [63.150.15.178]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fBH3eKm56421 for ; Sun, 16 Dec 2001 22:40:20 -0500 (EST) (envelope-from sszabo@megazone23.bigpanda.com) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id 07E43D5EF; Sun, 16 Dec 2001 19:40:24 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id EDB1A5BF1; Sun, 16 Dec 2001 19:40:24 -0800 (PST) Date: Sun, 16 Dec 2001 19:40:24 -0800 (PST) From: Stephan Szabo To: Marc Spitzer Cc: Subject: Re: persistent connections, AOLserver (Was: maybe Offtopic : In-Reply-To: Message-ID: <20011216193909.T46323-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200112/172 X-Sequence-Number: 5995 On Mon, 17 Dec 2001, Marc Spitzer wrote: > In article <20011203110458.E93680-100000@megazone23.bigpanda.com>, > Stephan Szabo wrote: > > On Fri, 30 Nov 2001, Steve Brett wrote: > > > >> is there a limit/guide to the number of inserts you should use in a > >> transaction block ? > > > > Not a hard one, but I usually do thousands of rows (around 5k) per > > transaction when I'm batch inserting, and I usually set it there so > > I can watch its progress from another db session as the counts rise. > > > > How do you set up the other session to watch? Usually I just set up something to do throw an occasional query to the server every so often (small script or something). Something like a select count(*) or select id order by id desc limit 1 type query.