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 201F0D1B55D for ; Tue, 13 Jan 2004 05:00:08 +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 44847-06 for ; Tue, 13 Jan 2004 00:59:36 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 192EDD1B494 for ; Tue, 13 Jan 2004 00:59:36 -0400 (AST) 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 i0D4xZ19008022; Mon, 12 Jan 2004 23:59:35 -0500 (EST) To: cnliou@so-net.net.tw Cc: "" Subject: Re: Ignore Some Updates In-reply-to: <1073963244.78843.cnliou@so-net.net.tw> References: <1073963244.78843.cnliou@so-net.net.tw> Comments: In-reply-to "cnliou" message dated "Tue, 13 Jan 2004 11:07:24 +0800" Date: Mon, 12 Jan 2004 23:59:35 -0500 Message-ID: <8021.1073969975@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/128 X-Sequence-Number: 5303 "cnliou" writes: > 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. We have to fire UPDATE triggers in any case. > 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 Seems like penalizing the intelligent people (by adding useless comparisons) in order to reward the "lazy" ones. regards, tom lane