Re: BUG #18708: regex problem: (?:[^\d\D]){0} asserts with "lp->nouts == 0 && rp->nins == 0"

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexander Lakhin <exclusion@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org, Aleksander Alekseev <aleksander@timescale.com>, dhyan@nataraj.su
Date: 2024-11-17T04:28:49Z
Lists: pgsql-bugs
Alexander Lakhin <exclusion@gmail.com> writes:
> 16.11.2024 19:02, Tom Lane wrote:
>> I'm inclined to guess this was some weird momentary glitch.  If it
>> reproduces then I'll look closer.

> (Un)fortunately, tern (which is also a ppc animal) has produced the same
> failure:
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=tern&dt=2024-11-16%2022%3A00%3A12

Yeah, I saw that.  Even more confused now about what it could be.

			regards, tom lane



Commits

  1. Fix recently-exposed portability issue in regex optimization.

  2. Avoid assertion due to disconnected NFA sub-graphs in regex parsing.

  3. Fix recovery conflict SIGUSR1 handling.

  4. Redesign interrupt/cancel API for regex engine.

  5. Use MemoryContext API for regex memory management.

  6. Invent "rainbow" arcs within the regex engine.