| From: | Sergei Kornilov <sk(at)zsrv(dot)org> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | Maksim Milyutin <milyutinma(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15585: infinite DynamicSharedMemoryControlLock waiting in parallel query |
| Date: | 2019-04-12 13:48:19 |
| Message-ID: | 31541555076899@sas1-b3ec53dbc12b.qloud-c.yandex.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hello
Just for archive purposes:
This bug should be already fixed in stable branch and will be shipped in next minor release (11.3 and 10.8). Until the fix is released, the simplest workaround is to disable parallel query with SET max_parallel_workers_per_gather = 0 if you're affected by the bug.
It's a rare timing bug, but some workloads seem to be more prone to it, so unfortunately it went undetected for a long time.
Related discussion and patch was here: https://www.postgresql.org/message-id/flat/20190207014719.GJ29720%40telsasoft.com
regards, Sergei
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-04-12 16:47:49 | Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker |
| Previous Message | Sergei Kornilov | 2019-04-12 13:44:37 | Re: BUG #15749: ERROR: dsa_area could not attach to segment | FATAL: cannot unpin a segment that is not pinned |