Horton

Re: Apply PGDLLIMPORT markings to some GUC variables

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Sofia Kopikova <s.kopikova@postgrespro.ru>, pgsql-hackers@postgresql.org, Peter Eisentraut <peter@eisentraut.org>
Date: 2024-08-19T06:18:20Z
Lists: pgsql-hackers 
On Tue, Aug 13, 2024 at 03:00:00PM -0400, Robert Haas wrote:
> This seems correct to me.

It is not the first time that this happens in recent history.  Would
it be worth automating that?  I would guess a TAP test that takes a
copy of the headers, applies the changes while filtering the few
exceptions, then compares it to the origin in the tree?
--
Michael

Commits

  1. Apply PGDLLIMPORT markings to some GUC variables

  2. Move extern declarations for EXEC_BACKEND to header files