| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ParallelContexts can get confused about which worker is which |
| Date: | 2015-10-31 06:05:40 |
| Message-ID: | CA+TgmoZPf9U4C1CPQoTXbHQyK-BUX0bRqatWTMgT4khYA7a1Gw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 30, 2015 at 11:24 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> The other way to fix this is to pass down the index
> that the leader assigns to any given worker, and have the worker use
> that index instead of allocating its own separate index after
> connecting to the DSM segment. Unfortunately, there's not really a
> good way to pass that additional information down to the worker right
> now, but we could fix that pretty easily by adding an additional field
> to the BackgroundWorker structure, which the worker would then be able
> to access via MyBgworkerEntry.
Here's a patch implementing that.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| Attachment | Content-Type | Size |
|---|---|---|
| fix-worker-index-confusion-v1.patch | text/x-diff | 3.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2015-10-31 06:55:32 | Re: New gist vacuum. |
| Previous Message | Michael Paquier | 2015-10-31 05:50:09 | Re: September 2015 Commitfest |