Re: not null constraints, again

From: Tender Wang <tndrwang(at)gmail(dot)com>
To: jian he <jian(dot)universality(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: not null constraints, again
Date: 2024-09-20 04:14:12
Message-ID: CAHewXNm+qmT6V0HJCsjsO9R7EyJwXyz8mbBOY3ES7cR7K3djvA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

jian he <jian(dot)universality(at)gmail(dot)com> 于2024年9月20日周五 11:34写道:

> another bug.
> I will dig later, just want to share it first.
>
> minimum producer:
> drop table if exists pp1,cc1, cc2,cc3;
> create table pp1 (f1 int );
> create table cc1 () inherits (pp1);
> create table cc2() inherits(pp1,cc1);
> create table cc3() inherits(pp1,cc1,cc2);
>
> alter table pp1 alter f1 set not null;
> ERROR: tuple already updated by self
>

I guess some place needs call CommandCounterIncrement().

--
Thanks,
Tender Wang

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2024-09-20 04:25:56 Re: Pgoutput not capturing the generated columns
Previous Message vignesh C 2024-09-20 04:06:44 Re: Logical Replication of sequences