Re: Doc: fix the rewrite condition when executing ALTER TABLE ADD COLUMN - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Doc: fix the rewrite condition when executing ALTER TABLE ADD COLUMN
Date
Msg-id e8c7d857-f719-4398-9f12-849ddc59bf44@eisentraut.org
Whole thread Raw
In response to Re: Doc: fix the rewrite condition when executing ALTER TABLE ADD COLUMN  (Álvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: Doc: fix the rewrite condition when executing ALTER TABLE ADD COLUMN
List pgsql-hackers
On 28.04.25 18:56, Álvaro Herrera wrote:
> On 2025-Apr-23, Nathan Bossart wrote:
> 
>> On Mon, Mar 24, 2025 at 11:37:20AM +0100, Álvaro Herrera wrote:
> 
>>> I'd add a note about these two things to the open items page, and wait
>>> to see if we get some of these limitations fixed, so that if we don't,
>>> we remember to note this limitation in the documentation.
>>
>> Are we still waiting on something for this, or should we proceed with the
>> documentation changes?  It doesn't seem tremendously urgent, but I noticed
>> it's been about a month since the last message on this thread.
> 
> I've edited the Open Items page to disclaim my responsibility from this
> item, since this comes from virtual generated columns which is not my
> turf.  I think we should just document the current state of affairs; we
> can come back with further code improvements during the next cycle.

Here is a proposed patch that includes some text about virtual generated 
columns and also fixes up a small mistake in the previous patch 
(confused identity and generated columns) and improves the wording and 
formatting a bit more.

Attachment

pgsql-hackers by date:

Previous
From: Arseniy Mukhin
Date:
Subject: GIN tries to form a tuple with a partial compressedList during insertion
Next
From: "Zhijie Hou (Fujitsu)"
Date:
Subject: RE: Fix slot synchronization with two_phase decoding enabled