Re: [HACKERS] Parallel worker error

Поиск
Список
Период
Сортировка
От Amit Kapila
Тема Re: [HACKERS] Parallel worker error
Дата
Msg-id CAA4eK1J2mxpRObUtG2=HJfSinDHkdF4Qen-qFmmAxkrX3tq-xg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Parallel worker error  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: [HACKERS] Parallel worker error  (Amit Kapila <amit.kapila16@gmail.com>)
Список pgsql-hackers
On Fri, Sep 8, 2017 at 3:13 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Fri, Sep 8, 2017 at 1:17 AM, Amit Kapila <amit.kapila16@gmail.com> wrote:
>> You are right.  I have changed the ordering and passed OuterUserId via
>> FixedParallelState.
>
> This looks a little strange:
>
> +    SetCurrentRoleId(fps->outer_user_id, fps->is_current_user_superuser);
>
> The first argument says "outer" but the second says "current".  I'm
> wondering if we can just make the second one is_superuser.
>

No issues changed as per suggestion.

> I'm also wondering if, rather than using GetConfigOptionByName, we
> should just make the GUC underlying is_superuser non-static and use
> the value directly.  If not, then I'm alternatively wondering whether
> we should maybe use a less-generic name than varval.
>

I think we can go either way.  So prepared patches with both
approaches. In fix_role_handling_parallel_worker_v3_1.patch, I have
changed the variable name and in
fix_role_handling_parallel_worker_v3_2.patch, I have exposed the guc
is_superuser.



-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Thomas Munro
Дата:
Сообщение: Re: [HACKERS] More flexible LDAP auth search filters?
Следующее
От: Tom Lane
Дата:
Сообщение: [HACKERS] Still another race condition in recovery TAP tests