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 A77AED1B4F2 for ; Thu, 23 Oct 2003 13:27:23 +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 47150-08 for ; Thu, 23 Oct 2003 10:26:56 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 9DB68D1B527 for ; Thu, 23 Oct 2003 10:26:52 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id h9NDQuit029124; Thu, 23 Oct 2003 09:26:56 -0400 (EDT) To: Mario Weilguni Cc: pgsql-performance@postgresql.org Subject: Re: vacuum locking In-reply-to: <200310230814.56738.mweilguni@sime.com> References: <16272.318.870000.93584@gargle.gargle.HOWL> <16279.4988.496000.539525@gargle.gargle.HOWL> <200310230814.56738.mweilguni@sime.com> Comments: In-reply-to Mario Weilguni message dated "Thu, 23 Oct 2003 08:14:56 +0200" Date: Thu, 23 Oct 2003 09:26:55 -0400 Message-ID: <29123.1066915615@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/600 X-Sequence-Number: 4348 Mario Weilguni writes: > I think oracle does not do garbage collect, it overwrites the tuples directly > and stores the old tuples in undo buffers. Since most transactions are > commits, this is a big win. ... 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. regards, tom lane