From: Andrew Lazarus <andrew@pillette.com>
To: pgsql-performance@postgresql.org
Subject: when is a DELETE FK trigger planned?
Date: Mon, 25 Feb 2008 12:56:26 -0800
Message-ID: <010161370.20080225125626@pillette.com> (raw)
I have a cascading delete trigger that is obviously using a seqscan.
(Explain analyze shows that trigger as taking over 1000s while all
other triggers are <1s. The value in test delete didn't even appear in
this child table, so an index scan would have been almost instant.)
If I do
DELETE FROM child_table WHERE fkey = value;
I get an index scan. Why doesn't the trigger do that, and how can I
force it to re-plan?
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: andrew@pillette.com
Subject: Re: when is a DELETE FK trigger planned?
In-Reply-To: <010161370.20080225125626@pillette.com>
* 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