| From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | crashes due to setting max_parallel_workers=0 |
| Date: | 2017-03-25 02:10:59 |
| Message-ID: | 6ecd6f17-0dcf-1de7-ded8-0de7db1ddc88@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
while working on a patch I ran into some crashes that seem to be caused
by inconsistent handling of max_parallel_workers - queries still seem to
be planned with parallel plans enabled, but then crash at execution.
The attached script reproduces the issue on a simple query, causing
crashed in GatherMerge, but I assume the issue is more general.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| crash-parallel.sql | application/sql | 537 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2017-03-25 02:40:51 | Re: dsm.c API tweak |
| Previous Message | David Rowley | 2017-03-25 01:42:50 | pg_get_statisticsextdef() is not quite the full shilling |