X-Original-To: pgsql-performance@postgresql.org Received: from spampd.localdomain (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id B394F475AE5 for ; Sun, 27 Apr 2003 02:50:56 -0400 (EDT) Received: from fuji.krosing.net (unknown [194.204.44.118]) by postgresql.org (Postfix) with ESMTP id F25E2474E42 for ; Sun, 27 Apr 2003 02:50:54 -0400 (EDT) Received: from fuji.krosing.net (lo [127.0.0.1]) by fuji.krosing.net (8.12.8/8.12.8) with ESMTP id h3R6oqoJ001925; Sun, 27 Apr 2003 09:50:52 +0300 Received: (from hannu@localhost) by fuji.krosing.net (8.12.8/8.12.8/Submit) id h3R6opFt001922; Sun, 27 Apr 2003 09:50:51 +0300 X-Authentication-Warning: fuji.krosing.net: hannu set sender to hannu@tm.ee using -f Subject: Re: More tablescanning fun From: Hannu Krosing To: jim@nasby.net Cc: Tom Lane , pgsql-performance@postgresql.org In-Reply-To: <20030425115613.E66185@flake.decibel.org> References: <20030424183817.A66185@flake.decibel.org> <3660.1051228710@sss.pgh.pa.us> <20030424235924.B66185@flake.decibel.org> <1051288086.1765.95.camel@fuji.krosing.net> <20030425115613.E66185@flake.decibel.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1051426250.1860.1.camel@fuji.krosing.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 27 Apr 2003 09:50:51 +0300 X-Spam-Status: No, hits=-32.9 required=5.0 tests=BAYES_10,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_XIMIAN,X_AUTH_WARNING autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) X-Archive-Number: 200304/220 X-Sequence-Number: 1726 Jim C. Nasby kirjutas R, 25.04.2003 kell 19:56: > I'm not familiar enough with pgsql's guts to know how big an impact > updates across pages are, or if they even happen often at all. If you're > not maintaining a clustered table, couldn't all updates just occur > in-place? In postgres _no_ updates happen in-place. The MVCC concurrency works by always inserting a new tuple on update . ----------- Hannu