Re: text_pattern_ops and complex regexps

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: 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 20:43:36
Message-ID: 27269.1241642616@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> ... Maybe we should make that
> setting PGC_POSTMASTER (or just get rid of it?),

Another thought here: if we do get persuaded that the regex_flavor GUC
has to stay, we could eliminate it as a hazard for planning by changing
its scope to PGC_BACKEND. That would be much less restrictive than
PGC_POSTMASTER; for instance it'd still work to set it for a particular
application via ALTER ROLE.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2009-05-06 20:47:45 Re: text_pattern_ops and complex regexps
Previous Message Dickson S. Guedes 2009-05-06 20:42:39 Re: Patch to fix search_path defencies with pg_bench