X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 17F9ED1DF83 for ; Thu, 29 Apr 2004 21:45:21 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 54734-07 for ; Thu, 29 Apr 2004 21:45:02 -0300 (ADT) Received: from tht.net (vista.tht.net [216.126.88.2]) by svr1.postgresql.org (Postfix) with ESMTP id 59532D1B4E0 for ; Thu, 29 Apr 2004 21:44:58 -0300 (ADT) Received: from [134.22.68.249] (dyn-68-249.tor.dsl.tht.net [134.22.68.249]) by tht.net (Postfix) with ESMTP id DB30276A69; Thu, 29 Apr 2004 20:45:03 -0400 (EDT) Subject: Re: Insert only tables and vacuum performance From: Rod Taylor To: Joseph Shraibman Cc: Postgresql Performance In-Reply-To: References: Content-Type: text/plain Message-Id: <1083285855.30065.462.camel@jester> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Thu, 29 Apr 2004 20:44:16 -0400 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200404/516 X-Sequence-Number: 6816 > Or even better an offset into the datatable for the earliest deleted > row, so if you have a table where you update the row shortly after > insert and then never touch it vacuum can skip most of the table > (inserts are done at the end of the table, right?) Inserts are done at the end of the table as a last resort. But anyway, how do you handle a rolled back insert?