Re: bug when apply fast default mechanism for adding new column over domain with default value - Mailing list pgsql-hackers

From Alexander Lakhin
Subject Re: bug when apply fast default mechanism for adding new column over domain with default value
Date
Msg-id 025a3ffa-5eff-4a88-97fb-8f583b015965@gmail.com
Whole thread Raw
In response to Re: bug when apply fast default mechanism for adding new column over domain with default value  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: bug when apply fast default mechanism for adding new column over domain with default value
List pgsql-hackers
Hello Tom,

03.03.2025 20:38, Tom Lane wrote:
Pushed with that adjustment and some other minor polishing.

I've discovered that 95f650674 introduced a defect similar to bug #18297,
but this time with DEFAULT. Namely, the following script:
CREATE TABLE a (aa text);
CREATE TABLE c (cc text) INHERITS (a);
CREATE TABLE d (dd text) INHERITS (c, a);
ALTER TABLE a ADD COLUMN i int DEFAULT 1;

fails with:
ERROR:  XX000: tuple already updated by self
LOCATION:  simple_heap_update, heapam.c:4421

Best regards,
Alexander Lakhin
Neon (https://neon.tech)

pgsql-hackers by date:

Previous
From: Renan Alves Fonseca
Date:
Subject: Document SQL functions behavior regarding custom/generic plan
Next
From: Daniel Gustafsson
Date:
Subject: Re: Test to dump and restore objects left behind by regression