| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <rhaas(at)postgresql(dot)org> |
| Cc: | pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Notify bgworker registrant after freeing worker slot. |
| Date: | 2017-03-06 13:21:06 |
| Message-ID: | CAA4eK1KL02hUNpq8tcEvSoo-=37CVjQjaQX1k0xvNxwOcME6Bw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On Fri, Mar 3, 2017 at 9:27 AM, Robert Haas <rhaas(at)postgresql(dot)org> wrote:
> Notify bgworker registrant after freeing worker slot.
>
After this commit, I am seeing parallel queires being stucked on my
windows machine. I think the notify pid is stale in
ReportBackgroundWorkerExit() as we are freeing the same in
ForgetBackgroundWorker(). Attached patch fixes the problem for me.
Ashutosh Sharma has independently reported (offlist) this problem to me.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| select_parallel_hang_v1.patch | application/octet-stream | 988 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-03-06 14:37:29 | pgsql: Reorder the asynchronous libpq calls for replication connection |
| Previous Message | Masahiko Sawada | 2017-03-06 12:37:58 | Re: pgsql: Allow vacuums to report oldestxmin |