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 6AB1BD1B511 for ; Fri, 24 Oct 2003 06:18:09 +0000 (GMT) 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 25495-06 for ; Fri, 24 Oct 2003 03:17:39 -0300 (ADT) Received: from relay.icomedias.com (relay.icomedias.com [62.99.232.66]) by svr1.postgresql.org (Postfix) with ESMTP id 77FE4D1B517 for ; Fri, 24 Oct 2003 03:17:31 -0300 (ADT) Received: from loki.icomedias.com ([10.192.17.128]) by relay.icomedias.com (8.12.10/8.12.10) with ESMTP id h9O6HO5A020337 for ; Fri, 24 Oct 2003 08:17:24 +0200 From: Mario Weilguni To: pgsql-performance@postgresql.org Subject: Re: vacuum locking Date: Fri, 24 Oct 2003 08:17:22 +0200 User-Agent: KMail/1.5.4 References: <16272.318.870000.93584@gargle.gargle.HOWL> <200310230814.56738.mweilguni@sime.com> <29123.1066915615@sss.pgh.pa.us> In-Reply-To: <29123.1066915615@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200310240817.22586.mweilguni@sime.com> X-Scanned-By: MIMEDefang 2.33 (www . roaringpenguin . com / mimedefang) X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/611 X-Sequence-Number: 4359 Am Donnerstag, 23. Oktober 2003 15:26 schrieb Tom Lane: > ... if all tuples are the same size, and if you never have any > transactions that touch enough tuples to overflow your undo segment > (or even just sit there for a long time, preventing you from recycling > undo-log space; this is the dual of the VACUUM-can't-reclaim-dead-tuple > problem). And a few other problems that any Oracle DBA can tell you about. > I prefer our system. of course both approaches have advantages, it simply depends on the usage pattern. A case where oracle really rules over postgresql are m<-->n connection tables where each record consist of two foreign keys, the overwrite approach is a big win here.