Re: GUC values - recommended way to declare the C variables? - Mailing list pgsql-hackers

From Peter Smith
Subject Re: GUC values - recommended way to declare the C variables?
Date
Msg-id CAHut+PtJEiVZ5XpZk+7NARjuY0Xn=ESSspJ7eAwvs-MfmQHNdA@mail.gmail.com
Whole thread Raw
In response to Re: GUC values - recommended way to declare the C variables?  (Michael Paquier <michael@paquier.xyz>)
Responses Re: GUC values - recommended way to declare the C variables?  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-hackers
On Tue, Oct 25, 2022 at 4:09 PM Michael Paquier <michael@paquier.xyz> wrote:
>
> On Tue, Oct 25, 2022 at 02:43:43PM +1100, Peter Smith wrote:
> > This is essentially the same as before except now, utilizing the
> > GUC_DEFAULT_COMPILE flag added by Justin's patch [1], the sanity-check
> > skips over any dynamic compiler-dependent GUCs.
>
> Yeah, this is a self-reminder that I should try to look at what's on
> the other thread.
>
> > Patch 0001 - GUC trivial mods to logical replication GUC C var declarations
>
> This one seems fine, so done.
> --

Thanks for pushing v3-0001.

PSA v4. Rebased the remaining 2 patches so the cfbot can still work.

------
Kind Regards,
Peter Smith.
Fujitsu Australia

Attachment

pgsql-hackers by date:

Previous
From: Japin Li
Date:
Subject: Re: fixing typo in comment for restriction_is_or_clause
Next
From: John Naylor
Date:
Subject: Re: fixing typo in comment for restriction_is_or_clause