From: | ow <oneway_111(at)yahoo(dot)com> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: pg 7.4.rc1, Range query performance |
Date: | 2003-11-11 11:46:39 |
Message-ID: | 20031111114639.15081.qmail@web21402.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
--- Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> wrote:
> Tom Lane wrote:
> > Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > > Sorry there isn't a simple solution.
> >
> > But there is: make an index with the column order (b,c,a).
>
> Oh, yea, right. If he puts the columns he is doing a straight equals
> comparison first, the 'a' comparison will work fine. Great.
>
Yes, I think Stephan Szabo was trying to convince me of something like that for
quite sometime; it was not clear to me then. I'll give it a try.
I still think "CREATE [CLUSTERED] INDEX" (or whatever) is an important feature
and should be implemented in pgSql. Locking large (or huge) tables for
prolonged periods of time may not be acceptable in many setups.
Thanks
__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree
From | Date | Subject | |
---|---|---|---|
Next Message | alban | 2003-11-11 11:52:14 | Re: 7.3 how remove password valid until |
Previous Message | sad | 2003-11-11 11:45:22 | a question to developers |