Received: from megazone.bigpanda.com (megazone.bigpanda.com [63.150.15.178]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fBSNfLm31603 for ; Fri, 28 Dec 2001 18:41:21 -0500 (EST) (envelope-from sszabo@megazone23.bigpanda.com) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id 0F979D5F4; Fri, 28 Dec 2001 15:41:18 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id 013FC5BF1; Fri, 28 Dec 2001 15:41:17 -0800 (PST) Date: Fri, 28 Dec 2001 15:41:17 -0800 (PST) From: Stephan Szabo To: Linh Luong Cc: Subject: Re: Begin/Commit In-Reply-To: <20011228222730.555C0197395@jamie.edmonton.computalog.com> Message-ID: <20011228154024.H62612-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200112/255 X-Sequence-Number: 6077 On Fri, 28 Dec 2001, Linh Luong wrote: > Hi, > > I was wondering is there a limitation in the number of sql stmt that can go > between a begin and commit. > > I have a very large file that contains many updates and inserts (I mean > many). And it is taking too long to restore the data. Pg_restore is out of > the questions at the current moment because of the data version. > > Example, > Begin Work; > .... > ... > .. (1000 update/inserts sql smts) > Commit Work; > > Is this allowed???? Yes, in general that should be fine (excepting that any failed statement will force a rollback which affects all of the statements in the transaction)