Horton
Menu

Re: Asynchronous MergeAppend

Matheus Alcantara <matheusssilv97@gmail.com>

View thread
From: Matheus Alcantara <matheusssilv97@gmail.com>
To: Alexander Korotkov <aekorotkov@gmail.com>, Alexander Pyhalov <a.pyhalov@postgrespro.ru>
Cc: Pgsql Hackers <pgsql-hackers@postgresql.org>
Date: 2026-03-30T12:25:47Z
Lists: pgsql-hackers 
Hi Alexander,

On 29/03/26 22:20, Alexander Korotkov wrote:
> Thank you for your work on this subject.
> I have revised the patchset.  I think it would be better if common
> infrastructure goes first.  Otherwise we commit async merge append and
> immediately revise it.  I also did some minor improvements.
> 

I was thinking about this but did not managed to spent time on it. 
Thanks for re-organizing the patches, it looks better and I think that 
it make more sense on this order.

I also agree with the minor improvements.

Thanks

--
Matheus Alcantara
EDB: https://www.enterprisedb.com

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Handle interrupts while waiting on Append's async subplans