Re: Apply PGDLLIMPORT markings to some GUC variables
Peter Eisentraut <peter@eisentraut.org>
From: Peter Eisentraut <peter@eisentraut.org>
To: Michael Paquier <michael@paquier.xyz>, Robert Haas <robertmhaas@gmail.com>
Cc: Sofia Kopikova <s.kopikova@postgrespro.ru>, pgsql-hackers@postgresql.org
Date: 2024-08-19T09:20:33Z
Lists: pgsql-hackers
On 19.08.24 08:18, Michael Paquier wrote: > 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? Probably worth thinking about, but it would at least require some kind of exclude list, because there are exceptions like src/include/common/ /logging.h.
Commits
-
Apply PGDLLIMPORT markings to some GUC variables
- 5304fec4d8a1 18.0 landed
-
Move extern declarations for EXEC_BACKEND to header files
- d3cc5ffe81f6 18.0 cited