Re: Status report: regex replacement - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Status report: regex replacement
Date
Msg-id Pine.LNX.4.44.0302101750400.6138-100000@peter.localdomain
Whole thread Raw
In response to Status report: regex replacement  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Status report: regex replacement
List pgsql-hackers
Tom Lane writes:

> code is concerned: the regex library actually offers three regex
> flavors, "advanced", "extended", and "basic", where "extended" matches
> what we had before ("extended" and "basic" correspond to different
> levels of the POSIX 1003.2 standard).  We just need a way to expose
> that knob to the user.  I am thinking about inventing yet another GUC
> parameter, say

Perhaps it should be exposed through different operators.  If someone uses
packages (especially functions) provided externally, they might have a
hard time coordinating what flavor is required by which part of what he is
using.

By analogy, imagine there was an environment variable that switched all
grep's to egrep's.  That would be a complete mess.

-- 
Peter Eisentraut   peter_e@gmx.net



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Labeling join rule in EXPLAIN output
Next
From: Peter Eisentraut
Date:
Subject: Re: Why is lc_messages restricted?