| From: | Sergei Kornilov <sk(at)zsrv(dot)org> |
|---|---|
| To: | "ccn(at)chrisnestrud(dot)com" <ccn(at)chrisnestrud(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15721: FATAL: dsa_allocate could not find 97 free pages |
| Date: | 2019-03-28 18:47:20 |
| Message-ID: | 4276531553798840@sas2-b4ed770db137.qloud-c.yandex.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hello
Thank you for report. This bug should be already fixed in stable branch and will be shipped in next minor release. 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.
If you're interested, related discussion was here: https://www.postgresql.org/message-id/flat/CAMAYy4%2Bw3NTBM5JLWFi8twhWK4%3Dk_5L4nV5%2BbYDSPu8r4b97Zg%40mail.gmail.com
regards, Sergei
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2019-03-29 01:14:11 | BUG #15722: 9000x performance regression on query starting PostgreSQL 10 due to bad query plan |
| Previous Message | PG Bug reporting form | 2019-03-28 17:28:09 | BUG #15721: FATAL: dsa_allocate could not find 97 free pages |