Re: Asynchronous MergeAppend
Etsuro Fujita <etsuro.fujita@gmail.com>
From: Etsuro Fujita <etsuro.fujita@gmail.com>
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>
Date: 2026-04-06T05:32:55Z
Lists: pgsql-hackers
On Mon, Apr 6, 2026 at 12:40 PM Richard Guo <guofenglinux@gmail.com> wrote: > On Sun, Apr 5, 2026 at 11:25 AM Alexander Korotkov <aekorotkov@gmail.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
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Handle interrupts while waiting on Append's async subplans
- af717317a04f 18.0 cited