Re: Add PGDLLIMPORT lines to some variables - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: Add PGDLLIMPORT lines to some variables
Date
Msg-id CAMsr+YETdvyXME8dsywVqR0SLbEn_row1xJ8r=v+DUOC8PBrew@mail.gmail.com
Whole thread Raw
In response to Re: Add PGDLLIMPORT lines to some variables  (Andres Freund <andres@anarazel.de>)
Responses Re: Add PGDLLIMPORT lines to some variables  (Brian Cloutier <brian@citusdata.com>)
List pgsql-hackers
On 21 November 2017 at 04:02, Andres Freund <andres@anarazel.de> wrote:
Hi,

Please quote properly on postgres mailing lists... We're old school [tm].

On 2017-11-20 11:58:44 -0800, Brian Cloutier wrote:
> > please, append session_timezone to your list
>
> Here's a v2 patch which also includes session_timezone.
>
> Separately, is this the kind of thing which is eligible for backporting
> into the next releases of 9.6 and 10?

I don't think we quite have an established protocol for this. I
personally, but I'm biased in this specific case, is that we should
adopt a position that PGDLLIMPORTs should basically backpatched whenever
a credible extension even halfway reasonably requires it. There's no
easy way to get this done by default, and we're so far unwilling to just
slap this onto every variable. So to not further disadvantage people
force dto live in the MS environment, that seems the sanest
solution. It's not like these are high risk.


+1

I'm all in favour of backports to the last supported release or the first one the variable appeared in. 



--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: [HACKERS] [PATCH] Incremental sort
Next
From: Craig Ringer
Date:
Subject: Re: Using isatty() on WIN32 platform