From: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Assert triggered during RE_compile_and_cache |
Date: | 2021-08-05 22:22:57 |
Message-ID: | 29C525E6-A912-459F-BE27-217F25F76B5E@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On Aug 5, 2021, at 3:15 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> I don't immediately see what's different about your failing case
> versus the not-failing ones.
I have now found lots of cases of this failure. I *believe* the backreference is always greater than 1, and it is always in a capture group which then has the {0} or {0,0} applied to it.
You can find lots of cases using the attached regex generating script I whipped up for testing your work. (Note this is just a quick and dirty tool for hacking, not anything refined.)
Attachment | Content-Type | Size |
---|---|---|
backref.pl | text/x-perl-script | 4.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Dilger | 2021-08-05 22:30:20 | Re: Accidentally dropped constraints: bug? |
Previous Message | Tom Lane | 2021-08-05 22:15:27 | Re: Assert triggered during RE_compile_and_cache |