From: | Jaime Casanova <systemguards(at)yahoo(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | multi-key index |
Date: | 2004-12-20 17:58:21 |
Message-ID: | 20041220175821.40410.qmail@web50002.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi everyone,
From the TODO items:
Use index to restrict rows returned by multi-key index
when used with non-consecutive keys to reduce heap
accesses.
For an index on col1,col2,col3, and a WHERE clause of
col1 = 5 and col3 = 9, spin though the index checking
for col1 and col3 matches, rather than just col1; also
called skip-scanning.
I was looking in the archives something about this but
i found nothing. Where can i found the thread (i
suppose should be one) about this issue?
regards,
Jaime Casanova
_________________________________________________________
Do You Yahoo!?
Información de Estados Unidos y América Latina, en Yahoo! Noticias.
Visítanos en http://noticias.espanol.yahoo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-12-20 18:03:05 | Re: multi-key index |
Previous Message | Tom Lane | 2004-12-20 16:47:41 | Re: Shared row locking |