X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 0865CD1B44A for ; Tue, 13 Jan 2004 03:08:00 +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 27894-06 for ; Mon, 12 Jan 2004 23:07:32 -0400 (AST) Received: from mail2000-4.so-net.net.tw (mail2000-4.so-net.net.tw [61.64.127.20]) by svr1.postgresql.org (Postfix) with SMTP id 86419D1B52F for ; Mon, 12 Jan 2004 23:07:27 -0400 (AST) Received: from 10.1.9.27 by mail2000-4.so-net.net.tw with Mail2000 ESMTP Server V2.71S(79708:0:AUTH_RELAY) Tue, 13 Jan 2004 11:07:28 +0800 (CST); (envelope-from ) Received: By OpenMail Mailer;Tue, 13 Jan 2004 11:07:24 +0800 (CST) From: "cnliou" Reply-To: cnliou@so-net.net.tw Subject: Ignore Some Updates Message-ID: <1073963244.78843.cnliou@so-net.net.tw> To: "" Date: Tue, 13 Jan 2004 11:07:24 +0800 (CST) MIME-Version: 1.0 Content-Type: text/plain X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/127 X-Sequence-Number: 5302 Dear developers, I wonder it happens to systems where inefficient update SQL's are used like this: UPDATE MyTable SET MyColumn=1234 Question arises when the value of MyColumn is already 1234 before the update. If I am right, even when the to-be-updated column values equal to the new values, the core never hates to update that row anyway. If so, is it wise or not to adjust the core for lazy SQL users to ignore such "meaningless" updates in order to reduce some disk load and prevent some "holes" resulted from the delete (a consequence of update) in that table? Regards, CN