Re: GUC values - recommended way to declare the C variables?

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: Peter Smith <smithpb2250(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: GUC values - recommended way to declare the C variables?
Date: 2022-10-27 02:53:37
Message-ID: Y1nysek4m+FCo4HC@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 26, 2022 at 09:49:34PM -0500, Justin Pryzby wrote:
> In v4, Peter posted a 2-patch series with my patch as 001.
> But I pointed out that it's better to fix the initialization of the
> compile-time GUCs rather than exclude them from the check.
> Then Peter submitted v5 whcih does that, and isn't built on top of my
> patch.

Okidoki, thanks for the clarification.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-10-27 03:08:31 Re: Allow file inclusion in pg_hba and pg_ident files
Previous Message Richard Guo 2022-10-27 02:50:08 Re: Use LIMIT instead of Unique for DISTINCT when all distinct pathkeys are redundant