From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: TODO Items |
Date: | 2004-08-04 03:25:47 |
Message-ID: | 87brhrmvno.fsf@stark.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > . Allow multi-column indexes to be used to optimize row-value expressions. Ie,
> > allow a btree index on a,b to be used to execute an expression like (a,b) <
> > (x,y).
>
> I have not heard of any of those so I have not been actively excluding
> them from the TODO list. However, I need someone with optimizer
> experience to make a recommendation.
Well the row-value expression stuff comes out of a discussion just this week.
You could check messages on pgsql-performance with the subject "[PERFORM] best
way to fetch next/prev record based on index". In particular Tom's messages
from Wednesday the 28th might be relevant.
The optimization in the first one came up in a conversation that was quite a
bit older. I don't have that thread saved. It seems like an obvious
optimization if it can be done efficiently.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Mascari | 2004-08-04 03:27:35 | Re: Preliminary PITR documentation available |
Previous Message | Scott Marlowe | 2004-08-04 02:51:45 | Re: Updateable Views? |
From | Date | Subject | |
---|---|---|---|
Next Message | Jamie Deppeler | 2004-08-04 04:28:27 | Point in Time Recovery |
Previous Message | Bruce Momjian | 2004-08-04 02:37:51 | Re: pgxs: build infrastructure for extensions v4 |