Re: Force ARE in regexp string - Mailing list pgsql-general

From Johannes Öberg
Subject Re: Force ARE in regexp string
Date
Msg-id 4C9A3205.9020409@proactivegaming.com
Whole thread Raw
In response to Re: Force ARE in regexp string  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
  On 2010-09-15 15:33, Tom Lane wrote:
> =?ISO-8859-1?Q?Johannes_=D6berg?=<johannes.oberg@proactivegaming.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.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Kill -9 for a session process caused all the sessions to be killed
Next
From: Whit Armstrong
Date:
Subject: file output via trigger/queue