From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: WIP: lookbehind constraints for our regexp engine |
Date: | 2015-10-17 14:15:24 |
Message-ID: | CAKFQuwZVaVK_vMi=-Z7y0GkqASL-SsGwnsyUvTk2dYkxS3yU5A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Friday, October 16, 2015, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2015-10-17 14:18:50 | Re: Allow ssl_renegotiation_limit in PG 9.5 |
Previous Message | Michael Paquier | 2015-10-17 14:10:56 | Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby |