From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Jaime Casanova <systemguards(at)yahoo(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: multi-key index |
Date: | 2004-12-20 18:03:05 |
Message-ID: | 200412201803.iBKI35J03818@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jaime Casanova wrote:
> 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?
I don't remember any detailed discussion on it except that it would be a
good idea.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2004-12-20 18:09:24 | Re: Shared row locking |
Previous Message | Jaime Casanova | 2004-12-20 17:58:21 | multi-key index |