Re: BUG #18879: PostgreSQL returns memory error.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: luy70(at)psu(dot)edu
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18879: PostgreSQL returns memory error.
Date: 2025-04-04 21:32:13
Message-ID: 2047360.1743802333@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> CREATE LOCAL TEMP TABLE IF NOT EXISTS v878825600 ( c878825601 INT
> COMPRESSION DEFAULT CONSTRAINT cons_878825602 REFERENCES v878825600 MATCH
> SIMPLE ON UPDATE NO ACTION ON DELETE SET DEFAULT ( c878825601, c878825601,
> c878825601, c878825601, c878825601, c878825601, c878825601 ) PRIMARY KEY )
> ON COMMIT DELETE ROWS;

Thanks for the report. A less illegible repro is

regression=# create temp table v1 (c1 int primary key references v1 on delete set default (c1,c1));
WARNING: problem in alloc set PortalContext: detected write past chunk end in block 0x2c25bc0, chunk 0x2c25e20
WARNING: problem in alloc set PortalContext: detected write past chunk end in block 0x2c25bc0, chunk 0x2c25e20
CREATE TABLE

(With more repetitions of "c1" you can get a crash.) It looks like
we're not being careful to reject duplicates in the SET DEFAULT list.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2025-04-05 03:54:22 Re: BUG #18877: PostgreSQL triggers assertion failure
Previous Message Kirill Reshke 2025-04-04 21:26:29 Re: BUG #18877: PostgreSQL triggers assertion failure