Postgres Pro
Downloads
Home   >   mailing lists

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

From Magnus Hagander
Subject Re: Mark all GUC variable as PGDLLIMPORT
Date
Msg-id CABUevExCG3Cm8TQhMCdmtfuJCQR4N7GOHw8WpFz8OV5=ydw_rw@mail.gmail.com
Whole thread Raw
In response to Re: Mark all GUC variable as PGDLLIMPORT  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Mark all GUC variable as PGDLLIMPORT  (Julien Rouhaud <rjuju123@gmail.com>)
List pgsql-hackers
Tree view


On Fri, Apr 8, 2022 at 2:42 PM Robert Haas <robertmhaas@gmail.com> wrote:
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.

\o/
 
--

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Commitfest Closed
Next
From: Tom Lane
Date:
Subject: Re: Extract epoch from Interval weird behavior