Re: Improve GetConfigOptionValues function

Поиск
Список
Период
Сортировка
От Bharath Rupireddy
Тема Re: Improve GetConfigOptionValues function
Дата
Msg-id CALj2ACVZ1GEaALLVoKCbLiMpMW2fYJGVFSL-vbwT8-_yWnSg7w@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Improve GetConfigOptionValues function  (Nitin Jadhav <nitinjadhavpostgres@gmail.com>)
Ответы Re: Improve GetConfigOptionValues function  (Nitin Jadhav <nitinjadhavpostgres@gmail.com>)
Список pgsql-hackers
On Thu, Jan 19, 2023 at 3:27 PM Nitin Jadhav
<nitinjadhavpostgres@gmail.com> wrote:
>
> > Possibly a better answer is to refactor into separate functions,
> > along the lines of
> >
> > static bool
> > ConfigOptionIsShowable(struct config_generic *conf)
> >
> > static void
> > GetConfigOptionValues(struct config_generic *conf, const char **values)
>
> Nice suggestion. Attached a patch for the same. Please share the
> comments if any.

The v2 patch looks good to me except the comment around
ConfigOptionIsShowable() which is too verbose. How about just "Return
whether the GUC variable is visible or not."?

I think you can add it to CF, if not done, to not lose track of it.

--
Bharath Rupireddy
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com



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

Предыдущее
От: "Jonathan S. Katz"
Дата:
Сообщение: Re: User functions for building SCRAM secrets
Следующее
От: Amit Kapila
Дата:
Сообщение: Re: Deadlock between logrep apply worker and tablesync worker