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 3F433D1B51E for ; Sat, 25 Oct 2003 00:08:26 +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 98621-03 for ; Fri, 24 Oct 2003 21:07:58 -0300 (ADT) Received: from smtp.istop.com (dci.doncaster.on.ca [66.11.168.194]) by svr1.postgresql.org (Postfix) with ESMTP id CF477D1B515 for ; Fri, 24 Oct 2003 21:07:54 -0300 (ADT) Received: from stark.dyndns.tv (gsstark.mtl.istop.com [66.11.160.162]) by smtp.istop.com (Postfix) with ESMTP id AA03E36B27; Fri, 24 Oct 2003 20:07:57 -0400 (EDT) Received: from localhost ([127.0.0.1] helo=stark.dyndns.tv ident=foobar) by stark.dyndns.tv with smtp (Exim 3.36 #1 (Debian)) id 1ADByH-0003je-00; Fri, 24 Oct 2003 20:07:57 -0400 To: Rob Nagler Cc: pgsql-performance@postgresql.org Subject: Re: vacuum locking References: <16272.318.870000.93584@gargle.gargle.HOWL> <200310230814.56738.mweilguni@sime.com> <29123.1066915615@sss.pgh.pa.us> <200310240817.22586.mweilguni@sime.com> <16281.41629.69000.492473@gargle.gargle.HOWL> In-Reply-To: <16281.41629.69000.492473@gargle.gargle.HOWL> From: Greg Stark Organization: The Emacs Conspiracy; member since 1992 Date: 24 Oct 2003 20:07:57 -0400 Message-ID: <87ekx2uqle.fsf@stark.dyndns.tv> Lines: 22 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/639 X-Sequence-Number: 4387 Rob Nagler writes: > Mario Weilguni writes: > > 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. I don't understand why you would expect overwriting to win here. What types of updates do you do on these tables? Normally I found using update on such a table was too awkward to contemplate so I just delete all the relation records that I'm replacing for the key I'm working with and insert new ones. This always works out to be cleaner code. In fact I usually leave such tables with no UPDATE grants on them. In that situation I would have actually expected Postgres to do as well as or better than Oracle since that makes them both functionally equivalent. -- greg