From: | "James Cooper" <jim(at)luckydigital(dot)com> |
---|---|
To: | "sql" <pgsql-sql(at)postgresql(dot)org> |
Subject: | indexing |
Date: | 2003-02-24 20:38:28 |
Message-ID: | 006a01c2dc48$94d665f0$c900a8c0@jax |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Hi all,
I've been doing a little reading on indexing in prelude to indexing my db.
I have the following to ask:
if I had three tables for a many to many relationship say A, B, AND C
B being the lookup. B being a huge 50k rows plus column and made just two forigen keys(b.a_id,b.c_id).
is it best to create two non-unique indexes or one unique index on both fields?
Please advise
Ps
I also attempted creating an index on a table i have called person on person_id and
ran
Explain
select person_id from person where person_id < n
but saw no results of my created index being used - am i doing something incorrectly
Pps
When indexing if searching tables is more important than concurrency - which type of index is best?
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2003-02-24 22:33:49 | Re: Denormalizing during select |
Previous Message | Jeff Boes | 2003-02-24 19:12:03 | Re: Denormalizing during select |