From: Matt Mello <alien@spaceship.com>
To: pgsql-performance@postgresql.org
Subject: Indexing foreign keys
Date: Mon, 27 Jan 2003 14:39:57 -0600
Message-ID: <3E35991D.5050704@spaceship.com> (raw)
Due to reasons that everyone can probably intuit, we are porting a large
server application from IBM Informix to PG. However, things that take
milliseconds in IFX are taking HOURS (not joking) in PG. I *think* I
may have come across some reasons why, but I would like to see if anyone
else has an opinion. I could not find anything relevant in docs (but if
it is there, please point me to it).
Let me give an example of one of the problems...
I have a table that utilizes 2 foreign keys. It has 400000 records of
approximately 512 bytes each (mostly text, except for the keys). When I
run a specific query on it, it takes 8000ms to complete, and it always
does a full scan.
I "assumed" that since I did not have to create an index on those
foreign key fields in IFX, that I did not have to in PG. However, just
for kicks, I created an index on those 2 fields, and my query time
(after the first, longer attempt, which I presume is from loading an
index) went from 8000ms to 100ms.
So, do we ALWAYS have to create indexes for foreign key fields in PG?
Do the docs say this? (I couldn't find the info.)
I will create other threads for my other issues.
Thanks!
--
Matt Mello
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: alien@spaceship.com
Subject: Re: Indexing foreign keys
In-Reply-To: <3E35991D.5050704@spaceship.com>
References: <3E35991D.5050704@spaceship.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