| From: | vignesh C <vignesh21(at)gmail(dot)com> |
|---|---|
| To: | Zhijie Hou <houzhijie22(at)gmail(dot)com> |
| Cc: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, shveta malik <shveta(dot)malik(at)gmail(dot)com>, Tomas Vondra <tomas(at)vondra(dot)me>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Andrei Lepikhov <lepihov(at)gmail(dot)com>, wenhui qiu <qiuwenhuifx(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com> |
| Subject: | Re: Parallel Apply |
| Date: | 2026-10-06 13:53:12 |
| Message-ID: | CALDaNm38KZ4svhTo+CnYi3h_oa=sqWtHVrFu5AqhQ2uspUttVQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 6 Oct 2026 at 16:57, Zhijie Hou <houzhijie22(at)gmail(dot)com> wrote:
>
> IIUC, this is not an issue introduced by this patch, since the patch doesn't
> change any error message handling here. It should have been there since the
> streaming parallel mode was introduced. Additionally, streaming parallel mode
> follows the same style as parallel query, so it looks possible that we have a
> similar issue in that case as well. If so, I think we should handle this
> separately in another thread, if it's really worth improving. Could you please
> confirm once?
Yes, this issue exists in HEAD's streaming parallel mode, the attached
patch helps in reproducing the issue in HEAD. I agree this need not be
handled in this thread and can be handled separately.
Regards,
Vignesh
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Test-to-reproduce-parallel-apply-error-context-issue.patch | application/octet-stream | 9.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vadim Ponomarev | 2026-10-06 14:01:28 | Re: Reduce SyncRepLock contention on the commit path |
| Previous Message | Bertrand Drouvot | 2026-10-06 13:46:24 | Re: Persist slot invalidations before publishing them |