MIME-Version: 1.0
References: <59be194c5a409fb9fc9f2031581b8a44@postgrespro.ru>
 <2fb1d9923b6995492e7b163e6cb95402@postgrespro.ru>
 <DE662JHGRO2O.3KJBBG2R3IT17@gmail.com>
 <efbfbcf00b6b790e8f80c13a83417a23@postgrespro.ru>
 <CAFY6G8d3Yvxa_kRQA24BsJhwqfmSCv1ujiv_7b6g5isf-ZTs_Q@mail.gmail.com>
 <b546d8bd5e2218f4f917fda4c93ead21@postgrespro.ru>
 <DED05POJZS2W.2EZ60AOBMDDAE@gmail.com>
 <bcdefce7e3db9566d0619ad2eed2a299@postgrespro.ru>
 <DF0RCOYB19RC.35BW2FHPO4N4S@gmail.com>
 <a16423ca928cde3650bbc219982a5ffc@postgrespro.ru>
 <DF28LV8UTUOO.71JUZDH1N8F9@gmail.com>
 <d5c0bfca6ee15d62df1ba72e540b4ddf@postgrespro.ru>
 <DFAQTF8P9AU0.2ZELZFXOCD0XL@gmail.com>
 <c264abe661f72d6627f987fc9aa4e456@postgrespro.ru>
 <DFBN6K9K9IUG.23WZ7OBL8DRAQ@gmail.com>
 <c0d55d3f68bfd5650fe3143d3a31c84c@postgrespro.ru>
 <782a968c8e01ec6db3b2da2120adf73b@postgrespro.ru>
 <554a73f7ffea8b22b3f81a4804b5fc34@postgrespro.ru>
 <e13717179328abed3e189f4ca1e63087@postgrespro.ru>
 <CAPpHfdu+3Eud0CBpdFT+osWiT=e=zOQUtBsx8Z5okKrqhgVAJg@mail.gmail.com>
 <42a9a941-e768-4fd8-8067-12958c5a1d70@gmail.com>
 <CAPpHfdsO8zYpDW==D6T5N0cJ+AzK7a_OyXJoYU1kFi=xZFTLuQ@mail.gmail.com>
 <CAMbWs49Nc_UKJ9Lm-j4w=X6Xd4a5SayQmb1F0P6OfA3XzGy=aw@mail.gmail.com>
In-Reply-To: 
 <CAMbWs49Nc_UKJ9Lm-j4w=X6Xd4a5SayQmb1F0P6OfA3XzGy=aw@mail.gmail.com>
From: Etsuro Fujita <etsuro.fujita@gmail.com>
Date: Mon, 6 Apr 2026 14:32:55 +0900
Message-ID: 
 <CAPmGK16c_hsMz1RM9Wu7F44cQzL+oOdC_T1S0nteAYG0hwTrxQ@mail.gmail.com>
Subject: Re: Asynchronous MergeAppend
To: Richard Guo <guofenglinux@gmail.com>
Cc: Alexander Korotkov <aekorotkov@gmail.com>,
 Matheus Alcantara <matheusssilv97@gmail.com>,
	Alexander Pyhalov <a.pyhalov@postgrespro.ru>,
 Pgsql Hackers <pgsql-hackers@postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CAPmGK16c_hsMz1RM9Wu7F44cQzL%2BoOdC_T1S0nteAYG0hwTrxQ%40mail.gmail.com>
Precedence: bulk

On Mon, Apr 6, 2026 at 12:40=E2=80=AFPM Richard Guo <guofenglinux@gmail.com=
> wrote:
> On Sun, Apr 5, 2026 at 11:25=E2=80=AFAM Alexander Korotkov <aekorotkov@gm=
ail.com> wrote:
> > I'm going to went through this patchset another time tomorrow and push
> > it on Monday if there are no objections.
>
> I completely understand the desire to get this committed ahead of the
> feature freeze.  However, I'm concerned that a one-day notice over the
> Easter weekend is simply too short for the community to see the
> announcement, let alone provide feedback, especially since this is a
> pretty big feature.
>
> I don't have any specific technical feedback on the patchset itself,
> as I haven't reviewed it.  My only hesitation is the short notice
> period.  That said, if you are highly confident in its readiness, I
> will defer to your judgment.

First, my apologies for not having reviewed this patch.  I was
planning to do so, but didn't have time for that, due to other
priorities.

I hate to say this, but as mentioned by Richard, this is a pretty big,
complex feature, so I also think the one-day notice is too short.

Best regards,
Etsuro Fujita