X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 8D9BAD1C916 for ; Wed, 6 Aug 2003 10:14:26 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 02577-08 for ; Wed, 6 Aug 2003 07:13:07 -0300 (ADT) Received: from smtp.pspl.co.in (unknown [202.54.11.65]) by svr1.postgresql.org (Postfix) with ESMTP id 9BB39D1C7EB for ; Wed, 6 Aug 2003 07:14:14 -0300 (ADT) Received: (from root@localhost) by smtp.pspl.co.in (8.12.9/8.12.9) id h76AEkU0002102 for ; Wed, 6 Aug 2003 15:44:46 +0530 Received: from daithan (daithan.intranet.pspl.co.in [192.168.7.161]) (authenticated bits=0) by persistent.co.in (8.12.9/8.12.9) with ESMTP id h76AEjip002074 for ; Wed, 6 Aug 2003 15:44:45 +0530 From: "Shridhar Daithankar" To: pgsql-performance@postgresql.org Date: Wed, 06 Aug 2003 15:46:06 +0530 MIME-Version: 1.0 Subject: Re: How Many Inserts Per Transactions Reply-To: shridhar_daithankar@persistent.co.in Message-ID: <3F3122BE.10716.137B9C@localhost> In-reply-to: <60d6fkhxwl.fsf@dev6.int.libertyrms.info> X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/96 X-Sequence-Number: 2913 On 5 Aug 2003 at 12:28, Christopher Browne wrote: > On Oracle, I have seen performance Suck Badly when using SQL*Load; if > I grouped too many updates together, it started blowing up the > "rollback segment," which was a Bad Thing. And in that kind of > context, there will typically be some "sweet spot" where you want to > commit transactions before they grow too big. > > In contrast, pg_dump/pg_restore puts the load of each table into a > single COPY statement, so that if there are 15,000,000 entries in the > table, that gets grouped into a single (rather enormous) transaction. > And doing things that way presents no particular problem. Well, psotgresql recycles WAL files and use data files as well to store uncommitted transaction. Correct me if I am wrong. Oracle does not do this. What does this buy? Oracle has constant time commits. I doubt if postgresql has them with such a design. For what hassle that is worth, I would buy expand-on-disk as you go approach of postgresql rather than spending time designing rollback segments for each application. It's not nice when customer reports rollback segment overflow. Tablespaces over file is royal pain when it does not work. Just a thought.. Bye Shridhar -- boss, n: According to the Oxford English Dictionary, in the Middle Ages the words "boss" and "botch" were largely synonymous, except that boss, in addition to meaning "a supervisor of workers" also meant "an ornamental stud."