Re: support ALTER TABLE DROP EXPRESSION for virtual generated column

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: jian he <jian(dot)universality(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: support ALTER TABLE DROP EXPRESSION for virtual generated column
Date: 2025-03-27 03:15:03
Message-ID: 1818336.1743045303@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

jian he <jian(dot)universality(at)gmail(dot)com> writes:
> the attached patch is to implement $subject.

Why would this be a good idea? I don't see any principled fallback
definition of the column. (No, "NULL" is not that.) Certainly we
should support ALTER TABLE DROP COLUMN, but removing the expression
and not providing a substitute seems semantically nonsensical.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-03-27 03:17:17 Re: Add Postgres module info
Previous Message Tom Lane 2025-03-27 03:09:42 Re: Use CLOCK_MONOTONIC_COARSE for instr_time when available