From: Tom Lane <tgl@sss.pgh.pa.us>
To: exclusion@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17113: Assert failed on calling a function fixed after an extension reload
Date: Mon, 19 Jul 2021 10:49:28 -0400
Message-ID: <260356.1626706168@sss.pgh.pa.us> (raw)
In-Reply-To: <17113-077605ce00e0e7ec@postgresql.org>
References: <17113-077605ce00e0e7ec@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> The following SQL snippet:
> ...
> leads to a failed assertion with the following stack:
Hmm ... it seems fine in v14 and HEAD, but I do see the crash in v13.
I have some errands to run, but will take a closer look later.
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-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, exclusion@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17113: Assert failed on calling a function fixed after an extension reload
In-Reply-To: <260356.1626706168@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