From: | "Postgres User" <postgres(dot)developer(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Chris <dmagick(at)gmail(dot)com>, "Erik Jones" <erik(at)myemma(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Regex query not using index |
Date: | 2008-02-20 05:52:17 |
Message-ID: | b88c3460802192152o3b6eb7e9y9bca5b0e5c7870bf@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
doh! tom, let me know if you decide to hack out a fix for this one of
these nights ;)
thanks for your help.
On Feb 19, 2008 9:45 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Postgres User" <postgres(dot)developer(at)gmail(dot)com> writes:
> > Yes that works, but the whole point of the exercise is replace many OR
> > statements with 1 regex expression. So it's not what I'm looking for.
>
> Unfortunately, Postgres is not as intelligent as you are. There is
> no mechanism to rewrite a multi-branch regex condition into multiple
> indexscans. I recommend going back to the OR's.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Postgres User | 2008-02-20 05:58:36 | Re: Regex query not using index |
Previous Message | Tom Lane | 2008-02-20 05:45:36 | Re: Regex query not using index |