Re: Asynchronous MergeAppend - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: Asynchronous MergeAppend
Date
Msg-id CAPpHfdu+3Eud0CBpdFT+osWiT=e=zOQUtBsx8Z5okKrqhgVAJg@mail.gmail.com
Whole thread
In response to Re: Asynchronous MergeAppend  (Alexander Pyhalov <a.pyhalov@postgrespro.ru>)
Responses Re: Asynchronous MergeAppend
List pgsql-hackers
Hi!

On Wed, Mar 18, 2026 at 8:17 AM Alexander Pyhalov
<a.pyhalov@postgrespro.ru> wrote:
> Alexander Pyhalov писал(а) 2026-03-02 09:44:
> > Alexander Pyhalov писал(а) 2026-02-12 10:08:
> >> Alexander Pyhalov писал(а) 2025-12-30 22:04:
> >>> Matheus Alcantara писал(а) 2025-12-30 18:04:
> >>>> On Tue Dec 30, 2025 at 10:15 AM -03, Alexander Pyhalov wrote:
> >>>>> Looks good. What do you think about
> >>>>> classify_matching_subplans_common()?
> >>>>> Should it stay where it is or should we hide it to
> >>>>> src/include/executor/execAppend.h ?
> >>>>>
> >>>> Yeah, sounds better to me to move classify_matching_subplans_common
> >>>> to
> >>>> execAppend.h since it very specific for the MergeAppend and Append
> >>>> execution. I've declared the function as static inline on
> >>>> execAppend.h
> >>>> but I'm not sure if it's the best approach.
> >>>>
> >>>> I've also wrote a proper commit message for this new version.
> >>>
> >>> Looks good to me.
> >>
> >> Hi.
> >> Rebased patches over fresh master.
> >
> > Hi.
> > Rebased patches over fresh master.
>
> Hi.
> Rebased patches over fresh master.

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.

------
Regards,
Alexander Korotkov
Supabase

Attachment

pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: Add comments about fire_triggers argument in ri_triggers.c
Next
From: Bharath Rupireddy
Date:
Subject: Re: Avoid multiple SetLatch() calls in procsignal_sigusr1_handler()