From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexander Pyhalov <a.pyhalov@postgrespro.ru>
Cc: Pgsql Hackers <pgsql-hackers@postgresql.org>
Subject: Re: PostgreSQL 14 backend crash on incorrect trigger
Date: Wed, 07 Jul 2021 15:22:06 -0400
Message-ID: <1902516.1625685726@sss.pgh.pa.us> (raw)
In-Reply-To: <b9a6f53549456b2f3e2fd150dcd79d72@postgrespro.ru>
References: <b9a6f53549456b2f3e2fd150dcd79d72@postgrespro.ru>
Alexander Pyhalov <a.pyhalov@postgrespro.ru> writes:
> The following test case makes postgresql backend crash. The trigger is
> incorrect, but this didn't crash postgresql before
Yup, that's a silly oversight. Fixed, thanks for the report!
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, a.pyhalov@postgrespro.ru
Subject: Re: PostgreSQL 14 backend crash on incorrect trigger
In-Reply-To: <1902516.1625685726@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