| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | 303677365(at)qq(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19421: PostgreSQL MERGE Crash: heap_compute_data_size() at heaptuple.c:236 |
| Date: | 2026-02-28 19:56:02 |
| Message-ID: | 26513.1772308562@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> PostgreSQL version: 15.5
The current release in that branch is 15.17; 15.5 is more than two
years out of date.
> -- PostgreSQL MERGE SIGSEGV Minimal Reproduction
> -- Crash location: heap_compute_data_size() at heaptuple.c:236
In 15.17, this example seems to do what I'd expect:
ERROR: new row for relation "parent_tbl" violates check constraint "pcheck"
DETAIL: Failing row contains (1, 100).
Quickly trawling the commit log, I'd guess this was fixed in
commit d6a3f3272ffee792e27c5dd871d7cf1cbf418962.
Please test against current release(s) before submitting bug reports.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Guo | 2026-03-02 05:09:46 | Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor> |
| Previous Message | PG Bug reporting form | 2026-02-28 01:26:07 | BUG #19421: PostgreSQL MERGE Crash: heap_compute_data_size() at heaptuple.c:236 |