From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: text_pattern_ops and complex regexps |
Date: | 2009-05-06 17:15:07 |
Message-ID: | 20090506171507.GP20491@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, May 06, 2009 at 12:10:49PM -0400, Alvaro Herrera wrote:
> Tom Lane wrote:
> > Stephen Frost <sfrost(at)snowman(dot)net> writes:
>
> > > Perhaps this is misguided but I would think that the regexp
> > > libraries might have some support for "give me all anchored
> > > required text for this regexp" which we could then use in the
> > > planner.
> >
> > I wouldn't see why. It's certainly worth considering to hand the
> > pattern to the regex engine and then burrow into the data
> > structure it builds; but right now we consider that structure to
> > be entirely private to backend/regex/. There's also the problem
> > that we'd have no easy way to determine how much the result
> > depends on the current regex flavor setting. There are some cases
> > now where regex_fixed_prefix deliberately omits possible
> > optimizations because of uncertainty about the flavor.
>
> I think changeable regex flavors turned out to be a bad idea.
+1
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Stefan Kaltenbrunner | 2009-05-06 17:18:52 | Re: text_pattern_ops and complex regexps |
Previous Message | Andres Freund | 2009-05-06 16:32:17 | Re: conditional dropping of columns/constraints |