From: Bruno Wolff III <bruno@wolff.to>
To: David Gagnon <dgagnon@siunik.com>
Cc: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Why the planner is not using the INDEX .
Date: Tue, 5 Jul 2005 07:32:17 -0500
Message-ID: <20050705123217.GA11379@wolff.to> (raw)
In-Reply-To: <42C9D47E.7090103@siunik.com>
References: <20050630222451.GA17628@calvin.surfutopia.net>
<42C473BA.9090305@commandprompt.com>
<20050630235821.GA2163@calvin.surfutopia.net>
<42C994BD.3000909@siunik.com>
<20050704132446.O14579@megazone.bigpanda.com>
<42C9D47E.7090103@siunik.com>
On Mon, Jul 04, 2005 at 20:29:50 -0400,
David Gagnon <dgagnon@siunik.com> wrote:
> Thanks .. I miss that FK don't create indexed ... since Primary key
> implicitly does ...
>
> I'm a bit surprised of that behavior thought, since it means that if we
> delete a row from table A all tables (B,C,D) with FK pointing to this
> table (A) must be scanned.
But in some applications you don't ever do that, so you don't save
anything by having the index for deletes but have to pay the cost to
update it when modifying the referencing table.
If you think an index will help in your case, just create one.
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: bruno@wolff.to, dgagnon@siunik.com, sszabo@megazone.bigpanda.com
Subject: Re: Why the planner is not using the INDEX .
In-Reply-To: <20050705123217.GA11379@wolff.to>
* 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