Re: Apply PGDLLIMPORT markings to some GUC variables

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Sofia Kopikova <s(dot)kopikova(at)postgrespro(dot)ru>, pgsql-hackers(at)postgresql(dot)org, Peter Eisentraut <peter(at)eisentraut(dot)org>
Subject: Re: Apply PGDLLIMPORT markings to some GUC variables
Date: 2024-08-19 06:18:20
Message-ID: ZsLjrPgdNkyXr7pW@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2024-08-19 06:21:30 Re: Create syscaches for pg_extension
Previous Message Xiaoran Wang 2024-08-19 06:17:17 Improve pg_re_throw: check if sigjmp_buf is valid and report error