From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Thom Brown <thom(at)linux(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: max_parallel_degree context level |
Date: | 2016-02-11 13:18:15 |
Message-ID: | CA+TgmoaDjWfpkeWT83kEyTwMn7PdxyZf7d_GMFHNXBYMvgPoUw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Feb 11, 2016 at 7:40 AM, Thom Brown <thom(at)linux(dot)com> wrote:
> As it currently stands, max_parallel_degree is set to a superuser
> context, but we probably want to discuss whether we want to keep it
> this way prior to releasing 9.6. Might we want to reduce its level so
> that users can adjust it accordingly? They'd still be limited by
> max_worker_processes, so they'd at least be constrained by that
> setting.
I don't have a clue why it's like that. It seems like it should be
PGC_USERSSET just like, say, work_mem. I think that's just brain fade
on my part, and I think the current setting will be really
inconvenient for unprivileged users: as it is, they have no way to
turn parallel query off. Unless somebody objects, I'll go change
that.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2016-02-11 13:20:08 | Invalid user-level setting = confusing error message |
Previous Message | Robert Haas | 2016-02-11 13:15:47 | Re: [PATCH] Refactoring of LWLock tranches |