Re: Improve GetConfigOptionValues function - Mailing list pgsql-hackers

From Bharath Rupireddy
Subject Re: Improve GetConfigOptionValues function
Date
Msg-id CALj2ACVZ1GEaALLVoKCbLiMpMW2fYJGVFSL-vbwT8-_yWnSg7w@mail.gmail.com
Whole thread Raw
In response to Re: Improve GetConfigOptionValues function  (Nitin Jadhav <nitinjadhavpostgres@gmail.com>)
Responses Re: Improve GetConfigOptionValues function
List 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 by date:

Previous
From: "Jonathan S. Katz"
Date:
Subject: Re: User functions for building SCRAM secrets
Next
From: Amit Kapila
Date:
Subject: Re: Deadlock between logrep apply worker and tablesync worker