Re: Adding a stored generated column without long-lived locks

From: Alberto Piai <alberto(dot)piai(at)gmail(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Alberto Piai <alberto(dot)piai(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Cc: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Subject: Re: Adding a stored generated column without long-lived locks
Date: 2026-08-28 05:50:15
Message-ID: DL0C8TG99HCO.1XVPKG2IM0C1S@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed Aug 26, 2026 at 7:20 AM CEST, Laurenz Albe wrote:
>> Since the root of the hierarchy is in both cases just a table
>> (partitoned or not), what about just calling it a table?
>>
>>   ERROR:  cannot convert column "c" to generated
>>   DETAIL:  Converting only part of a partitioning or inheritance hierarchy is not supported.
>>   HINT:  Use this command on the root table without specifying ONLY.
>
> Both variants look fine to me. Pick the one you prefer.

OK, I went with "table" then.

Here's v9, rebased on top of current master.

Best regards,

Alberto

--
Alberto Piai
Sensational AG
Zürich, Switzerland

Attachment Content-Type Size
v9-0001-Support-changing-a-column-into-a-stored-generated.patch text/plain 71.4 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2026-08-28 05:52:17 Re: First draft of PG 19 release notes
Previous Message Ajit Awekar 2026-08-28 05:43:39 Re: [(known) BUG] DELETE/UPDATE more than one row in partitioned foreign table