public inbox for [email protected]  

help / color / mirror / Atom feed

From: Chapman Flack <[email protected]>
To: Tom Lane <[email protected]>
Cc: Julien Rouhaud <[email protected]>
Cc: Andres Freund <[email protected]>
Cc: Michael Paquier <[email protected]>
Cc: [email protected]
Subject: Re: Mark all GUC variable as PGDLLIMPORT
Date: Sun, 13 Feb 2022 17:57:24 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <20210822081033.kx6op325sbd24cw5@nol>
	<[email protected]>
	<20210822120743.lvazjchtns5sezb2@nol>
	<[email protected]>
	<20210822132901.ztlervolfdbqypw4@nol>
	<20210823065334.6jpx4ux7l2maggvf@nol>
	<[email protected]>
	<20220213072931.dxfdumusodlrkxyf@jrouhaud>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On 02/13/22 15:48, Tom Lane wrote:
> much fix any worries there.  Or we could provide APIs that let an
> extension look up a "struct config_generic *" once and then fetch
> directly using that pointer.  (But I'd prefer not to, since it'd
> constrain the internals more than I think is wise.)

There is GetConfigOptionByNum already ... but I'm not sure there's
an easy way to ask "what's the num for option foo?".

GetNumConfigOptions exists, so there is a brute-force way.

Regards,
-Chap

view thread (10+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Mark all GUC variable as PGDLLIMPORT
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox