Bruce Momjian <[EMAIL PROTECTED]> writes: > Sorry to be getting in here late. Have you tried CLUSTER? Prolly won't help much. I think what he's getting burnt by is that the planner thinks that an indexscan based on the LIKE 'http://www.postgresql.org/%' condition will be extremely selective --- it has no idea that most of the URLs in his table will match that prefix. It's ye same olde nonuniform-distribution problem; until we have better statistics, there's not much hope for a non-kluge solution. regards, tom lane
- [HACKERS] How to get around LIKE inefficiencies? The Hermit Hacker
- Re: [HACKERS] How to get around LIKE inefficiencies... Tom Lane
- Re: [HACKERS] How to get around LIKE inefficien... Bruce Momjian
- Re: [HACKERS] How to get around LIKE ineffi... Tom Lane
- Re: [HACKERS] How to get around LIKE in... Philip Warner
- Re: [HACKERS] How to get around LI... Bruce Momjian
- Re: [HACKERS] How to get around LIKE in... Bruce Momjian
- Re: [HACKERS] How to get around LIKE inefficien... Philip Warner
- Re: [HACKERS] How to get around LIKE ineffi... Tom Lane
- Re: [HACKERS] How to get around LIKE in... Philip Warner
- Re: [HACKERS] How to get around LI... The Hermit Hacker
- Re: [HACKERS] How to get aroun... Tom Lane
- Re: [HACKERS] How to get a... The Hermit Hacker
- Re: [HACKERS] How to get aroun... Philip Warner