Postgres Pro
Downloads
Home   >   mailing lists

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

From Robert Haas
Subject Re: Mark all GUC variable as PGDLLIMPORT
Date
Msg-id CA+TgmoZkRJGYDhZWJjdWdfcomT46aO9QwKM=daqrNQQ0CUyZgw@mail.gmail.com
Whole thread Raw
In response to Re: Mark all GUC variable as PGDLLIMPORT  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Mark all GUC variable as PGDLLIMPORT  (Magnus Hagander <magnus@hagander.net>)
Re: Mark all GUC variable as PGDLLIMPORT  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Tree view 
On Wed, Apr 6, 2022 at 7:56 PM Michael Paquier <michael@paquier.xyz> wrote:
> 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.

Done now.

-- 
Robert Haas
EDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Add parameter jit_warn_above_fraction
Next
From: Justin Pryzby
Date:
Subject: Re: Defer selection of asynchronous subplans until the executor initialization stage