| From: | Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Parallel Apply |
| Date: | 2025-09-05 11:44:59 |
| Message-ID: | CADzfLwXnJ1H4HncFugGPdnm8t+aUAU4E-yfi1j3BbiP5VfXD8g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello, Amit!
Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>:
> So, in such cases as we won't be able to detect
> transaction dependencies, it would be better to allow out-of-order
> commits optionally.
I think it is better to enable preserve order by default - for safety reasons.
I also checked the patch for potential issues like [0] - seems like it
is unaffected, because parallel apply workers sync their concurrent
updates and wait for each other to commit.
Best regards,
Mikhail.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chao Li | 2025-09-05 12:22:06 | Re: Raw parse tree is not dumped to log |
| Previous Message | Zhijie Hou (Fujitsu) | 2025-09-05 11:33:18 | RE: Conflict detection for update_deleted in logical replication |