Re: [PATCH] force_parallel_mode and GUC categories

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] force_parallel_mode and GUC categories
Date: 2021-04-13 12:31:39
Message-ID: 20210413123139.GE6091@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

On Tue, Apr 13, 2021 at 04:34:23PM +0900, Michael Paquier wrote:
> On Mon, Apr 12, 2021 at 01:40:52AM -0400, Tom Lane wrote:
> >> - Should we make more general the description of the developer options
> >> in the docs?
> >
> > Perhaps ... what did you have in mind?
>
> The first sentence of the page now says that:
> "The following parameters are intended for work on the PostgreSQL
> source code, and in some cases to assist with recovery of severely
> damaged databases."
>
> That does not stick with force_parallel_mode IMO. Maybe:

Good point.

--
Justin

Attachment Content-Type Size
v3-0001-track_activity_query_size-is-STATS_COLLECTOR-cate.patch text/x-diff 879 bytes
v3-0002-track_commit_timestamp-is-REPLICATION_SENDING.patch text/x-diff 855 bytes
v3-0003-Change-force_parallel_mode-to-a-DEVELOPER-GUC-and.patch text/x-diff 8.1 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2021-04-13 12:32:15 Re: vacuum freeze - possible improvements
Previous Message Bharath Rupireddy 2021-04-13 12:03:29 Re: TRUNCATE on foreign table

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2021-04-13 14:12:35 Re: [PATCH] force_parallel_mode and GUC categories
Previous Message Michael Paquier 2021-04-13 07:34:23 Re: [PATCH] force_parallel_mode and GUC categories