Re: support virtual generated column not null constraint

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: jian he <jian(dot)universality(at)gmail(dot)com>, Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Xuneng Zhou <xunengzhou(at)gmail(dot)com>, Navneet Kumar <thanit3111(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: support virtual generated column not null constraint
Date: 2025-03-28 14:06:16
Message-ID: c6245804-0dfd-4f31-98ab-cd29bb78f5bf@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 24.03.25 04:26, jian he wrote:
> rebase, and some minor code comments change.

I have committed this.

I did a bit more editing on the naming of various things. In terms of
functionality, in ExecConstraints() notnull_virtual_attrs and
virtual_notnull_check were redundant, so I simplified that. I also cut
back a little bit on the assertions. They were all ok, but I felt in
some places they bloated the code quite a bit for no real gain.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2025-03-28 14:11:15 Re: Test to dump and restore objects left behind by regression
Previous Message Tom Lane 2025-03-28 14:06:01 Re: Buffer overflow in zic