Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 90C2E9FB2CF for ; Sun, 15 Apr 2007 02:29:09 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 37733-01 for ; Sun, 15 Apr 2007 02:29:06 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 775359FB274 for ; Sun, 15 Apr 2007 02:29:06 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id l3F5T1W4026400; Sun, 15 Apr 2007 01:29:01 -0400 (EDT) To: cluster cc: pgsql-performance@postgresql.org Subject: Re: FK triggers misused? In-reply-to: References: Comments: In-reply-to cluster message dated "Sat, 14 Apr 2007 15:51:37 +0200" Date: Sun, 15 Apr 2007 01:29:01 -0400 Message-ID: <26399.1176614941@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/311 X-Sequence-Number: 24188 cluster writes: > It seems that the FK triggers for the table are evaluated even though > none of the FK columns are altered. Hm, they're not supposed to be, at least not in reasonably modern PG releases (and one that breaks out trigger runtime in EXPLAIN ANALYZE should be modern enough IIRC). Exactly which PG release are you running? Can you provide a self-contained test case? regards, tom lane