Re: Assert triggered during RE_compile_and_cache

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

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

To: Mark Dilger <mark.dilger@enterprisedb.com>

Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2021-08-05T22:15:27Z

Lists: pgsql-hackers

Mark Dilger <mark.dilger@enterprisedb.com> writes:
> +select '' ~ '(())(\2){0}';
> +server closed the connection unexpectedly

> Any ideas?

Huh.  This seems like some deficiency in the part of parseqatom
starting with

	/* annoying special case:  {0} or {0,0} cancels everything */
	if (m == 0 && n == 0)

but I don't immediately see what's different about your failing case
versus the not-failing ones.

			regards, tom lane

Commits

Check the size in COPY_POINTER_FIELD
- c1132aae336c 15.0 cited
Rethink regexp engine's backref-related compilation state.
- 5227d9989672 14.0 landed
- 00116dee5ad4 15.0 landed
Fix use-after-free issue in regexp engine.
- f42ea8350db2 14.0 landed
- cc1868799c83 15.0 landed
Make regexp engine's backref-related compilation state more bulletproof.
- cb76fbd7ec87 15.0 landed
- 5e6ad63c6db7 14.0 landed
Really fix the ambiguity in REFRESH MATERIALIZED VIEW CONCURRENTLY.
- ba9f665a4413 13.4 cited
Avoid generating extra subre tree nodes for capturing parentheses.
- ea1268f6301c 14.0 cited