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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Peter Smith <smithpb2250(at)gmail(dot)com>
Cc: Justin Pryzby <pryzby(at)telsasoft(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-25 05:09:32
Message-ID: Y1dvjIIl+Gag46ru@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-10-25 05:20:12 Re: Getting rid of SQLValueFunction
Previous Message Tom Lane 2022-10-25 04:58:20 Re: Issue in GIN fast-insert: XLogBeginInsert + Read/LockBuffer ordering