From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mark Dilger <mark.dilger@enterprisedb.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Assert triggered during RE_compile_and_cache
Date: Thu, 05 Aug 2021 18:15:27 -0400
Message-ID: <2426993.1628201727@sss.pgh.pa.us> (raw)
In-Reply-To: <7F9BFA6F-9BC6-4A27-BFA1-2F01682BD644@enterprisedb.com>
References: <0203588E-E609-43AF-9F4F-902854231EE7@enterprisedb.com>
<7F9BFA6F-9BC6-4A27-BFA1-2F01682BD644@enterprisedb.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, mark.dilger@enterprisedb.com
Subject: Re: Assert triggered during RE_compile_and_cache
In-Reply-To: <2426993.1628201727@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox