| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
| Subject: | Re: Virtual generated columns |
| Date: | 2025-01-08 16:38:58 |
| Message-ID: | 1662507.1736354338@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter(at)eisentraut(dot)org> writes:
> On 03.12.24 15:15, jian he wrote:
>> SELECT attrelid, attname, attgenerated FROM pg_attribute WHERE
>> attgenerated IN ('v') and (attnotnull or not atthasdef);
> I don't understand what the purpose of testing attnotnull is. That is
> independent of attgenerated, I think.
Does it make any sense to set NOT NULL on a generated column (virtual
or otherwise, but especially virtual)? What is the system supposed
to do if the expression evaluates to null? That concern generalizes
to any constraint really. Even if we checked it at row storage time,
there's no real guarantee that the expression is immutable enough
to pass the constraint later.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mahendra Singh Thalor | 2025-01-08 16:41:17 | Re: Non-text mode for pg_dumpall |
| Previous Message | Pavel Stehule | 2025-01-08 16:33:31 | Re: Re: proposal: schema variables |