moving extraUpdatedCols out of RangeTblEntry (into ModifyTable) - Mailing list pgsql-hackers

From Amit Langote
Subject moving extraUpdatedCols out of RangeTblEntry (into ModifyTable)
Date
Msg-id CA+HiwqFshLKNvQUd1DgwJ-7tsTp=dwv7KZqXC4j2wYBV1aCDUA@mail.gmail.com
Whole thread Raw
Responses Re: moving extraUpdatedCols out of RangeTblEntry (into ModifyTable)  (Amit Langote <amitlangote09@gmail.com>)
Re: moving extraUpdatedCols out of RangeTblEntry (into ModifyTable)  (Amit Langote <amitlangote09@gmail.com>)
List pgsql-hackers
Per Alvaro's advice, forking this from [1].

In that thread, Tom had asked if it wouldn't be better to find a new
place to put extraUpdatedCols [2] instead of RangeTblEntry, along with
the permission-checking fields are now no longer stored in
RangeTblEntry.

In [3] of the same thread, I proposed to move it into a List of
Bitmapsets in ModifyTable, as implemented in the attached patch that I
had been posting to that thread.

The latest version of that patch is attached herewith.  I'll add this
one to the January CF too.

-- 
Thanks, Amit Langote
EDB: http://www.enterprisedb.com

[1] https://www.postgresql.org/message-id/CA+HiwqGjJDmUhDSfv-U2qhKJjt9ST7Xh9JXC_irsAQ1TAUsJYg@mail.gmail.com
[2] https://www.postgresql.org/message-id/3098829.1658956718%40sss.pgh.pa.us
[3] https://www.postgresql.org/message-id/CA%2BHiwqEHoLgN%3DvSsaNMaHP-%2BqYPT40-ooySyrieXZHNzbSBj0w%40mail.gmail.com

Attachment

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Perform streaming logical transactions by background workers and parallel apply
Next
From: MichaelDBA
Date:
Subject: Directly associate primary key with user-defined tablespace