From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Rod Taylor <rod(dot)taylor(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Could regexp_matches be immutable? |
Date: | 2009-10-14 22:17:21 |
Message-ID: | 20091014221721.GA19233@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Oct 14, 2009 at 06:06:23PM -0400, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> > David Fetter wrote:
> >> Speaking of which, can we see about deprecating and removing this GUC?
> >> I've yet to hear of anyone using a flavor other than the default.
>
> > You have now. I have a client who sadly uses a non-default setting. And
> > on 8.4, what is more.
>
> How critical is it to them? It would be nice to get rid of that source
> of variability.
>
> It would be possible to keep using old-style regexes even without the
> GUC, if they can interpose anything that can stick an "embedded options"
> prefix on the pattern strings. See 9.7.3.4:
> http://developer.postgresql.org/pgdocs/postgres/functions-matching.html
Switching it to just embedded options solves the issue of leaving the
feature in while cutting the surprises down for those not using it. :)
The "embedded options" method is also doable by search-and-replace, as
they only work in AREs, which such people wouldn't be using.
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 | Mark Mielke | 2009-10-14 22:21:15 | Re: Rejecting weak passwords |
Previous Message | Tom Lane | 2009-10-14 22:16:46 | Re: Triggers on columns |