From: Alexander Lakhin <exclusion@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Richard Guo <guofenglinux@gmail.com>
Cc: pgsql-bugs@postgresql.org
Subject: Re: Assert failure when CREATE TEMP TABLE
Date: Tue, 17 Oct 2023 12:00:00 +0300
Message-ID: <b9a42817-d913-03ab-b717-97606e0b758a@gmail.com> (raw)
In-Reply-To: <2301835.1697471214@sss.pgh.pa.us>
References: <CAMbWs4-x26=_QxxgdJyNbiCDzvtr2WV5ZDso_v-CukKEe6cBZw@mail.gmail.com>
<2301835.1697471214@sss.pgh.pa.us>
16.10.2023 18:46, Tom Lane wrote:
> Richard Guo <guofenglinux@gmail.com> writes:
>> I came across an Assert failure while running sqlancer. The repro query
>> is
> Hmm. AFAICT, the critical thing about this CHECK condition is simply
> that it's bulky enough to create an out-of-line toasted "conbin" field
> in pg_constraint. When we come to ON COMMIT DROP, we have to delete
> the pg_constraint entry and thereby the toast item, and we evidently
> lack a snapshot at that point.
That's very similar to bug #18127, and looks like one more case to the
collection [1], with RemoveConstraintById() -> CatalogTupleDelete() ->
simple_heap_delete() ...
https://www.postgresql.org/message-id/9541c507-a325-7768-38b0-90f6532c01e3%40gmail.com
Best regards,
Alexander
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: exclusion@gmail.com, tgl@sss.pgh.pa.us, guofenglinux@gmail.com
Subject: Re: Assert failure when CREATE TEMP TABLE
In-Reply-To: <b9a42817-d913-03ab-b717-97606e0b758a@gmail.com>
* 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