X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 5C2EF528F3 for ; Fri, 17 Jun 2005 02:07:27 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 06188-02 for ; Fri, 17 Jun 2005 05:07:20 +0000 (GMT) Received: from tht.net (vista.tht.net [216.126.88.2]) by svr1.postgresql.org (Postfix) with ESMTP id E11B95281E for ; Fri, 17 Jun 2005 02:07:19 -0300 (ADT) Received: from 216-154-15-201.dsl.look.ca (216-154-15-201.dsl.look.ca [216.154.15.201]) by tht.net (Postfix) with ESMTP id 1150276A19; Fri, 17 Jun 2005 01:07:26 -0400 (EDT) Subject: Re: How does the transaction buffer work? From: Rod Taylor To: Tom Lane Cc: pgsql-performance@postgresql.org, Veikko =?ISO-8859-1?Q?M=E4kinen?= In-Reply-To: <15555.1118981289@sss.pgh.pa.us> References: <42B1D2DE.4020709@ecom.fi> <15555.1118981289@sss.pgh.pa.us> Content-Type: text/plain Date: Fri, 17 Jun 2005 01:05:15 -0400 Message-Id: <1118984715.78366.240.camel@home> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.014 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200506/348 X-Sequence-Number: 12985 > Now of course this isn't Nirvana, you must pay somewhere ;-) and our > weak spot is the need for VACUUM. But you have no need to fear large > individual transactions. No need to fear long running transactions other than their ability to stop VACUUM from doing what it's supposed to be doing, thus possibly impacting performance. --