From: Tom Lane <tgl@sss.pgh.pa.us>
To: cluster <skrald@amossen.dk>
Cc: pgsql-performance@postgresql.org
Subject: Re: FK triggers misused?
Date: Mon, 16 Apr 2007 19:49:56 -0400
Message-ID: <12205.1176767396@sss.pgh.pa.us> (raw)
In-Reply-To: <f00vq0$2ncr$1@news.hub.org>
References: <evqm6g$29b1$1@news.hub.org>
<26399.1176614941@sss.pgh.pa.us>
<slrnf23eqp.10cj.andrew+nonews@atlantis.supernews.net>
<102.1176650563@sss.pgh.pa.us>
<slrnf258g3.10cj.andrew+nonews@atlantis.supernews.net>
<f00vq0$2ncr$1@news.hub.org>
cluster <skrald@amossen.dk> writes:
>> So the next question is, what pg version is the original poster using?
>> because 8.1.x doesn't report trigger execution times, and 8.2.x would use
>> a single bitmap index scan with an = ANY condition, not a BitmapOr.
> I have tried 8.1.0 and 8.1.3 for this query.
Checking the code, 8.1.x does report trigger times, so AndrewSN is
mistaken on that point.
However, it's also the case that 8.1 does have the suppress-the-trigger
logic for FKs, and it works fine for me in a simple test. I'm using
8.1 branch tip, but there are no relevant changes since 8.1.0 as far
as I can see in the CVS logs.
What is that non-FK trigger shown in your results?
> Trigger posts_tsvectorupdate: time=61.659 calls=5
Could it possibly be firing an extra update on the table?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, skrald@amossen.dk
Subject: Re: FK triggers misused?
In-Reply-To: <12205.1176767396@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox