Question about Foreign key constraint causes "costly sequential scans"? - Mailing list pgsql-general

From Emi Lu
Subject Question about Foreign key constraint causes "costly sequential scans"?
Date
Msg-id 430B32F6.7090408@cs.concordia.ca
Whole thread Raw
Responses Re: Question about Foreign key constraint causes "costly sequential scans"?  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Question about Foreign key constraint causes "costly  (Matt Miller <mattm@epx.com>)
Re: Question about Foreign key constraint causes "costly sequential scans"?  (Michael Fuhr <mike@fuhr.org>)
List pgsql-general
Greetings,

I have a question about foreign key cost. I have two tables A and B.
A has 300,000 records, B has 3 records.

A (col1, col2, col3... ... colN)

B (colB1 primary key, colB2)

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

Some comments about it?

Thanks a lot!
Emi




pgsql-general by date:

Previous
From: "Ilja Golshtein"
Date:
Subject: Re: ctid access is slow
Next
From: "Thomas F. O'Connell"
Date:
Subject: Re: ORDER BY time consuming