Message-ID: <487a96ce-9a5e-d89c-b1e7-c3a8285d8b15@enterprisedb.com>
Date: Fri, 25 Mar 2022 16:20:05 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0)
 Gecko/20100101 Thunderbird/91.7.0
Subject: Re: automatically generating node support functions
Content-Language: en-US
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: David Rowley <dgrowleyml@gmail.com>,
 pgsql-hackers <pgsql-hackers@postgresql.org>
References: <c1097590-a6a4-486a-64b1-e1f9cc0533ce@enterprisedb.com>
 <2f876203-7142-fa71-6d22-6ce00eb26869@enterprisedb.com>
 <c091e5cd-45f8-69ee-6a9b-de86912cc7e7@enterprisedb.com>
 <b85eec6e-a54b-6c72-97f8-2a6fbf4f9070@enterprisedb.com>
 <c683a356-4d22-4126-bf55-64ed54e06014@enterprisedb.com>
 <50fedc80-4104-bdc8-d777-04f030fc550f@dunslane.net>
 <7848b872-7a10-67b2-b55f-7c9c475ae863@enterprisedb.com>
 <40a2e977-98ba-0c01-af6c-9dfb39e864ba@enterprisedb.com>
 <812ea8eb-6827-ba32-6ec0-6714f7ffa5dd@enterprisedb.com>
 <2905876.1644858587@sss.pgh.pa.us>
 <bee9fdb0-cd10-5fdb-3027-c4b5a240bc74@enterprisedb.com>
 <CAApHDvppoxUxzRJbwF9oOF12ngdfNoPEMfDsu63+LREgGnheUw@mail.gmail.com>
 <968928d9-a526-a1b5-dc36-0355632a843e@enterprisedb.com>
 <3236082.1648215164@sss.pgh.pa.us>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
In-Reply-To: <3236082.1648215164@sss.pgh.pa.us>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/487a96ce-9a5e-d89c-b1e7-c3a8285d8b15%40enterprisedb.com>
Precedence: bulk

On 25.03.22 14:32, Tom Lane wrote:
> Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
>> On 24.03.22 22:57, David Rowley wrote:
>>> Also, I'm quite keen to see this work make it into v15.  Do you think
>>> you'll get time to do that? Thanks for working on it.
> 
>> My thinking right now is to wait for the PG16 branch to open and then
>> consider putting it in early.
> 
> +1.  However, as noted by David (and I think I made similar points awhile
> ago), the patch could still use a lot of mop-up work.  It'd be prudent to
> continue working on it so it will actually be ready to go when the branch
> is made.

The v5 patch was intended to address all the comments you made in your 
Feb. 14 mail.  I'm not aware of any open issues from that.