| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Subject: | Re: moving extraUpdatedCols out of RangeTblEntry (into ModifyTable) |
| Date: | 2022-12-08 02:47:21 |
| Message-ID: | CA+HiwqGtp7+c06+LDBkUFLrhgPbAYrdBHLAj_k4bBSi7BHB_tA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Dec 7, 2022 at 8:54 PM Amit Langote <amitlangote09(at)gmail(dot)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 | Content-Type | Size |
|---|---|---|
| v2-0001-Add-per-result-relation-extraUpdatedCols-to-Modif.patch | application/octet-stream | 25.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Corey Huinker | 2022-12-08 03:37:28 | Re: Error-safe user functions |
| Previous Message | Masahiko Sawada | 2022-12-08 02:46:44 | Re: Assertion failure in SnapBuildInitialSnapshot() |