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

From Amit Langote
Subject Re: moving extraUpdatedCols out of RangeTblEntry (into ModifyTable)
Date
Msg-id CA+HiwqGtp7+c06+LDBkUFLrhgPbAYrdBHLAj_k4bBSi7BHB_tA@mail.gmail.com
Whole thread Raw
In response to moving extraUpdatedCols out of RangeTblEntry (into ModifyTable)  (Amit Langote <amitlangote09@gmail.com>)
Responses Re: moving extraUpdatedCols out of RangeTblEntry (into ModifyTable)  (vignesh C <vignesh21@gmail.com>)
Re: moving extraUpdatedCols out of RangeTblEntry (into ModifyTable)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Dec 7, 2022 at 8:54 PM Amit Langote <amitlangote09@gmail.com> wrote:
> 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.

Updated to replace a list_nth() with list_nth_node() and rewrote the
commit message.

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

Attachment

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Assertion failure in SnapBuildInitialSnapshot()
Next
From: Corey Huinker
Date:
Subject: Re: Error-safe user functions