public inbox for [email protected]  

help / color / mirror / Atom feed

From: Alexander Pyhalov <[email protected]>
To: Matheus Alcantara <[email protected]>
Cc: Alena Rybakina <[email protected]>
Cc: Pgsql Hackers <[email protected]>
Subject: Re: Asynchronous MergeAppend
Date: Wed, 05 Nov 2025 09:30:59 +0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

Hi.

Matheus Alcantara писал(а) 2025-11-03 16:00:
> So I'm +1 for the idea. I know it's been while since the last patch, 
> and
> unfortunully it hasn't received reviews since then. Do you still plan 
> to
> work on it? I still need to take a look on the code to see if I can 
> help
> with some comments.
> 
> During the tests I got compiler errors due to fce7c73fba4, so I'm
> attaching a v5 with guc_parameters.dat correctly sorted.
> 
> The postgres_fdw/regress tests was also failling due to some whitespace
> problems, v5 also fix this.
> 
> [1] 
> https://www.postgresql.org/message-id/202510251154.isknefznk566%40alvherre.pgsql
> 

I'm still interested in working on this patch, but it didn't get any 
review (besides internal one). I suppose, Append and MergeAppend nodes 
need some unification, for example, ExecAppendAsyncEventWait and 
ExecMergeAppendAsyncEventWait looks the same, both 
classify_matching_subplans() versions are suspiciously similar. But 
honestly, patch needs thorough review.
-- 
Best regards,
Alexander Pyhalov,
Postgres Professional

view thread (33+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Asynchronous MergeAppend
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox