Re: moving extraUpdatedCols out of RangeTblEntry (into ModifyTable)

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-07 11:57:09
Message-ID: CA+HiwqHn34nVP7Q6gFWWpw1SrZbHCexHVPSwadLWRq6E1Z-zJw@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. I'll add this
> one to the January CF too.

Done.

https://commitfest.postgresql.org/41/4049/

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2022-12-07 12:20:41 Re: Support logical replication of DDLs
Previous Message MichaelDBA 2022-12-07 11:56:55 Directly associate primary key with user-defined tablespace