From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
Cc: | "Kaare Rasmussen" <kaare(at)jasonic(dot)dk>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Questions about indexes with text_pattern_ops |
Date: | 2008-02-25 17:40:28 |
Message-ID: | 29056.1203961228@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> How so? If you think this change is a bad idea you'd better speak up
>> PDQ.
> Well I think it's fine for 'foo ' != 'foo' even if they sort similarly.
> But I'm not sure it makes sense for <'foo ','a'> to sort after <'foo','b'> if
> the locale says that 'foo ' should be compare "equal" to 'foo' and 'a' before
> 'b'.
I don't think we can concern ourselves with that; it would require
allowing different columns of an index to interact, which would be
impossibly messy. What's more, it'd destroy the property that a btree
index is sorted by its leading column(s) as well as by all its columns.
> Perhaps we should always generate those inequalities even if there's no index
> that can use them.
Hmmm ... we intentionally don't do that, but the constraint exclusion
code might be a sufficient reason to reconsider.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2008-02-25 17:55:42 | pgsql: Link postgres from all object files at once, to avoid the |
Previous Message | Roberts, Jon | 2008-02-25 17:36:55 | pgAgent job throttling |