Re: Question about Foreign key constraint causes "costly sequential scans"?

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: Emi Lu <emilu(at)cs(dot)concordia(dot)ca>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Question about Foreign key constraint causes "costly sequential scans"?
Date: 2005-08-23 15:04:25
Message-ID: 20050823150425.GA9588@winnie.fuhr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Aug 23, 2005 at 10:30:14AM -0400, Emi Lu wrote:
> I'd like to setup foreign key constraint for A.col3, as the following:
> CONSTRAINT Aclo3_fk FOREIGN KEY (col3) REFERENCES B(colB1)
>
> But I got a warning msg from postgresql as:
>
> foreign key constraint "Aclo3_fk" will require costly sequential scans

Is there not a DETAIL message following this warning? It should
explain the problem: the referring and the referred-to columns are
of different types.

Additionally, it's usually a good idea to create an index on the
referring column (A.col3) to speed up referential integrity checks
when modifying the referred-to table (B).

--
Michael Fuhr

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Fuhr 2005-08-23 15:18:05 Re: Import File
Previous Message Tom Lane 2005-08-23 14:57:08 Re: Question about Foreign key constraint causes "costly sequential scans"?