From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Subject: | Re: moving extraUpdatedCols out of RangeTblEntry (into ModifyTable) |
Date: | 2023-01-06 06:33:35 |
Message-ID: | 2914735.1672986815@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Amit Langote <amitlangote09(at)gmail(dot)com> writes:
> BTW, you wrote in the commit message:
> (At present it seems that we don't enforce that for partitioning
> either, which is likely wrong to some degree or other; but the case
> clearly needs to be handled with traditional inheritance.)
> Maybe I'm missing something, but AFICS, neither
> traditional-inheritance child tables nor partitions allow a generated
> column with an expression that is not the same as the parent's
> expression for the same generated column:
Well, there's some large holes in that, as per my post at [1].
I'm on board with locking this down for partitioning, but we haven't
done so yet.
regards, tom lane
[1] https://www.postgresql.org/message-id/2793383.1672944799%40sss.pgh.pa.us
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2023-01-06 06:35:42 | Re: Perform streaming logical transactions by background workers and parallel apply |
Previous Message | Amit Langote | 2023-01-06 06:29:07 | Re: moving extraUpdatedCols out of RangeTblEntry (into ModifyTable) |