From: | Joshua Drake <jd(at)commandprompt(dot)com> |
---|---|
To: | "Ma, Marcus" <marcjma(at)amazon(dot)com> |
Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Sharing DSA pointer between parallel workers after they've been created |
Date: | 2022-06-09 17:23:16 |
Message-ID: | CAJvJg-Qc6yOHr9yXprtUWXob+PbYoLVpqtKKAZW8sUOZaTJZow@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Marcus,
This is probably better suited for -hackers.
JD
On Wed, Jun 8, 2022 at 8:00 PM Ma, Marcus <marcjma(at)amazon(dot)com> wrote:
> Hey,
>
>
>
> I’m currently working on a parallelization optimization of the Sequential
> Scan in the codebase, and I need to share information between the workers
> as they scan a relation. I’ve done a decent amount of testing, and I know
> that the parallel workers all share the same dsa_area in the plan state.
> However, by the time I’m actually able to allocate a dsa_pointer via
> dsa_allocate0(), the separate parallel workers have already been created so
> I can’t actually share the pointer with them. Since the workers all share
> the same dsa_area, all I need to do is be able to share the single
> dsa_pointer with them but so far I’ve been out of luck. Any advice?
>
>
>
> Marcus
>
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua Drake | 2022-06-09 18:24:56 | Re: Logical replication of large objects |
Previous Message | Joshua Drake | 2022-06-09 17:22:37 | Re: Cluster OID Limit |