Re: WIP: lookbehind constraints for our regexp engine - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: WIP: lookbehind constraints for our regexp engine
Date
Msg-id CAKFQuwZVaVK_vMi=-Z7y0GkqASL-SsGwnsyUvTk2dYkxS3yU5A@mail.gmail.com
Whole thread Raw
In response to WIP: lookbehind constraints for our regexp engine  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Friday, October 16, 2015, Tom Lane <tgl@sss.pgh.pa.us> wrote:

Anyway, I'm not planning to do much more work on this right now, but
I thought I'd throw it out there just to let people know that this seems
within reach.  I'm curious to know how many people care, and how much.


+1

It's hard to quantify how much but look behind is a tool that I find occasion to use.  My most recent need involved ensuring that the current position after processing two variable length matches is exactly n characters from the start of the string.

I don't have any immediate projects that would be refactored into a more pure SQL variation for having this feature so on that the strength is fairly low.  But if you are going to do it then now, while it is fresh, would be the best time.

David J. 

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: [HACKERS] Re: [HACKERS] Windows service is not starting so there’s message in log: FATAL: "could not create shared memory segment “Global/PostgreSQL.851401618”: Permission denied”
Next
From: Simon Riggs
Date:
Subject: Re: Allow ssl_renegotiation_limit in PG 9.5