|
Oct 5 |
awarded | Popular Question |
|
Aug 10 |
comment |
How do I create an index to speed up an aggregate LIKE query on an expression in postgres 8.4? For now, I've found a way to suppress the leading wildcard. It turns out you can use an index with LIKE, if you create the index with an appropriate operator class. Docs are here: postgresql.org/docs/8.4/static/indexes-opclass.html |
|
Aug 10 |
accepted | How do I create an index to speed up an aggregate LIKE query on an expression in postgres 8.4? |
|
Aug 9 |
awarded | Supporter |
|
Aug 9 |
awarded | Scholar |
|
Aug 9 |
comment |
How do I create an index to speed up an aggregate LIKE query on an expression in postgres 8.4? Well, after a little bit of research on LIKE and full-text indexing, and I'm beginning to see your point. |
|
Aug 9 |
comment |
How do I create an index to speed up an aggregate LIKE query on an expression in postgres 8.4? Also, the leading % is a necessary feature: the customer service reps need it for finding customer accounts, especially when there's a typo in the email address. |
|
Aug 9 |
comment |
How do I create an index to speed up an aggregate LIKE query on an expression in postgres 8.4? That's what I was afraid of. Is there another kind of index that will help? As I said, I'm a bit constrained in my ability to affect the query itself. |
|
Aug 9 |
awarded | Student |
|
Aug 9 |
asked | How do I create an index to speed up an aggregate LIKE query on an expression in postgres 8.4? |