pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jesper Pedersen <jesper.pedersen@redhat.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Thomas Munro <thomas.munro@enterprisedb.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] A GUC to prevent leader processes from running subplans?
Date: Wed, 15 Nov 2017 08:35:26 -0500
Message-ID: <000f92d6-f623-95a5-b341-46e2c0495cea@redhat.com> (raw)
In-Reply-To: <CA+Tgmoa=AxuLKo2f1AKwLmvFoo3rr3j+SYHaJ5GVyx1PhhOJ0Q@mail.gmail.com>
References: <CAEepm=2U++Lp3bNTv2Bv_kkr5NE2pOyHhxU=G0YTa4ZhSYhHiw@mail.gmail.com>
	<CA+TgmoZ9aamZq25MngYFEReADDWFJu2mGiASrg4+-8k65vY3DA@mail.gmail.com>
	<CAEepm=1+_Qo9Dwt6GD_2RQLoMgPCdMuq=mYvobPiHEgqCgqh9w@mail.gmail.com>
	<CA+TgmoZFtGUj5k=ak04fmBy1b=1M7h7v0Kt13m_MborcguBAxg@mail.gmail.com>
	<CAEepm=1GXFx488zXASvw249uVCnhzTZLDV19KcQAaMwUFJTgMQ@mail.gmail.com>
	<CA+Tgmoa=AxuLKo2f1AKwLmvFoo3rr3j+SYHaJ5GVyx1PhhOJ0Q@mail.gmail.com>

On 11/15/2017 08:28 AM, Robert Haas wrote:
> On Tue, Nov 14, 2017 at 12:28 AM, Thomas Munro
> <thomas.munro@enterprisedb.com> wrote:
>> Thanks.  You're right.  Rebased and updated to describe what "off" does.
> 
> Committed.  I noticed that you didn't add the new GUC to
> postgresql.conf.sample, so I did that.  But then I thought it didn't
> really belong in the section you put it, so I moved it to
> RESOURCES_ASYNCHRONOUS.
> 

Small typo.

Best regards,
  Jesper

Attachments:

  [text/x-patch] typo.patch (718B, ../000f92d6-f623-95a5-b341-46e2c0495cea@redhat.com/2-typo.patch)
  download | inline diff:
diff --git a/src/backend/utils/misc/postgresql.conf.sample b/src/backend/utils/misc/postgresql.conf.sample
index c7cd72ade2..63b8723569 100644
--- a/src/backend/utils/misc/postgresql.conf.sample
+++ b/src/backend/utils/misc/postgresql.conf.sample
@@ -163,7 +163,7 @@
 #effective_io_concurrency = 1		# 1-1000; 0 disables prefetching
 #max_worker_processes = 8		# (change requires restart)
 #max_parallel_workers_per_gather = 2	# taken from max_parallel_workers
-#parallel_leader_particulation = on
+#parallel_leader_participation = on
 #max_parallel_workers = 8		# maximum number of max_worker_processes that
 					# can be used in parallel queries
 #old_snapshot_threshold = -1		# 1min-60d; -1 disables; 0 is immediate

view thread (11+ messages)  latest in thread

Message-ID: <000f92d6-f623-95a5-b341-46e2c0495cea@redhat.com>
Permalink:  ../000f92d6-f623-95a5-b341-46e2c0495cea@redhat.com/
Also on:    postgresql.org/message-id/000f92d6-f623-95a5-b341-46e2c0495cea@redhat.com

 ·  · 

reply

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: jesper.pedersen@redhat.com, robertmhaas@gmail.com, thomas.munro@enterprisedb.com
  Subject: Re: [HACKERS] A GUC to prevent leader processes from running subplans?
  In-Reply-To: <000f92d6-f623-95a5-b341-46e2c0495cea@redhat.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