| From: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Richard Guo <guofenglinux(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Assert failure when CREATE TEMP TABLE |
| Date: | 2023-10-17 09:00:00 |
| Message-ID: | b9a42817-d913-03ab-b717-97606e0b758a@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
16.10.2023 18:46, Tom Lane wrote:
> Richard Guo <guofenglinux(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2023-10-17 10:49:47 | Re: Error “Unable to Write Inside Temp Environment Variable Path” |
| Previous Message | Le Thai Hoa | 2023-10-17 08:00:58 | Error “Unable to Write Inside Temp Environment Variable Path” |