From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: PostgreSQL-development <pgsql-hackers@postgresql.org>
To: Robert Haas <robertmhaas@gmail.com>
Subject: crashes due to setting max_parallel_workers=0
Date: Sat, 25 Mar 2017 03:10:59 +0100
Message-ID: <6ecd6f17-0dcf-1de7-ded8-0de7db1ddc88@2ndquadrant.com> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackersAttachments:
[application/sql] crash-parallel.sql (537B, ../6ecd6f17-0dcf-1de7-ded8-0de7db1ddc88@2ndquadrant.com/2-crash-parallel.sql)
download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tomas.vondra@2ndquadrant.com, robertmhaas@gmail.com
Subject: Re: crashes due to setting max_parallel_workers=0
In-Reply-To: <6ecd6f17-0dcf-1de7-ded8-0de7db1ddc88@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox