Message-ID: <b9a42817-d913-03ab-b717-97606e0b758a@gmail.com>
Date: Tue, 17 Oct 2023 12:00:00 +0300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.4.2
Subject: Re: Assert failure when CREATE TEMP TABLE
To: Tom Lane <tgl@sss.pgh.pa.us>, Richard Guo <guofenglinux@gmail.com>
Cc: pgsql-bugs@postgresql.org
References: 
 <CAMbWs4-x26=_QxxgdJyNbiCDzvtr2WV5ZDso_v-CukKEe6cBZw@mail.gmail.com>
 <2301835.1697471214@sss.pgh.pa.us>
Content-Language: en-US
From: Alexander Lakhin <exclusion@gmail.com>
In-Reply-To: <2301835.1697471214@sss.pgh.pa.us>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/b9a42817-d913-03ab-b717-97606e0b758a%40gmail.com>
Precedence: bulk

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