Re: Force ARE in regexp string

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Johannes Öberg <johannes(dot)oberg(at)proactivegaming(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Force ARE in regexp string
Date: 2010-09-15 13:33:00
Message-ID: 3954.1284557580@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

=?ISO-8859-1?Q?Johannes_=D6berg?= <johannes(dot)oberg(at)proactivegaming(dot)com> writes:
> Hi! I'm trying to do an advanced regexp match but postgres doesn't
> seem to let me.

> I've set regex_flavor to ARE, and I've tried prefixing my strings, i.e.
> ~* E'***:abc' but for some reason postgres treats all my regexps as BRE's.

> Common newbie gotchas?

Well, the symptom as described seems pretty improbable. You didn't show
an exact example, but I'm suspecting the real problem is that you're not
allowing for backslashes in a string literal getting eaten by string
parsing. Do the cases that don't work for you involve backslashes in
the regex?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Gary Fu 2010-09-15 13:46:11 Re: select sql slow inside function
Previous Message Peter Hopfgartner 2010-09-15 12:55:39 Getting FATAL: terminating connection due to administrator command