| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Parallel Apply |
| Date: | 2025-09-05 11:14:06 |
| Message-ID: | CAA4eK1LRuQjo63Ponr6czfaoxYn+=JZbugJXW2YO-xF41uyk5g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Sep 5, 2025 at 2:59 PM Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
>
> On Mon, Aug 11, 2025 at 10:16 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> >
>
> +1 for the idea. So I see we already have the parallel apply workers
> for the large streaming transaction so I am trying to think what
> additional problem we need to solve here. IIUC we are actually
> parallely applying the transaction which were actually running
> parallel on the publisher and commits are actually applied in serial
> order. Whereas now we are trying to parallel apply the small
> transactions so we are not controlling the commit apply order at the
> leader worker so we need extra handling of dependency and also we need
> to track which transaction we need to apply and which we need to skip
> after the restarts as well. Is that right?
>
Right.
> I am reading the proposal and POC patch in more detail to get the
> fundamentals of the design and will share my thoughts.
>
Thanks.
--
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2025-09-05 11:20:06 | Re: Logical Replication of sequences |
| Previous Message | Matheus Alcantara | 2025-09-05 10:45:32 | Re: LISTEN/NOTIFY bug: VACUUM sets frozenxid past a xid in async queue |