On Mon, Jun 03, 2019 at 09:16:56PM -0400, Tom Lane wrote:
> Yeah, I see we already did that in later branches. I'll go fix it,
> thanks for the heads-up!
Thanks.
--
Michael
signature.asc
Description: PGP signature
Michael Paquier writes:
> On Mon, Jun 03, 2019 at 10:06:21PM +, Tom Lane wrote:
>> Fix contrib/auto_explain to not cause problems in parallel workers.
> This has broken the builds on Windows for 9.6 and 10:
> https://buildfarm.postgresql.org/cgi-bin/show_stage_log.pl?nm=woodlouse&dt=2019-06-0
Hi Tom,
On Mon, Jun 03, 2019 at 10:06:21PM +, Tom Lane wrote:
> Fix contrib/auto_explain to not cause problems in parallel workers.
>
> A parallel worker process should not be making any decisions of its
> own about whether to auto-explain. If the parent session process
> passed down flags a
Fix contrib/auto_explain to not cause problems in parallel workers.
A parallel worker process should not be making any decisions of its
own about whether to auto-explain. If the parent session process
passed down flags asking for instrumentation data, do that, otherwise
not. Trying to enable ins
Fix contrib/auto_explain to not cause problems in parallel workers.
A parallel worker process should not be making any decisions of its
own about whether to auto-explain. If the parent session process
passed down flags asking for instrumentation data, do that, otherwise
not. Trying to enable ins
Fix contrib/auto_explain to not cause problems in parallel workers.
A parallel worker process should not be making any decisions of its
own about whether to auto-explain. If the parent session process
passed down flags asking for instrumentation data, do that, otherwise
not. Trying to enable ins
Fix contrib/auto_explain to not cause problems in parallel workers.
A parallel worker process should not be making any decisions of its
own about whether to auto-explain. If the parent session process
passed down flags asking for instrumentation data, do that, otherwise
not. Trying to enable ins
