Re: Force ARE in regexp string

From: Johannes Öberg <johannes(dot)oberg(at)proactivegaming(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Force ARE in regexp string
Date: 2010-09-22 16:42:45
Message-ID: 4C9A3205.9020409@proactivegaming.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2010-09-15 15:33, Tom Lane wrote:
> =?ISO-8859-1?Q?Johannes_=D6berg?=<johannes(dot)oberg(at)proactivegaming(dot)com> writes:
>> 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.
> 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
>
This was indeed what was happening, problem solved, thanks alot! Now,
I'm having new problems with Postgres seemingly thinking I'm regexping
too much for a single query, but that's will be another thread.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2010-09-22 16:43:09 Re: Kill -9 for a session process caused all the sessions to be killed
Previous Message Atul.Goel 2010-09-22 16:26:29 Kill -9 for a session process caused all the sessions to be killed