Re: Mark all GUC variable as PGDLLIMPORT - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Mark all GUC variable as PGDLLIMPORT
Date
Msg-id Yk4oo1V7Opt9E06F@paquier.xyz
Whole thread Raw
In response to Re: Mark all GUC variable as PGDLLIMPORT  (John Naylor <john.naylor@enterprisedb.com>)
Responses Re: Mark all GUC variable as PGDLLIMPORT  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Wed, Apr 06, 2022 at 12:57:29AM +0700, John Naylor wrote:
> For these two patches, I'd say a day or two after feature freeze is a
> reasonable goal.

Yeah.  For patches as invasive as the PGDLLIMPORT business and the
frontend error refactoring, I am also fine to have two exceptions with
the freeze deadline.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: PATCH: add "--config-file=" option to pg_rewind
Next
From: "David G. Johnston"
Date:
Subject: Re: shared-memory based stats collector - v70